Set up first-party tracking

First-party tracking serves the Buron pixel from a subdomain you own, like t.yourdomain.com, instead of Buron's default domain. The pixel still runs in the browser. You're just loading it first-party, from your own domain, which is what keeps ad blockers and browser tracking prevention from filtering it out.

This is optional. Tracking works on the default domain without it. Turning it on recovers the visits and journeys you'd otherwise lose to blocking.

Why serve the pixel from your own domain

Ad blockers and browser privacy features (like Safari's Intelligent Tracking Prevention) filter requests to known third-party analytics domains. When the pixel loads from Buron's shared domain, some of those requests never fire, so those visits never reach your reports.

Served from your own subdomain, the pixel is first-party. It looks like part of your site, so more of your events arrive and the cookies that stitch a journey together last longer. On a site with meaningful blocked traffic, this is often the difference between a partial picture and a complete one.

Before you begin

You'll need:

• A Buron site with the pixel installed. If you haven't done that yet, start with Install the Buron pixel.
• A dedicated subdomain you own, such as t.yourdomain.com. Use a subdomain, not your root domain.
• Access to your domain's DNS provider.

Step 1: Add your subdomain in Buron

Open Settings → Pixel, find First-party tracking, and enter the subdomain you want to use, like t.yourdomain.com. Select Use custom domain.

Buron detects your DNS provider and shows you the single record to add.

Step 2: Add the CNAME record

At your DNS provider, add one record:

Enter only the subdomain label in Name (t), not the full t.yourdomain.com. Most providers add the rest of your domain for you.

Step 3: Wait for it to verify

Buron checks your DNS automatically and re-checks every 15 seconds, so you can leave the page open. You can also select Recheck now. The status moves through a few states:

• Waiting for DNS — the record isn't visible yet.
• Propagating — the record is found and pointing the right way, and Buron is issuing the HTTPS certificate. This takes a few minutes.
• Active — your subdomain is serving the pixel over HTTPS. The certificate is issued and renewed for you.

Step 4: Reinstall the snippet

Once the domain is Active, the snippet on Settings → Pixel updates to load from your subdomain. Copy it again and replace the old one on your site, so both the script and its events run through your domain.

Until the domain is active, Buron keeps the snippet pointed at the default domain, so you never paste a half-configured one.

Remove a custom domain

Remove the domain in Settings → Pixel, then delete the CNAME record at your DNS provider.

Frequently asked questions

Does the default domain stop working? No. If you remove the custom domain, tracking falls back to the default domain automatically.

Can I use my root domain? Use a dedicated subdomain. A CNAME record can't sit on a root domain, and a dedicated subdomain keeps this separate from your other records.

Is this the same as server-side tracking? No. First-party tracking changes where the pixel is served from; the pixel still runs in the browser. Server-side tracking sends events from your backend instead — a different approach, covered in Server-side tracking: what it fixes, what it costs, and whether you need it.

Next steps

• Connect your CRM so revenue ties back to source
• See how Buron attribution works end to end