AT Internet

we are going to deprecate this sdk we are going to deprecate this sdk summary official websites true 162 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type developer integrations true 160 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type tracking service event support matrix overview of the supported events and their configuration true 163,262left unhandled content type unhandled content type unhandled content type left unhandled content type unhandled content type unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type purchases purchases are not supported ( ) ( ) actions actions and views views contains special handling regarding parameters more detailed information can be found below in the description of the event configuration for actions and views general structure in tracking config json tracking service key name in " tracking config json " is " atinternet atinternet " general structure { "atinternet" { "eventsenabledbydefault" true, "viewsenabledbydefault" true, "purchasesenabledbydefault" false, "attributesenabledbydefault" true, "events" { // your configured list of events }, "views" { // your configured list of events }, "purchases" {}, "attributes" { // your configured list of attributes } } } event configuration actions at internet supports action events action event "action event key" { "templates" { "name" "value of template", "action" "value of template", "chapter1" "value of template", "chapter2" "value of template", "chapter3" "value of template", "level2" "value of template" }, "parameters" { "property parameter key 1" "value of parameter", // your configured list of parameters, // added as non persistant properties to at internet } } example "issue downloaded" { "templates" { "action" "download", "name" "{{issue name}}", "chapter1" "{{publication name}}", "chapter2" "download", "level2" "1" }, "parameters" { "property issue id" "{{issue id}}", "property issue name" "{{issue name}}", "property issue categories" "{{issue categories}}", "property issue tags" "{{issue tags}}", "property issue purchasable" "{{issue purchasable}}", "property issue purchased" "{{issue purchased}}", "property publication id" "{{publication id}}", "property publication name" "{{publication name}}" } } templates " action" action" with at internet each action event is tracked as a " gesture event " as it is described in the official documentation true 174 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type each " gesture event " can have a different types of actions this is configured with the corresponding action action template true 167 unhandled content type unhandled content type unhandled content type unhandled content type if no action or an invalid value was provided, the event will be sent as a " touch touch " event on the web platform, gestures are always sent as " click click " events " level2 level2 " quote from at internets documentation " at internet’s sdk offers you the possibility to “separate” your application into different sections (called “level 2s”) these level 2s allow you to better target certain parts of your application in order to zoom in on how these parts are used " true 174 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type this is configured with the corresponding level2 level2 template true 167 unhandled content type unhandled content type unhandled content type unhandled content type parameter purple implements parameter for action events for at internet as follows each parameter will be sent as a non persistent property before the event itself is sent when they are marked with the prefix " property property " this prefix is removed before sending read more about persistent and non persistent properties in the https //developers atinternet solutions com/as2 tagging en/piano analytics tagging/tagging custom properties sdk en/ example for non persistent property parameter " property property my awesome property my awesome property " " awesome awesome " is sent as " my awesome property my awesome property " " awesome awesome " all parameters without this " property property " prefix are ignored views at internet supports view events view event "view event key" { "templates" { "name" "value of template", "chapter1" "value of template", "chapter2" "value of template", "chapter3" "value of template", "level2" "value of template" }, "parameters" { "property parameter key 1" "value of parameter", // your configured list of parameters, // added as non persistant properties to at internet "parameter key 1" "value of parameter", // your configured list of parameters, // added as custom vars to at internet } } example "storefront newsstand" { "templates" { "name" "e paper", "level2" "1" }, "parameters" { "property issue id" "{{issue id}}", "property issue name" "{{issue name}}", "issue id" "{{issue id}}", "issue name" "{{issue name}}" } } template " level2 level2 " quote from at internets documentation " at internet’s sdk offers you the possibility to “separate” your application into different sections (called “level 2s”) these level 2s allow you to better target certain parts of your application in order to zoom in on how these parts are used " true 174 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type this is configured with the corresponding level2 level2 template true 167 unhandled content type unhandled content type unhandled content type unhandled content type parameter purple implements parameter for view events for at internet as follows each parameter will be sent as a non persistent property before the event itself is sent when they are marked with the prefix " property property " this prefix is removed before sending in addition to this all parameters without that prefix are sent as custom variables for the event the restriction for custom variables is that the parameter key must be evaluable as an integer value read more about persistent and non persistent properties in the https //developers atinternet solutions com/as2 tagging en/piano analytics tagging/tagging custom properties sdk en/ example for non persistent property parameter " property property my awesome property my awesome property " " awesome awesome " is sent as " my awesome property my awesome property " " awesome awesome " example for custom var parameter is sent as configured, key must be an integer " 1 1 " " awesome awesome " all parameters without this " property property " prefix or those with a parameter key that cannot be evaluated as an integer are ignored purchases at internet does not support purchase events attributes at internet supports attributes attribute "attribute key" { "templates" { "name" "value of template" } } example "has active subscription" { "templates" { "name" "has active subscription" } } attributes purple implements attributes for at internet as follows each attribute will be sent as a persistent property via " setprop setprop " api read more about this topic in the official documenation true 174 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type additional supported functionality no additional features which may be provided by at internet are currently supported how to configure native purple app any native tracking service is configured in the purple manager purple manager enable sdk settings location " your app your app " => " consent/push/analytics consent/push/analytics " => " analytics (general/ios/android/web) analytics (general/ios/android/web) " true 166,307 unhandled content type unhandled content type unhandled content type unhandled content type configuration settings are different by the used platform true 166,307 unhandled content type unhandled content type unhandled content type unhandled content type true 166,307 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type apple privacy / att settings location " your app your app " => " consent/push/analytics consent/push/analytics " => " privacy privacy " consent management settings location " your app your app " => " consent/push/analytics consent/push/analytics " => " consent management consent management " true 166,307 unhandled content type unhandled content type unhandled content type unhandled content type web integration enable sdk at internet is not explicitly enabled if a valid configuration of at internet is present in the " experience config json ", the sdk is integrated into the html document structure in experience config json plugin configuration { "purple" { "analytics" { "atinternet" { "configuration" { // there is no further configuration needed // since the configuration is done within the // customer specific javascript file } } } } } consent management if you use one of the cmps supported by purple, you must specify the cmp specific vendor id for at internet, which you can get from your cmp frontend additionally, the iab vendor id for at internet can also be added structure in experience config json plugin configuration with consent { "purple" { "analytics" { "atinternet" { "configuration" { // there is no further configuration needed // since the configuration is done within the // customer specific javascript file }, "consent" { "vendorid" "", "iabvendorid" "" } } } } }