How to configure a custom subdomain in Onetagger?

Edited 5 days ago

Configuring your own subdomain is one of the first steps to fully set up your Onetagger server-side tagging container. Using a dedicated subdomain tied to your brand domain is strongly recommended — it ensures more reliable data tracking, improves domain reputation, and reduces the risk of being blocked by ad blockers.

Why use a custom subdomain?

Using your own subdomain means all your tracking requests run through a branded URL (e.g., track.mywebsite.be), which makes them appear as first-party and significantly improves deliverability and resilience against tracking disruptions.

If you can’t set up a custom domain, you can still use a default Onetagger subdomain. However, this might be more easily recognized and blocked by privacy tools in the future, so for maximum performance, we suggest configuring your own.


Key terms explained

Term Description
Subdomain A subdomain is a subdivision of your main domain, such as shop.mywebsite.be or track.mywebsite.be. Your Onetagger container will run on this subdomain.
DNS record DNS (Domain Name System) records connect your domain name to specific servers or IP addresses so that traffic is routed correctly.
Domain host The company or service where your domain is managed and configured. Examples include Cloudflare, GoDaddy, Namecheap, Wizzou, etc.

Steps to set up your subdomain

1️⃣ Choose your subdomain

Decide on a subdomain you want to use, like track.mywebsite.be. In your Onetagger container setup screen, select Use custom domain, and enter this subdomain. Once entered, Onetagger will automatically generate the DNS configuration details you’ll need.


2️⃣ Configure your DNS record

Log in to your domain hosting or DNS provider.

  • Navigate to your DNS management area.

  • Create a new A record:

    • Type: A

    • Name: The chosen subdomain (e.g., track)

    • Value: The IP address provided by Onetagger in your setup instructions

  • Save the changes.

If your provider supports it, you might also be able to add a CNAME record instead, depending on your setup and our instructions.


3️⃣ Verify your setup

After adding the DNS record, return to your Onetagger setup screen and click Verify or Check configuration.

Onetagger will check whether your subdomain is correctly pointing to our infrastructure.

  • If verification succeeds, you’ll see a success message and can proceed to finalize your container.

  • If it fails, check for typos in the subdomain name or IP address, and ensure the record is saved and propagated.


Validation tip

DNS changes can take some time (anywhere from a few minutes to up to 24 hours) to propagate globally. You can check propagation status using external tools like WhatsMyDNS.

Once your subdomain is live, visiting it should display a confirmation page indicating it is ready for tagging operations.


Provider-specific help

We’ve prepared step-by-step guides for common DNS providers:

  • Cloudflare

  • GoDaddy

  • Namecheap

  • Google Domains

  • AWS Route 53

  • And more

If your provider is not listed, refer to their support documentation on creating A or CNAME records.


Final checks

✅ Subdomain correctly points to Onetagger IP or hostname
✅ Verification in the dashboard passes
✅ Test container loads on your subdomain without errors

Once these checks are complete, you’re ready to start using Onetagger for your server-side tracking setup.


Need help?

If you encounter issues, please refer to our troubleshooting guide or contact our support team directly.

Was this article helpful?