-
Notifications
You must be signed in to change notification settings - Fork 0
code parameter
When you save a Data Query template, it gives you a short code back. This short code is the short cut of the Data Query data set.
It is generally recommended to use short codes to ensure the best flexibility in reporting.
By default, a short code will contain all of the items of the template: columns, sort, filters, site, etc.
If you need to change how the calls to the short code are sorted, it is possible to overload the short code in order to apply a new sort.
For example, here is our basic query:
https://apirest.atinternet-solutions.com/data/v2/xml/GetData?code=2MEu4z&period={D:2017-08-12}&max-results=30&page-num=1
Please refer to this note if you’re using SSO to login to AT Internet services.
You therefore need to change the way the calls to the short code are sorted, which is currently carried out in descending order on the metric “m_visits”. Should you need to sort this on another metric of the data set, just add it to the query as follows:
https://apirest.atinternet-solutions.com/data/v2/xml/GetData?code=2MEu4z&period={D:2017-08-12}&max-results=30&page-num=1&sort=-m_conversions1_visits
Please refer to this note if you’re using SSO to login to AT Internet services.
In the event of an overload on the columns parameter, all of the columns will be reset.
In the previous example the short code 2MEu4z contains the following columns: d_time_month,d_source,m_visits,m_conversions1_visits
During an overload, the short code will be as follows:
https://apirest.atinternet-solutions.com/data/v2/xml/GetData?code=2MEu4z&period={D:2017-08-12}&max-results=30&page-num=1&columns={d_page,m_visits}
Please refer to this note if you’re using SSO to login to AT Internet services.
The result will only be the visits for the “d_page” column, and not the entire set of columns from the short code 2MEu4z plus the “d_page” column.
Last update: 22/01/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