Direct advertising links
In your site settings, open Channels → Direct from ads, then choose Copy link for the channel and paste it into your ad. No landing page, JavaScript, API key or DNS setup is required.
The site needs a connected Meta pixel and an active linked Telegram channel and bot.
AdTarget records the visit and queues a Meta PageView, generates an attributed Telegram invitation, then returns HTTP 302. The configured conversion (normally Lead) is sent when the person joins; a redirect is not a join. Meta delivery is asynchronous and can fail.
Query parameters are preserved in the visit URL. fbclid is converted to fbc; UTM parameters and gclid, ttclid and sccid are captured. pixelRoute optionally selects an existing Meta route owned by the site account. fbc and fbp can be passed explicitly by an upstream integration. Shared AdTarget marketing cookies are never reused for customer attribution.
A site-scoped HttpOnly cookie reuses the same operation for the same URL for 60 seconds. A changed query creates a new visit. Without the cookie, including simultaneous first requests or a response lost before cookie receipt, deduplication is not guaranteed. Do not add a fixed visitRequestId to ads.
GET returns a non-cacheable 302 only after an attributed invitation is ready. HEAD and explicit browser prefetch do not record events. Errors return 400, 404, 429 or 5xx without redirecting to an untracked fallback. Retry the same link after a transient failure.
Use the link copied from AdTarget; the example below contains placeholders. Existing /c/ links and POST /backend/track/direct-invite remain unchanged. The standard link uses adtarget.io. Choose Custom domain to connect your own subdomain. Test the full redirect, join and Meta receipt before launching. No browser Meta pixel is executed on this server-only path; previews performing an ordinary GET can be counted as visits.
https://adtarget.io/r/{siteId}/{channelId}?utm_source=facebook&utm_campaign=launchYour own domain
In channel settings, open Direct from ads, choose Custom domain, enter a subdomain such as
go.example.com. Add the displayed DNS records
at your DNS provider, then select Verify. DNS editors that append your zone
name require relative record names. Keep the ownership TXT after activation.
The link becomes active after ownership, routing and HTTPS checks. Verification
is automatic; DNS propagation may take longer. Copy link then
copies https://go.example.com/. Your main website stays at its current
hosting. A path on an externally hosted website cannot be routed by DNS alone.
Each hostname maps to one channel. Existing links with paths continue to work. Disconnect disables the link
immediately, followed by automatic provider cleanup.
Verified custom domains preserve first-party Meta identifiers in host-only cookies and send the branded URL to CAPI. A 302 does not execute the browser Meta pixel; do not assume CAPI PageView receipt equals the Landing Page Views metric in Ads Manager.