Tracking Specifications

Get a complete overview of how AnyTrack tracks conversions across client-side and server-side channels. Covers the Tracking Tag, Click ID, standard events, event attributes, tag management, and advanced tracking methods.

AnyTrack tracks conversions using two channels that work together: a client-side Tracking Tag installed on your website and server-side integrations (webhooks, postbacks, APIs) that receive conversion data from affiliate networks, eCommerce platforms, and CRMs.

The Tracking Tag captures what happens in the browser: page views, outbound clicks, form submissions, UTM parameters, and first-party cookies. Server-side integrations capture what happens after the click leaves your site: purchases, commissions, lead status changes, and customer details that browsers cannot access. The Click ID ties both sides together, matching a server-side conversion back to the visitor session that started it.

Every tracked event is automatically mapped to each connected ad platform's format and forwarded via Conversion API, giving Facebook, Google, and TikTok the signals they need to optimize campaigns.

Core Tracking Components

These are the building blocks of the AnyTrack tracking system. Each handles a specific part of the data pipeline, from collecting raw visitor interactions to delivering enriched conversion signals to ad platforms.

Events and Conversion Data

AnyTrack uses a standard set of event names that map automatically to each ad platform. You can also define custom events, enrich them with detailed attributes, and combine multi-step transactions into a single order.

Tracking Methods and Tag Management

AnyTrack supports multiple tracking methods for different scenarios: link clicks, form submissions, page views, A/B tests, offline conversions, and more. The built-in tag management loads ad platform tags (Meta Pixel, Google Tag, TikTok Pixel) with the correct identifiers so data collection works without manual tag setup.

How the Pieces Fit Together

A typical tracking flow moves through four stages:

  1. Capture: A visitor clicks an ad and lands on your site. The Tracking Tag records UTM parameters, ad platform click IDs (gclid, fbclid, ttclid), and first-party cookies. A session starts.

  2. Identify: The visitor interacts with your page. When they click an affiliate link or submit a form, AnyTrack generates a Click ID and attaches it to the outbound action via AutoTag. This identifier follows the visitor off-site.

  3. Match: A conversion happens on an external platform (affiliate network, eCommerce checkout, CRM). The platform sends conversion data back to AnyTrack through a webhook or postback that includes the Click ID. AnyTrack matches the conversion to the original session.

  4. Distribute: AnyTrack enriches the matched conversion with event attributes (customer email, product value, transaction ID) and sends it to every connected ad platform via Conversion API. Each platform receives the event in its own format with the matching parameters it needs.

The result: a single tracked conversion flows from your ad click through your funnel to every ad platform that needs it for optimization, without duplicate setup per platform.

📘

Note

For most integrations, this flow is fully automatic. Connect a conversion source (like Shopify or an affiliate network), install the Tracking Tag, and AnyTrack handles the rest. Manual Click ID implementation is only needed for custom platforms not in the Integration Catalog.

Tracking Specs FAQ

FAQ was last reviewed on 2026-04-15

No. AnyTrack tracks conversions once and distributes them to all connected ad platforms automatically. Each platform receives the event in its own expected format via Conversion API. You connect the ad platform in AnyTrack, and event mapping handles the translation.
Client-side tracking uses the AnyTrack Tracking Tag in the browser to capture page views, clicks, form submissions, and cookies. Server-side tracking receives conversion data directly from platforms (Shopify, affiliate networks, CRMs) via webhooks or postbacks. Server-side data survives ad blockers and browser privacy restrictions that would otherwise block client-side signals.
When a visitor clicks an affiliate link on your site, AutoTag appends the AnyTrack Click ID to the outbound URL. When the affiliate network records a conversion, it sends a postback containing that Click ID back to AnyTrack. AnyTrack matches it to the original visitor session, which already has the ad platform click ID and UTM data attached, completing the attribution chain.
Server-side data from webhooks and postbacks will still reach AnyTrack. However, without the Tracking Tag, there is no client-side session data to match against. Conversions will not be attributed to specific ad clicks or visitor sessions. The Tracking Tag is required for full attribution.
AnyTrack automatically deduplicates events before forwarding them to ad platforms. If the same conversion arrives from both the browser and a webhook, AnyTrack sends only one event to each ad platform. See the Deduplication article for details.

What’s Next

Learn how AnyTrack collects first-party and event data