-
Notifications
You must be signed in to change notification settings - Fork 0
Dynamic screens 85336f
Dynamic screens (or dynamic labels) allow you to save the history of a page whose content has been modified.
This tag, especially designed for media sites, enables continuity when tracking an app screen even if the editorial content (articles, in large part) changes.
The screen can be renamed to better adapt to the editorial content without disrupting the continuity of analyses.
The tagging principle is the same as that of a screen.
Once your tag is initialised, you can start tagging your dynamic screens.
If you want to use variables, be sure to import ATInternet, Tracker, DynamicScreen classes in your Activity.
To tag a screen, the tracker exposes a dynamicScreens object.
This property exposes an add method allowing for the inclusion of screen information.
This method sends back a DynamicScreen-type object. To send the defined information, you must manually call your object’s sendView method or call the dispatch method of the Tracker.
- Tagging a screen with a dynamic name:
@Override
protected void onResume() {
super.onResume();
tracker.DynamicScreens().add("1", "News", new Date()).sendView();
}| Name | Type | Default value | Description |
|---|---|---|---|
| screenId | String (Int deprecated) | null | Gets or sets the screen ID (ex: “article-123456”) |
| update | Date | null | Gets or sets the date of screen creation or update |
| name | String | Chaîne vide | Gets or sets the screen name |
| chapter1 | String | null | Gets or sets the first chapter |
| chapter2 | String | null | Gets or sets the second chapter |
| chapter3 | String | null | Gets or sets the third chapter |
| action | Enum | Action.View | Gets or sets the action type |
| level2 | Int | -1 | Gets or sets the level 2 ID |
| isBasketScreen | Bool | false | Indicates if the screen is displaying the content of a cart (if the SalesTracker option is used) |
| Name | Return type | Description |
|---|---|---|
| sendView | void | Sends the screen hit |
Last update: 29/11/2019
-
Data API
- Data flow
- Advice optimizations data flow
- Error codes data flow
- Faq data flow
- General information data flow
- Technical information data flow
- Reporting API v3
- Getting started
- Methods
- Parameters
- Technical information
- REST API
- Campaigns
- Custom variables
- Getting started rest
- Methods rest
- Response structure parameters rest
- Fixed periods
- Parameters compatibility
- Relative periods
- Structure of the response
- “code” parameter
- “columns” parameter
- “evo” parameter
- “filter” parameter
- “include” parameter
- “lng” parameter
- “max-results” parameter
- “page-num” parameter
- “period” parameter
- “period” parameter: “H” v. “He” & “MN” v. “MNe”
- “retention” parameter
- “segmentdesc” parameter
- “segment” parameter
- “sep” parameter
- “sort” parameter
- “space” parameter
- Technical specifications rest
- Data flow
-
Data collection
- Android
- Advanced features
- Campaigns
- Changelog
- Content
- Ecommerce
- Getting started
- Users
- Apple
- Advanced features
- Campaigns
- Changelog
- Content
- Ecommerce
- Getting started
- Users
- General
- Cddc renew staging process
- Changelog
- Craft your hit
- Encoded parameters
- Server side cookie management
- Supported taggings
- Tagging deletion
- Utilisation of dispatch sdks
- JavaScript
- Advanced features
- Campaigns
- Changelog
- Content
- Ecommerce
- Getting started
- Partners javascript
- Users
- Piano Analytics
- Event tagging piano analytics
- Getting started piano analytics
- Piano analytics tagging
- Feeding piano analytics with as2 tagging
- Tagging custom properties sdk
- Android