When you switch to a custom track domain or change to a new one, the tracking configuration is only one part of the setup. Other components can still point to the old track domain. This page lists what to check. Only the components you actually use are relevant for you.
Important
Change your configuration only after Mapp has confirmed that the new track domain is ready. Requests to a track domain without a valid certificate are lost. Keep the old track domain active as long as apps or other systems still send tracking requests to it. Your Mapp contact removes it afterwards.
What to Check
The tracking configuration of every integration
Existing visitor IDs in server-side cookies
Marketing Automation
Server-to-server tracking
Calls to the Mapp Intelligence APIs
Your own tracker or proxy
Tracking Configuration
Replace the previous track domain with the new one wherever it is configured. The place depends on the integration, for example the Smart Pixel configuration, the Mapp Intelligence plugin in the Tag Integration, or the SDK initialization in apps. See step 6 in Custom Track Domain.
Existing Visitor IDs
Server-side cookies belong to the track domain that set them. After a change, the new track domain cannot read them. Returning visitors then receive a new everId and are counted as new visitors. To avoid this, migrate the cookies with the Cookie Control Plugin.
Marketing Automation
To read the everId, which the segments rely on, Marketing Automation requests must be sent to your custom track domain. Contact your Mapp Intelligence Customer Success Manager for the configuration.
If you load the Marketing Automation library or its server configuration via your custom track domain, also check the parameters mcpBaseURL and widgetServiceUrl. See Implementing the Marketing Automation Plugin.
Server-to-Server Tracking
The tracking system generates an everId on the first visit of a visitor and stores it in the cookie wteid_[Track-ID]. Your server can read the everId from this cookie and send it in the parameter eid with each server-to-server request. See Server-to-Server Tracking.
Note
Your server can only read a cookie that the browser sends to it. This requires that the cookie belongs to a domain your server receives requests for. If your server needs the everId and does not receive the cookie, ask Mapp for help.
API Calls
If you call the Mapp Intelligence REST APIs through your custom track domain, replace the host name in the request URL with your track domain and use HTTPS. The path depends on the API: /segments/v2 for the Audience API and /dmp/recos/v2 for the Recommendation API.
Important
Using the APIs through your own track domain requires a separate activation by Mapp. Ask Mapp to activate it before you change the host name.
For details, see Using the Audience API and Using the Recommendation API.
Own Tracker or Proxy
If you use your own tracking server or a proxy server that forwards requests to Mapp, contact your Mapp Intelligence Customer Success Manager. Together you verify that your current implementation works with the new track domain.