Dynamic screens

 

Foreword

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.

 

Get off to a good start

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.

 

Tagging

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 example

  1. Tagging a screen with a dynamic name:
 

DynamicScreen class

 

Properties

Name Type Default value Description
screenId String (Int deprecated) null Gets or sets the screen ID
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)
 

Méthodes

Name Return type Description
sendView void Sends the screen hit
Was this post helpful?
Yes
No
Last update: 30/01/2018