-
Notifications
You must be signed in to change notification settings - Fork 0
Dynamic labels
Before using dynamic labels methods, please make sure you have initialised the AT Internet JavaScript Tracker and selected the Page plugin from within the Tag Composer interface.
Dynamic labels allow you to track the history of a page whose content has been modified.
This tag, especially suited for media sites, allows tracking continuity to be maintained, even if the editorial content (mostly articles) changes.
The page can therefore be renamed to better correspond to the editorial content, without disrupting analysis continuity.
The Tracker has a dynamicLabel.set() method allowing you to define the values of dynamic names/labels. The method takes, as a parameter, an object whose properties are as follows:
| Property | Description |
|---|---|
| pageId | Dynamic ID enabling the renaming of the page, without creating a new page |
| chapter(i) | Name of the chapter corresponding to the new page label |
| update | Date of the name change, to insert in the format YYYYMMDDHHMM |
-
- Tagging a page with dynamic labels:
var tag = new ATInternet.Tracker.Tag();
tag.page.set({
name:'pageName',
level2:'2'
});
tag.dynamicLabel.set({
pageId: 'article-123456',
chapter1: 'mychapter1',
chapter2: 'mychapter2',
chapter3: 'mychapter3',
update: '200910031045'
});
tag.dispatch();- Tagging dynamic labels with the “page.send()” method:
Tagging dynamic labels by way of the “page.send()” method requires directly passing the “dynamicLabel” object as a parameter:
var tag = new ATInternet.Tracker.Tag();
tag.page.send({
name:'pageName',
level2:'2',
dynamicLabel:{
pageId: 'article-123456',
chapter1: 'mychapter1',
chapter2: 'mychapter2',
chapter3: 'mychapter3',
update: '200910031045'
}
});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