Conversion Logic

Understand how AnyTrack processes raw conversion data from affiliate networks, eCommerce platforms, and lead gen tools, then maps it to standard events that ad platforms can optimize against. Covers the data flow from source to ad platform, event normalization, deduplication, and how attribution is maintained across the chain.

Every conversion that reaches AnyTrack goes through a processing pipeline before it arrives at your ad platforms. This pipeline normalizes data from dozens of different sources into a consistent format, attributes each conversion to the right traffic source, and routes it to the correct destinations. Understanding this flow helps you troubleshoot tracking gaps and configure your integrations correctly.

The Conversion Data Flow

Conversion data enters AnyTrack from two paths:

Client-side (Tracking Tag): The Tracking Tag captures user interactions directly on your site. Link clicks, form submissions, and checkout events are detected by AutoTrack and sent to AnyTrack servers in real time.

Server-side (Postback and API): Affiliate networks, eCommerce platforms, and CRM systems send conversion notifications to AnyTrack through postback URLs, webhooks, or direct API connections. These arrive after the conversion happens, sometimes minutes or hours later.

Both paths feed into the same processing pipeline:

Source Event → AnyTrack Ingestion → Normalization → Attribution → Event Mapping → Ad Platforms

Step 1: Normalization

Every integration sends data in its own format. ClickBank calls a sale “SALE”, ShareASale sends “transaction”, Shopify sends an order webhook with line items. AnyTrack normalizes all of these into standard events like Purchase, Lead, or AddToCart.

This normalization happens automatically based on the integration type. You don’t configure it manually. When a ClickBank IPN arrives with a sale notification, AnyTrack knows to map that to a Purchase event with the correct revenue value and currency.

If you need to override the default mapping or send custom event names, you can configure that through event mapping in your property settings.

Step 2: Attribution

Once the event is normalized, AnyTrack matches it to the original visitor session. This is where the Click ID (atclid) becomes critical.

For client-side events, the Click ID is already attached because the Tracking Tag generated it during the page visit. For server-side events (like an affiliate network postback), AnyTrack matches the Click ID that was passed through the affiliate link back to the original session.

This matching process connects the conversion to:

The traffic source (Google Ads, Facebook, organic, etc.)
The specific campaign, ad set, and ad
The landing page and referrer
Any UTM parameters from the original click

Without a valid Click ID match, AnyTrack cannot attribute the conversion. This is the most common reason for missing conversions in ad platforms. See the troubleshooting guide if you suspect attribution gaps.

Step 3: Event Mapping and Routing

After attribution, AnyTrack checks your event mapping configuration to determine which ad platforms should receive this event and how it should be named on each platform.

For example, a single Purchase event from ClickBank might be sent to:

Destination	Event Name	Format
Facebook CAPI	Purchase	Server-side API call
Google Ads	purchase	Google Ads API conversion
TikTok	CompletePayment	TikTok Events API
Google Analytics 4	purchase	GA4 Measurement Protocol

Each platform receives the event in its native format with the correct parameters. AnyTrack handles all the translation automatically.

Step 4: Deduplication

AnyTrack prevents the same conversion from being counted twice. If both your Tracking Tag and a server-side postback report the same transaction, deduplication catches it and only forwards one event to your ad platforms.

Deduplication uses transaction IDs, timestamps, and event fingerprints to identify duplicates. This protects your ad platform data from inflated conversion counts that would distort campaign optimization.

Revenue and Currency Processing

When a conversion includes a revenue value, AnyTrack preserves the original amount and currency. If the source sends revenue in EUR but your property is configured for USD, AnyTrack converts the value automatically. See Conversion Tracking Revenues for details on how revenue aggregation works.

Event attributes like product name, quantity, and transaction ID are also preserved and forwarded to ad platforms that support them. Richer event attributes improve Event Match Quality and give ad platforms more signals for optimization.

Conversion Logic FAQ

FAQ was last reviewed on 2026-06-10

How fast does AnyTrack process conversions?

Client-side events from the Tracking Tag are processed in under 2 seconds. Server-side postbacks and webhooks are processed as soon as they arrive, typically within 1-5 seconds of receipt.

What happens if a conversion arrives without a Click ID?

AnyTrack cannot attribute the conversion to a traffic source without a valid Click ID. The event is still logged in your Integration Event Log, but it will not be forwarded to ad platforms. Check that AutoTag is active and the Click ID is being passed through your affiliate links.

Can I change how events are mapped after they have been processed?

Event mapping changes apply to future events only. Previously processed conversions are not reprocessed. Update your event mapping in the property settings under the Ads Integrations section.

Why do I see a conversion in AnyTrack but not in my ad platform?

The most common causes are missing Click ID attribution, disabled event mapping for that platform, or the ad platform rejecting the event due to low Event Match Quality. Check the Integration Event Log for the specific event status and error details.