Setting Up Your DNS


MetaRouter includes the ability to collect data under a first-party domain for all of your properties. This is particularly important for client-side event streams, where it provides the benefits of cross-domain identity syncing, and mitigation against common ad blocking technology. There are two primary domains that are used by the client-side libraries that can be set up first-party.

Who is this guide for?

This guide is relevant to those in your organization who are familiar with any CDNs you may already have set up for your website, as well as those responsible from your organization for the installation of MetaRouter.

DNS Setup

There are two aspects of your DNS that you will need to define before sending events to MetaRouter- your Javascript CDN and your Ingestion Domain.

Javascript CDN

The Javascript CDN is where the javascript file that is loaded from the Analytics.js Install Guide exists. When the javascript snippet loads on the page, it retrieves the contents of this file and executes the library on the page. Periodically, when configurations are updated inside of the platform, a new file will need to be generated to manage those configuration changes. We will always generate this file for you, but you are responsible for where your file is hosted and who is responsible for updating the file inside of your CDN when there are necessary updates. By hosting this file yourself, you benefit from cross-domain identity syncs and ad blocker mitigation. However, you will be responsible for updating the file when configuration changes are required.

The most common scenario for updating an Analytics.js file is when you would want to add a new integration that requires an update to the Sync Injector in order to resolve identity for a particular user. Generally, you will not have to update your Analytics.js file often unless you add new integrations often.

For an additional fee, we can provide use of our own CDN for a MetaRouter-hosted Analytics.js file. While this option is helpful for some scenarios, where we maintain the file on a CDN maintained by us and handle the update automatically, it is not the recommended setup as it does not facilitate cross-domain identity syncing and ad blocker mitigation benefits.

Ingestion Domain

The Ingestion Domain is the URL that your Analytics.js library will send events to and represents the entry point for events into your MetaRouter cluster. Once events are received inside of your cluster, we will apply any event transformation preferences you indicate within our UI and forward events to your integrations.

In order to recognize the benefits of first-party event ingestion, you will also need to designate an A Record for your domain so all event ingestion can occur in the first-party. The cluster will automatically provision SSL using an HTTP challenge once the A Record is set up inside of your domain.

The process will be started by your Solution Lead.

  1. Via, you will share your Events Subdomain and CDN Location. Your subdomain will be dedicated to only receive events.
  2. Also via the same support ticket, you will advise the CDN location of the DNS Record URL.
  3. Your Solution Lead will create your MetaRouter cluster, IP Address, A.js file and snippet.
  4. You will receive an email with an alert when your download is ready.
  5. After downloading the information, you will create an A Record that points to the IP Address provided to you.
  6. Then you may verify events have fired using the Metrics and Monitoring feature.

Once you have selected your CDN hosting option, the Analytics.js file is hosted inside of your CDN, and you have set up your Ingestion Domain, you are ready to install your Analytics.js SDKs and send events into your MetaRouter cluster.