This is the first onboarding step, and the Tie Pixel depends on it. It is a small change at your domain provider, and your live site is never touched.
What you are doing
Tie runs your tracking environment on a dedicated subdomain of your domain (for example zone.yourdomain.com). Tie provisions and manages that subdomain on our side. You do not create it. Your only job is to delegate it to Tie by adding a set of NS (nameserver) records at your domain provider.
Steps
Open your Connect Domain page in the Tie dashboard, enter your store's domain, and submit it.
Tie then provisions your tracking subdomain and generates your NS records. This is quick, but it is not instant, so give the page a moment to finish. Your records do not exist until this completes, which is why you will not see any records before you submit a domain.
The fastest way to add them: click Adjust added DNS below the domain field. It opens Entri, the service Tie uses for DNS setup. Entri detects who hosts your DNS, asks you to sign in there, and adds the records for you in one click. If you have access to your DNS, this is the whole job.
To add the records by hand instead, close the Entri tab. Back on the Tie tab your NS records are now listed. Add them at your domain provider.
Add these alongside your existing records. Do not change or overwrite your primary nameservers.
Save and allow time to propagate. Verification can take up to 72 hours, and Tie emails you once it completes. A low TTL helps changes take effect faster.
Back on the Connect Domain page, click Check Verification Status to force a re-check and unlock your next steps.
Good to know
Your root domain and live site are never touched, and there is no downtime.
Cannot add NS records at your provider? Some setups, including domains hosted directly through Shopify, do not allow it. See My domain provider will not let me add NS records.
Nervous about DNS changes? Ask your Tie contact about starting with a TXT test record first.
Why NS records and not a CNAME? Tie runs a full tracking, identity, and server-side event environment on the subdomain (script hosting, event ingestion, SSL, global routing), and only NS delegation can carry that.
Verification not passing?
See DNS verification isn't passing for the common causes.
