Dynamic screens



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.



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:
    protected void onResume() {
            tracker.DynamicScreens().add("1", "News", new Date()).sendView();

DynamicScreen class



NameTypeDefault valueDescription
screenIdString (Int deprecated)nullGets or sets the screen ID (ex: “article-123456”)
updateDatenullGets or sets the date of screen creation or update
nameStringChaîne videGets or sets the screen name
chapter1StringnullGets or sets the first chapter
chapter2StringnullGets or sets the second chapter
chapter3StringnullGets or sets the third chapter
actionEnumAction.ViewGets or sets the action type
level2Int-1Gets or sets the level 2 ID
isBasketScreenBoolfalseIndicates if the screen is displaying the content of a cart (if the SalesTracker option is used)


NameReturn typeDescription
sendViewvoidSends the screen hit
Last update: 29/11/2019