Content types

getting started a subset of content aware events are based on the content type content type of the affected content these events are documented with their tracking key templates at action events docid 8rra4o7vzdaw13y joqek and view events docid\ mixe5 ijkbr47eummdyga , but not with their possible occurrences a tracking key template itself includes a placeholder for the content type content type the content type content type is determined at runtime (e g in the app) and used instead of the placeholder in the respective tracking key template the content types content types are described in the following paragraph content types docid\ tz lfyagszxfbnspzmiwq an example for finding and configuring a corresponding event is described in the paragraph content types docid\ tz lfyagszxfbnspzmiwq content types the content type can have the following values issue issue post post bundle bundle all content that is available in an app, for example, is assigned to one of these content types content types the content types content types are passed for the placeholders in the tracking key template uppercased before they are used for tracking for example, " issue issue " becomes " issue issue " content type based event in order to configure a content type content type based event, three steps are necessary what usecase to track and how to find your event how to find which content type content type your content has how to create a corresponding entry in your tracking config json example step 1 what usecase to track and how to find your event as an example, a user's tap on the bookmark button of an issue in the storefront of an app should be tracked this is an action event and the corresponding event documentation can be found action events docid 8rra4o7vzdaw13y joqek the event consists of the following tracking key template storefront < content type content type > bookmark add clicked step 2 how to find which content type content type your content has this step depends on how your content comes to your app for this example we assume that the user taps on bookmark button for an issue so that case results in a content type content type " issue issue " step 3 how to create a corresponding entry in your tracking config json now we simply replace the placeholder " content type content type " within the tracking key template by " issue issue " and then get the final tracking key storefront issue bookmark add clicked now compose your event configuration and add it to your tracking config json so your event configuration may look as follows code sample "storefront issue bookmark add clicked" { "templates" { "action" "issue bookmark add clicked" }, "parameters" { "view" "{{view}}", "issue id" "{{issue id}}", "issue name" "{{issue name}}", "issue categories" "{{issue categories}}", "issue tags" "{{issue tags}}", "issue purchasable" "{{issue purchasable}}", "issue purchased" "{{issue purchased}}", "issue product id" "{{issue product id}}", "publication id" "{{publication id}}", "publication name" "{{publication name}}" } } note the code sample above is used for firebase depending on your tracking service that configuration may differ