Enable first-party data collection with DNS setup. This is highly recommended as it increases the amount of tracked conversions. To fully unlock the power of Tracklution’s server-side tracking, we strongly recommend setting up a custom DNS record for your website. This crucial step allows you to collect data as first party, dramatically improving your ability to track conversions accurately, even when third-party cookies are blocked or click IDs are missing.
When Tracklution scripts are loaded through your own domain (instead of ours), ad platforms like Google and Meta treat the tracking as first party. This significantly improves data reliability and opens the door to powerful features like:
- Higher Conversion Match Rates: Capture more conversions that would otherwise go untracked.
- Enhanced Conversions & Advanced Matching: Fully benefit from Google Ads and Meta advanced features.
- Improved Attribution: Maintain visibility across user sessions and devices.
- Better Performan c e : More accurate campaign data leads to smarter ad optimisation.
If you want Tracklution to work at its best, DNS setup is not just a nice-to-have, it’s essential.
- Log in to your DNS provider: Access your domain’s DNS settings through your hosting provider.
- Add a CNAME or A record. You will find your unique records at the Tracklution dashboard, under "First-Party Mode" tab:
- Save and apply the changes
- Verify your installation: Go back to your Tracking Container’s onboarding interface and press the "Verify DNS installation" button. Tracklution will check if your DNS is configured correctly.
- Troubleshooting tip:
-
- If verification fails, try changing the host from "tralut.YOUR-DOMAIN**.com" to simply "tralut", or "tralut."
**instead of YOUR-DOMAIN, use your own domain.
If you track subdomains: the DNS settings need to be done for the main domain (only).
If you track multiple separate domains (not subdomains) in one container, the DNS settings should be configured for each domain individually, while all domains point to the same Tracklution container backend.
For example, if you are tracking websiteA.com and websiteB.com, the CNAME should be added twice. Both should be pointing to the domain that is under your container's "First-Party Mode"-tab.
- Host: tralut.websiteA.com → Points to: main-1234.trlution.com
- Host: tralut.websiteB.com → Points to: main-1234.trlution.com
- *check the right domain from your container.
Both domains use the same Tracklution container and are now able to share sessions reliably using first-party tracking.
