Page Contents

Compliance: Storing or reading cookies on the devices of endusers for marketing tracking purposes requires prior consent. Clients are adviced not to trigger Agillic tracking on webpages and in emails unless a valid consent is obtained first.

It is possible to implement a tracking script on any external website, which will feed activity data to Agillic. If Agillic has identified a particular recipient in the browser the tracking data will be tied to this particular recipient, otherwise it will be assigned an anonymous identity. If at a later stage a recipient is identified in the same browser the tracking data is transfered to the recipient and the anonymous cookie is removed.

The tracking service is enabled in Agillic UI and the script can be copied from here as well.
The tracking data can be used to target particular recipients in Agillic as well as in a simple personalization on a 3rd. party site.

Read how to export tracking data to apply additional analysis and logic.


The Agillic tracking setup is run on a different set of servers than the server used for campaigning. In order to ensure the most effective sharing of information the tracking servers and your Agillic server share the same domain, which mean that they see each others cookies, i.e. no need for redirects between them in order to detect if the other have identified the server. In order to avoid the many issues with 3rd party cookies, we recommend that you assign a domain to Agillic, which is a subdomain to the domain where the tracking script is placed. We also recommend that you never use the default domain assigned for tracking.

All calls to our tracking server is done protocol relative (i.e. if the page is loaded in http the tracking call is http, and if it’s loaded in https, then we use https). This means that if the website you want to track uses https then you cannot start tracking before you have correctly setup a custom sub-domain with https in Agillic.

All tracking data is stored on the tracking server. Agillic will the query that server for the relevant information when needed as part of evaluations or exports. This means that the tracking data is available immidiately.


The tracking logic itself is fairly standard and straightforward:

  1. You place a small js script on the pages (either directly or using Google tag manager)
  2. When the page is loaded the js script will create a simple image url with the relevant parameters identifying which page it was loaded on etc.
  3. This call goes to our tracking server
  4. The tracking server will check for two cookies: the one used for identifiying recipients in Agillic, the one it set itself for anonymous trackings.
  5. If either is present it will store the tracking on that key, if both are present it will delete the anonymous cookie and merge the trackings for the two keys into one
  6. If neither are present it will check if it can set a cookie, and if it can set a new anonymous cookie and if so assign the tracking to that new key

On the Agillic side we also have a bit of logic which means that everytime we identify a recipient in a browser and write that cookie, we check for the anonymous tracking cookie, and if that is found delete it and notify the tracking server to merge the two keys into one.

The merge happens asynchronously, so there will be a tiny delay from we identify the recipient until the tracking data is merged.

This logic will ensure that it doesn’t matter if a recipient is first tracked and then identified, or the other way around. We will have the same information available.

If you have a way of identifying a recipient on your side (e.g. after login on the website where the tracking script is), please contact Agillic support for assistance on how to provide this information to Agillic to improve the matching rate.