To perform website customer data tracking with MetaRouter, you must first configure your Domain Naming Service (DNS) server and a Content Distribution Network (CDN):
- The DNS server settings should provision a subdomain that is mapped to your MetaRouter data infrastructure. This will represent the endpoint where MetaRouter sends your customer data.
- The CDN will host the analytics.js file that your snippet retrieves and loads on your website users' browsers. This file performs the tracking and routing of data to your MetaRouter data infrastructure.
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.
Regardless of whether you choose an A or CNAME record, you will need to provide a subdomain naming convention. When determining the subdomain, ensure you enforce the same naming convention across all of your domains. For example, we commonly see
analytics.[companyname].com . We recommend choosing a subdomain that is less common than these, as some ad blockers may prevent a subdomain with the words
tracking , the letters
t or other common tracking-related keywords from loading.
MetaRouter will provide you with your cluster's IP Address or A record, which will need to be added to your DNS configuration. The IP Address will be required if you are configuring the cluster endpoint as an A record. We'll provide you with the A record for the cluster if you would like the endpoint to be a CNAME record.
You will need access to your DNS provider account in order to create your record. Any DNS provider should suffice. We'll walk through the process for a common DNS provider, Cloudflare:
- Login to your Cloudflare account.
- Select your website domain.
- Click the DNS tab, and select the Records subsection.
- Click the "+ Add record" button.
- Choose the record Type. Again, we recommend using an A record, but you may select C as well.
- Enter your subdomain (
- Enter the cluster IP address (if configuring an A record) or A records (if configuring a C record) that we sent you.
- Click "Save".
Your cluster should now be able to ingest data sent with your new DNS record!
Once the Analytics.js file is hosted inside of your CDN and you have configured your DNS record, you are ready to install your Analytics.js SDKs and send events into your MetaRouter cluster.
Updated 3 months ago