Domains — custom domains
Connecting custom domains and subdomains via Cloudflare for tracking links, landing pages, and event tracking in Tracker. Tracker → Domains is an infrastructure section used to connect domains for cam
Connecting custom domains and subdomains via Cloudflare for tracking links, landing pages, and event tracking in Tracker.
Tracker → Domains is an infrastructure section used to connect domains for campaign operations. Without an added domain, the Domain field in Information — Basic Campaign Identification will remain unavailable, and the campaign cannot be saved.
Chatterfy does not sell domains and does not manage registrations: you must purchase a domain from a registrar, connect it via Cloudflare, and only then add it to Tracker.
What the Domains section allows
Domains allows you to configure: tracking links on your own domain, landing pages and funnel transitions, specific subdomains for offers, GEOs and teams, HTTPS and SSL via Cloudflare, and access management for domains between media buyers and teams — see Buyers — Buyers and Team Leads.
A typical sequence looks like this:
domain → Cloudflare → landing page → Telegram → events and analytics.
If you skip one of the setup stages, you usually encounter issues such as:
SSL did not activate
the browser displays an insecure connection warning
tracking link does not open
What is inside
— How to add a subdomain — creating an additional address within an already connected primary domain.
Why Cloudflare is needed
Cloudflare is used as a DNS proxy between your domain and Chatterfy infrastructure.
It is used to configure:
DNS records
SSL certificates
HTTPS
proxying and basic traffic protection
For most scenarios, the free Cloudflare plan is sufficient.
The target DNS record for integration with Tracker is a CNAME to:
tracker.chatterfy.aiCloudflare handles the following:
tracking link opens
landing page loads
user transitions
some server requests and events
Without proper SSL and DNS, ad networks and browsers may restrict transitions.
What can be connected
Apex domain
The main domain without a subdomain.
Examples:
example.com · mybrand.ioSuitable if:
you are launching infrastructure from scratch
you need a separate brand
an affiliate program requires a separate domain
you want to completely isolate the offer
Subdomain
An additional address within the main domain.
Examples:
us.example.com · de.example.com · promo.example.comSuitable if:
the main site is already running on apex
you need multiple entry points for GEOs or offers
you are testing different funnels
you want to separate teams and traffic
Subdomains are usually easier and cheaper to maintain: one domain can be used for dozens of separate scenarios.
When to use a domain vs a subdomain
Situation | What to choose |
|---|---|
First launch, no domain yet | New domain |
The main domain already has a site | Subdomain |
Multiple offers or GEOs | Multiple subdomains |
Need full isolation | Separate domain |
Quick test | Subdomain |
One domain can be used simultaneously in several Tracker campaigns.
How the setup works
Connecting a domain is not a single step, but a sequence of settings between Cloudflare and Chatterfy.
For a new apex domain
Setup sequence:
For a subdomain
If the primary domain is already connected to Cloudflare:
gicon:TriangleAlert
Менять порядок нельзя
Without Cloudflare, Tracker will not verify the domain. Without SSL, redirects may be blocked. Without adding it to Chatterfy, the domain will not appear in Campaigns.
In this case, you usually do not need to change nameservers at the registrar — a new DNS record inside Cloudflare is sufficient.
Why the domain must be added to Tracker first
Once connected, the domain is used by the system for: tracking links, landing pages, redirects, event tracking, branded URL, and shortened links via Bot Variables in AI Prompts.
All user clicks pass through your domain rather than the platform's technical address.
One domain or multiple
Small team
Usually sufficient:
one primary domain
2–3 subdomains for GEO
Example:
us.example.com · de.example.comMultiple media buyers
Usually, they use:
separate subdomains per team
separate domains for risky offers
This allows you to isolate traffic and restrictions.
Agency model
You can connect a separate branded domain for each client.
Which domains are suitable
Tracker usually has no restrictions on domain zones.
Restrictions more often arise from:
Cloudflare
ad networks
affiliate programs
Most common zones
Zone | Features |
|---|---|
.com / .net / .org / .io | Most versatile |
.de / .us / .uk | GEO-oriented |
.xyz / .site / .online | Cheap, but sometimes cause more checks |
When choosing a domain, consider the requirements of ad platforms and affiliate programs.
Linking domains to buyers
In Domains, you can restrict access to domains for individual users and teams.
This is convenient if:
the team has many domains
different buyers work with different offers
infrastructure isolation is needed
Getting started
Task | Article |
|---|---|
First domain | |
New subdomain | |
SSL error | |
Domain is missing in Campaigns | |
Need a landing page |
FAQ
Section articles
Related
Was this article helpful?








