-
Notifications
You must be signed in to change notification settings - Fork 0
Custom object 9d4b7b
Before using the “customObject” parameter, please make sure you have initialised the AT Internet JavaScript Tracker and selected the Page plugin from the Tag Composer interface.
The “customObject” parameter allows you to pool together all parameters you wish to measure and possibly display variables pre-defined by AT Internet (“name”, “level2”, etc.): the Data Manager interface is necessary in order to tell our data treatment system which parameter corresponds to which dimension.
The “customObject” parameter can contain as many parameters as you wish.
- Declaration format for a parameter with 1 dimension:
tag.page.set({
customObject: {
param1: 'val1',
param2: 'val2'
}
});
tag.dispatch();where “param(i)” are the labels of parameters and “val(i)” are the values to associate with these parameters (surrounded by quotes in the case of text). 2. Declaration format for a parameter with 2 dimensions:
tag.page.set({
customObject: {
param1: {
param11: 'val1',
param12: 'val2'
}
}
});
tag.dispatch();where “param(ii)” are the labels of parameters and “val(ii)” are the values to associate with these parameters (surrounded by quotes in the case of text). In the above example, the parameters “param 11” and “param12” are completely dependent on the parameter “param1�.
- Declaration format for a parameter with 1 dimension:
tag.page.send({
customObject: {
param1: 'val1',
param2: 'val2'
}
});- Declaration format for a parameter with 2 dimensions:
tag.page.send({
customObject: {
param1: {
param11: 'val1',
param12: 'val2'
}
}
});It is possible to combine parameters with 1 or 2 dimensions in the �customObject� declaration.
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