-
Notifications
You must be signed in to change notification settings - Fork 0
Custom tree structure 6eaf02
AT Internet’s SDK lets you create a custom tree structure for your application.
Thanks to this feature, you can get a completely customised view of your traffic that responds precisely to your analysis criteria.
To do this, you must use screen categories. They represent a new way of classifying your screens, complementary to chapters, enabling a lateral view of results.
Once your tag has been initialised, you can create your custom tree structure.
If you want to use variables, be sure to import ATInternet, Tracker, Screen and CustomTreeStructure classes in your Activity.
The Screen object makes available a CustomTreeStructure method.
This method takes one parameter :
- category1 of type int indicates the first custom tree category
This method returns a CustomTreeStructure object
- Create a custom tree structure
package com.atinternet.atinternetdemo;
import android.app.Activity;
import android.os.Bundle;
import com.atinternet.tracker.ATInternet;
import com.atinternet.tracker.Tracker;
public class MainActivity extends Activity {
private Tracker tracker;
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_main);
tracker = ATInternet.getInstance().getDefaultTracker();
}
@Override
protected void onResume() {
super.onResume();
Screen s = tracker.Screens().add(this);
s.CustomTreeStructure(5)
.setCategory2(8)
.setCategory3(4);
s.sendView(); // &ptype=5-8-4
}
}| Name | Type | Default value | Description |
|---|---|---|---|
| category1 | Int | 0 | Gets or sets the tree structure’s main category |
| category2 | Int | 0 | Gets or sets the tree structure’s subcategory |
| category3 | Int | 0 | Gets or sets the tree structure’s sub-subcategory |
Last update: 05/04/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