-
Notifications
You must be signed in to change notification settings - Fork 0
Custom tree structure 94c810
Before using page custom tree structure methods, please ensure that you have initialised the AT Internet JavaScript tracker and selected the Page plugin from within the Tag Composer interface.
Thanks to this feature, you can obtain a completely customised view of all your traffic to completely match your analysis criteria. To do this, you must use page categories. Page categories allow you to classify pages complementarily to chapters, in order to have a transverse view of all results.
The following is a prerequisite for using a custom tree structure:
- Declare your page categories (names, levels, etc.) from within the interface (Tools > Settings > Navigation & usability > Custom tree structure)
You can create your custom tree structure in an Excel or CSV file, then import it directly into your AT Internet interface.
The Tracker has a customTreeStructure.set() method enabling you to define the custom tree structure values. This method takes an object as a parameter with the following properties:
| Property | Description |
|---|---|
| category1 | ID of first category level |
| category2 | ID of second category level |
| category3 | ID of third category level |
IDs passed in the tag corresponding to those declared in the interface. They are between 0 and 255.
- Tagging a page with a custom tree structure:
var tag = new ATInternet.Tracker.Tag();
tag.page.set({
name:'pageName'
});
tag.customTreeStructure.set({
category1:1,
category2:2,
category3:3
});
tag.dispatch();- Tagging a custom tree structure with the “page.send()” method:
The tagging of tags via the “page.send()” method requires passing the “customTreeStructure” object directly as a parameter:
var tag = new ATInternet.Tracker.Tag();
tag.page.send({
name:'pageName',
customTreeStructure:{
category1:1,
category2:2,
category3:3
}
});Last update: 30/01/2018
-
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