Technical documentation · v1.1
Tracking link specification
This page explains exactly what the Traffic Boosters tracking link does with an ad click. It is written for advertisers, agencies and ad-platform policy reviewers.
1. Overview
The tracking link runs on click.trafficboosters.net. Advertisers put it in the tracking-template or click-URL field of their ad account. For each paid click, the link records the click’s metadata and then sends the visitor to the advertiser’s final URL, unchanged.
The link only measures and monitors. Traffic-quality analysis runs separately, after the redirect has already been served. It never affects where a click goes.
2. What the link is used for
Traffic Boosters uses the tracking link for monitoring. Each click that passes through it gives us the signals we need to check that a campaign is working as intended:
- Traffic-quality monitoring — the requesting network, user agent, timing and click frequency, which separate a genuine visitor from a bot, a data-center proxy or a repeat clicker. Ad platforms don’t report these per click.
- Link and landing-page monitoring — confirming that every ad link resolves and that the destination responds, so broken or slow landing pages are caught before they waste budget.
- Campaign reporting — click counts by campaign, ad group, keyword and device, reconciled against what the ad platform bills.
Server-side measurement also catches traffic that never runs JavaScript on the landing page. With the results we report invalid and suspicious clicks to the advertiser, suggest exclusions they can apply in their own ad account, and provide click-level evidence for invalid-activity credit requests.
3. URL format
Tracking template, set at account, campaign or ad-group level. Values in braces are filled in by the ad platform’s own macros when the click happens:
https://click.trafficboosters.net/c?cid={campaign_id}&agid={adgroup_id}&crid={ad_id}&kw={keyword}&dev={device}&clid={click_id}&url={destination_url}| Parameter | Placeholder | Purpose |
|---|---|---|
cid | {campaign_id} | Campaign identifier |
agid | {adgroup_id} | Ad group or ad set identifier |
crid | {ad_id} | Ad or creative identifier |
kw | {keyword} | Keyword or targeting term, where the platform provides one |
dev | {device} | Device type |
clid | {click_id} | The ad platform’s click identifier |
url | {destination_url} | Destination. Always the final parameter. |
The destination is always shown in the URL, in the url parameter. It is the last parameter on purpose. Some platforms don’t escape & when they insert the final URL mid-template. So the link reads the destination as everything after url=. The final URL’s own query string, with its UTM tags, stays intact.
4. Redirect behaviour
For a valid request, the link returns one 302 Found whose Location is the decoded value of url. It is character for character the final URL the ad platform provided.
GET /c?cid=123&agid=456&clid=abc123&url=https%3A%2F%2Fwww.example.com%2Fshoes%3Fcolor%3Dred HTTP/1.1
Host: click.trafficboosters.net
HTTP/1.1 302 Found
Location: https://www.example.com/shoes?color=red
Cache-Control: no-storeIf the ad platform appends its own click identifier to the final URL, it does so itself. The link doesn’t add, remove or reorder any parameter.
5. Background tracking
Some ad platforms can load the final URL directly and request the tracking link separately, in the background (often called parallel tracking). The link returns exactly the same response in both modes. In background mode the visitor never waits for it, and it can’t influence the page they land on.
6. What the link never does
- Redirect to any address other than the one in the url parameter.
- Pick the destination from a server-side setting, campaign rule, split test or rotation.
- Return different responses based on user agent, IP address, location, referrer, fraud score or whether the request looks like a crawler or reviewer.
- Add, remove or rewrite query parameters on the destination, including UTM tags and affiliate identifiers.
- Chain additional redirects through third-party domains.
- Serve interstitial pages, content or scripts, or set cookies on the advertiser’s domain.
- Modify, frame, cache or proxy the advertiser’s landing page.
Traffic-quality scores are used only for reporting and for exclusions the advertiser controls. A click scored as invalid is redirected exactly like a click scored as valid.
7. Abuse & open-redirect protection
The link only accepts plain http and https destinations. Other schemes, addresses with embedded credentials and malformed URLs get 400 Bad Request and no redirect. Every click’s destination domain is logged. Domains reported for phishing, malware or spam are blocked, and links to them return 400 instead of redirecting. Report abuse to contact@trafficboosters.net.
8. Performance & reliability
The link runs on Cloudflare’s global edge network, close to the visitor. Recording a click is handed off asynchronously. If logging or scoring is degraded, the redirect is still served. Measurement never blocks a visitor from reaching the advertiser’s site.
9. Data collected
For each click we store: timestamp, IP address, user agent, referrer, Accept-Language, the parameters listed above, and the destination domain. We do not collect names, email addresses, form contents or payment information, and we do not track visitors across websites. Data is used only to monitor traffic quality and link health for the advertiser whose ad was clicked. It is never sold. See the privacy policy for retention periods.
10. Contact
Questions about the tracking link, policy reviews or abuse reports: contact@trafficboosters.net.