This repository was archived by the owner on May 5, 2026. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
Tracker initialization
Benjamin Diolez edited this page May 5, 2026
·
1 revision
Before starting, you need to download our JavaScript library, or push it to our CDN, from the Tag Composer interface.
This interface will allow you to:
- Configure the marking perimeter (site, domain used for writing cookies, etc.).
- Select the desired features through configurable plugins.
Once the library is set up, you need to call on it in the <head> tag of your page.
<!-- Local file -->
<script src="smarttag.js"></script>
<!-- CDN file -->
<!-- File must be published on the TDN for this site within Tag Composer -->
<script src="//tag.aticdn.net/YOURSITEID/smarttag.js"></script>
The Tracker initialization is done through JavaScript methods to be inserted.
<html>
<head>
<meta charset="UTF-8">
<title>My Page</title>
<script src="smarttag.js"></script>
</head>
<body>
...
<script type="text/javascript">
var tag = new ATInternet.Tracker.Tag();
tag.events.send("page.display", {
"page": "My Page",
"page_chapter1": "My chapter 1"
});
</script>
</body>
</html>The ATInternet.Tracker.Tag() constructor can take two objects as parameters, one intended to override the Tracker configuration and a second intended to add context values.
The initialization of the Piano Analytics tagging is the same as for the AS2 tagging.
For more information, you can turn to the dedicated articles:
Last update: 06/05/2022
-
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