Migrate to a custom domain (CDDC)

 

Introduction

You wish to migrate your site to a custom domain (Custom Domain Data Collection – CDDC), and must therefore update your tag to collect on this new domain, during the authorized migration period (28 days).

This migration must be done during the 28-day period allowed for migration, during which we collect on both domains. After this period, any hit sent on the old domain will be lost.

With a custom domain, you also have the ability to change the pixel path (/hit.xiti by default), in order to further customize your data collection.

Some adblockers blocking the resource /hit.xiti, we recommend customizing the pixelPath.

 

To be noted

 

No campaign tagging by redirection

For security reasons, the CDDC does not allow campaigns to be tagged by redirection (/go.url, /gopc.url, …). Attempting to mark by redirection on the CDDC will result in a 403 error, and the visitor will not access your site.

We therefore invite you to switch to direct marking.

 

Planning migration

Migration planning is done via the interface of site management. When editing a site, if a custom domain is available, you will be offered to migrate. You will then have to choose a migration start date, from which a 28-day period will be automatically determined. You will then have to migrate the tagging during this period, otherwise the data would not be collected.

 

With CDN

If you use the Internet CDN AT, simply update the file via TagComposer, and you will then automatically switch to your new collection domain.

This update must be done during the migration period to ensure that it contains the correct information.

 

With a local file

If you are using a file hosted locally on your server, you will need to download a new version of the file from TagComposer, and replace the file in question with the new one.

This download must be done during the migration period to ensure that it contains the correct information.

 

Without updating the smarttag.js file

It is also possible to migrate without updating the file, via a modification of the tracker instantiation.

 

Version up to 5.12.1

Until version 5.12.1, the configurations log, logSSL and domain can be used to migrate to a custom domain.
You will then have to split your customized collection domain like this:

Technically, a concatenation by a point is made between log and domain, and between logSSL and domain.

var tag = new ATInternet.Tracker.Tracker.Tag({log:'YOURLOG', logSSL:'YOURSSLLOG', domain:'YOURDOMAINLOG', pixelPath:'/collect' });

To be noted:

  • The non secure domain and the SSL domain are the same
  • The pixel path pixelPath must start with / and can’t be empty
 

Version 5.13.0+

Since version 5.13.0, the configurations log, logSSL and domain have been replaced by collectDomain and collectDomainSSL.

Old configurations remain available for backwards compatibility

If you are using version 5.13.0 or later, you just need to initialize your tracker like this:

var tag = new ATInternet.Tracker.Tag({collectDomain:'YOURCOLLECTDOMAIN', collectDomainSSL:'YOURSSLCOLLECTDOMAIN', pixelPath:'/collect' });

To be noted:

  • The non secure domain and the SSL domain are the same
  • The pixel path pixelPath must start with / and can’t be empty
 

Was this post helpful?

Last update: 26/08/2019