3rd party integrations
...
Purple Tracking
Tracking Services

AT Internet

26min

We are going to deprecate this SDK in favor of Piano. 

Summary

Official websites

Developer integrations

Platform

URL

Android

iOS

Website

Customer specific Javascript file provided by AT Internet

Tracking service

Event support matrix

Overview of the supported events and their configuration.



Templates

Parameter

Actions

name action chapter1 chapter2 chapter3 level2

supported*

Views

name chapter1 chapter2 chapter3 level2

supported*

Attributes

name

not supported

Purchases are not supported.

(*) Actions and 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"

General structure


Event configuration

Actions

AT Internet supports action events.

Action event
Example


Templates

"action"

With AT Internet each action event is tracked as a "Gesture event" as it is described in the official documentation:

Each "Gesture event" can have a different types of actions. This is configured with the corresponding action template.

Template key

Template value

action

The values need to be one of:

  • "touch"
  • "navigation"
  • "download"
  • "exit"
  • "search"

If no action or an invalid value was provided, the event will be sent as a "touch" event. On the web platform, gestures are always sent as "click" events.

"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."

This is configured with the corresponding level2 template.

Template key

Template value

level2

The value must evaluate to a valid integer value.

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_". This prefix is removed before sending.

Read more about persistent and non-persistent properties in the official documentation. 

Example for non-persistent property

Parameter "property_my_awesome_property": "Awesome"

is sent as "my_awesome_property": "Awesome"

All parameters without this "property_" prefix are ignored.

Views

AT Internet supports view events.

View event
Example


Template

"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."

This is configured with the corresponding level2 template.

Template key

Template value

level2

The value must evaluate to a valid integer value.

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_". 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 official documentation.

Example for non-persistent property

Parameter "property_my_awesome_property": "Awesome"

is sent as "my_awesome_property": "Awesome"

Example for custom var

Parameter is sent as configured, key must be an integer "1": "Awesome"

All parameters without this "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
Example


Attributes

Purple implements attributes for AT Internet as follows: Each attribute will be sent as a persistent property via "setProp" API. Read more about this topic in the official documenation:

Platform

API => setProp

Android

setProp (scroll down, only "Tracker" class is linked)

iOS

setProp

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.

Enable SDK

Settings location

"Your app" => "Consent/Push/Analytics" => "Analytics (General/iOS/Android/Web)"

Setting

Description

Enable AT Internet

To enable the AT Internet SDK in your app, activate this checkbox.

Configuration settings are different by the used platform.

Setting (Android)

Description

Configuration-JSON

The configuration file for Android. This file is provided by AT Internet.

Setting (iOS)

Description

Configuration file

The configuration file for iOS. This file is provided by AT Internet. This file is used for any device class.

iPad configuration file

The configuration file for iPad.

If present, it will be used instead of the global configuration file.

iPhone configuration file

The configuration file for iPhone.

If present, it will be used instead of the global configuration file.

iPod configuration file

The configuration file for iPod.

If present, it will be used instead of the global configuration file.

Apple privacy / ATT

Settings location

"Your app" => "Consent/Push/Analytics" => "Privacy"

Consent management

Settings location:

"Your app" => "Consent/Push/Analytics" => "Consent Management"

Setting

Description

Vendor-ID for AT Internet

The Vendor-ID is provided by the consent management platform.

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


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




Updated 19 Jul 2024
Did this page help you?