ExoClick conversion tracking: goals, IDs, and postbacks

ExoClick conversion tracking needs a Conversion Goal and the full click ID generated by {conversions_tracking}. For S2S tracking, your sender returns that stored ID as tag, the goal ID as goal, and dynamic revenue as value when configured. An affiliate-network postback into Tracked is a separate handoff, using Tracked's own click ID. Tracked supports capture and inbound conversions; a native or automatic ExoClick outbound workflow is not verified.

A conversion in your tracker and a conversion in ExoClick are separate records. Set up each handoff before relying on the two reports to agree.

Create the ExoClick goal before configuring a postback

ExoClick's conversion-tracking documentation starts with Campaigns → Conversion Tracking → New Conversion Goal. Create the goal first, then select its tracking method.

These settings determine what the conversion means in ExoClick:

Goal setting	What to choose	Why it matters
Name	A recognizable business event, such as an approved lead	Helps distinguish funnel stages in reports
Conversion type	The required offer category, such as Lead - Single Opt In or Purchase - Credit Card	Describes the offer; it is not a tracker event macro
Conversion Value	No Value, Fixed, or Dynamic	Controls the amount associated with the goal and used for revenue, profit, and ROI
Count	One conversion or Every conversion	Determines whether repeated notifications for the same conversion ID can count again
Conversion Window	A window matching the expected delay between ad interaction and conversion	A late callback outside the window is rejected
Order	The goal's display position	Changes column placement, not which event should trigger the goal

The default conversion window is 24 hours. Documented choices include 12 hours, 2, 3, 7, 30, or 90 days, plus custom whole-day values from 1 to 90.

Choose One conversion when the goal represents a single qualifying action per source ID. Choose Every conversion only when repeated conversions are intentional. Do not use it to hide duplicate callback delivery.

For separate lead and sale stages, define which event should notify which goal. Do not treat ExoClick's Order setting as an event selector. Goals with the same Order are displayed oldest first.

Click Create, then choose Conversion Tracking API - S2S, ExoClick's recommended method for server notifications. Copy the postback generated for your goal. Its goal ID is a 32-character hexadecimal string, not a goal name, campaign number, or tracker click ID.

Preserve the complete ExoClick source ID

In the ExoClick campaign's Step 2 - Ads, use +Add Tokens beside the campaign URL. Add {conversions_tracking} under the query parameter your receiving tracker captures.

Generic arrival example, not a shipped Tracked connector:

https://tracker.example/campaign?exotracker={conversions_tracking}

exotracker is an example parameter name from ExoClick's documentation. It is not mandatory. The receiving tracker's configuration determines the correct key.

ExoClick replaces {conversions_tracking} with a unique source ID on the ad click. Its documented length is 150–700 characters. Preserve the entire value through capture, storage, and outbound URL construction. Truncating it to fit a short sub-ID field breaks the return path.

Available Tracked capture layer: a custom platform's Click ID Parameter identifies the incoming query key to read. For the example above, use exotracker and associate the campaign with that platform. Tracked stores the captured platform click ID separately from its own click ID. Configure the ExoClick arrival token explicitly; a generic URL placeholder is not proof of correct source expansion.

This captures an input. It does not establish automatic ExoClick delivery. Destination parameter passthrough in Tracked is macro-driven, not an assurance that every incoming parameter survives every redirect.

Keep the source ID, tracker ID, and goal ID separate

The source ID identifies the ExoClick ad interaction. The tracker ID identifies the tracked offer click. The goal ID identifies the ExoClick conversion action you created.

Value or field	Meaning	Required mapping
{conversions_tracking}	ExoClick's campaign URL token	Expands into the source ID captured on arrival
exotracker	Example arrival query key	Must match the receiver's configured source-ID parameter
Tracked {{click.id}}	Tracked offer-click macro	Goes into the affiliate network's documented sub-ID field
Tracked inbound click_id	Lookup key for the recorded Tracked click	Receives the saved Tracked ID from the affiliate network
ExoClick outbound goal	The selected conversion action	Receives the goal's 32-character hexadecimal ID
ExoClick outbound tag	The original ExoClick source ID	Receives the full stored {conversions_tracking} result
ExoClick outbound value	Dynamic conversion amount	Receives the intended monetary value when the goal uses Dynamic

The word tag can also appear in a tracker's arrival URL. That does not make it a universal input convention. ExoClick's official Voluum manual uses tag={conversions_tracking} on arrival, while the generic guide uses exotracker.

Record the affiliate-network conversion in Tracked

This is the affiliate network → Tracked handoff. Send the Tracked offer-click ID to the network, not the long ExoClick source ID.

Tracked macro with an illustrative network parameter:

https://offer.example/landing?sub1={{click.id}}

Use a tracked offer action such as /click/N so the offer redirect inserts that click's ID. Replace sub1 with the network's documented sub-ID parameter.

Configure the network to return its saved Tracked ID:

https://YOUR_TRACKED_DOMAIN/postback?click_id=NETWORK_TOKEN_FOR_TRACKED_ID&payout=NETWORK_PAYOUT_TOKEN

The capitalized values are explanatory placeholders, not working macros. Use the affiliate network's actual output syntax.

For Tracked's primary sale callback, omit both type and conversion_type. Configure the Offer's implicit default event. Explicitly typed callbacks are secondary funnel signals and currently record zero payout, even if they contain payout. ExoClick goal selection is a separate mapping; adding a goal-like type to this callback does not configure outbound delivery.

The postback URL guide explains the inbound fields. Once this handoff records a conversion, you still need an outbound sender to notify ExoClick.

Map the outbound ExoClick postback using the sender's syntax

ExoClick documents an HTTP GET notification to this endpoint:

http://s.magsrv.com/tag.php?goal=GOAL_ID&tag=STORED_EXOCLICK_ID

For a goal configured with Dynamic value:

http://s.magsrv.com/tag.php?goal=GOAL_ID&tag=STORED_EXOCLICK_ID&value=CONVERSION_AMOUNT

These are explanatory templates, not executable callbacks or Tracked macros. Copy your own goal's generated URL. ExoClick explicitly says its postback domain changed to s.magsrv.com; do not copy an obsolete host from an old setup article.

The official examples use HTTP, not HTTPS. This research does not verify an HTTPS alternative. Tracked's provider-endpoint validation requires HTTPS, so resolve that compatibility boundary before configuring outbound delivery. Do not silently change the scheme or assume a generic custom-postback field makes the documented endpoint compatible.

The official ExoClick Voluum manual provides a concrete sender-specific example:

http://s.magsrv.com/tag.php?goal=GOAL_ID&tag={externalid}&value={payout}

Here, {externalid} and {payout} are Voluum output tokens. They are not ExoClick arrival macros or Tracked syntax. The manual instructs users to replace the template's goal placeholder with their goal ID and add value for Dynamic goals.

ClickFlare's own ExoClick guide instead documents {external_id} for its stored source ID. That underscore matters. Neither tracker's recipe establishes a Tracked feature.

Map the affiliate payout or intended conversion amount deliberately. Ad spend is not conversion value. A numeric payout recorded in Tracked does not automatically populate ExoClick's value field.

Choose S2S or pixel tracking for the event you can observe

Situation	Setup decision
An affiliate network can notify your tracker, but you cannot edit checkout	Use the network's inbound callback and a separately supported S2S sender for ExoClick
You control the confirmation page	ExoClick offers a pixel script as another tracking method; copy it from the goal
You need separate lead and purchase signals	Define separate event-to-goal mappings rather than sending every event to one goal
A tracker records sales but has no verified ExoClick sender	Treat tracker reporting as available and ExoClick feedback as unresolved

ExoClick's documented pixel loads https://a.magsrv.com/tag_gen.js, uses data-goal for the goal ID, and adds data-value for Dynamic goals. It belongs in the page's body. That HTTPS script URL is not evidence that the S2S endpoint accepts HTTPS.

A pixel also requires access to the relevant page and appropriate privacy handling. It does not replace the affiliate-network callback that records conversions in Tracked.

Troubleshoot the ID or goal boundary that failed

ExoClick documents these response bodies for its S2S endpoint:

Response or symptom	What to inspect
OK	ExoClick says the conversion was registered; inspect the intended goal's reporting column
ERROR: Tag is invalid!	Wrong ID, truncated source ID, or a literal unexpanded token
ERROR: No tag data.	Missing source ID in tag
ERROR: Goal ID is invalid.	Goal ID must be 32 hexadecimal characters
ERROR: No Goal ID.	Missing goal or goal/tag data in the generated callback
ERROR: This conversion has already been notified and saved.	A repeated source ID for a goal counting One conversion
ERROR: Conversion window is not respected.	Notification arrived outside the configured window
Tracked returns 404 for the inbound callback	The inbound click_id does not resolve to a recorded Tracked offer-click ID
Tracked shows a sale; ExoClick shows none	Confirm an outbound sender exists before changing inbound callbacks
ExoClick conversion appears missing from the table	Enable the corresponding goal column in Campaigns List and Statistics

Goal Order controls display position. The official Voluum manual specifically reminds users to enable the relevant goal columns. A hidden column is not evidence of a failed callback.

For a setup review, trace the expanded arrival ID, stored tracker ID, inbound conversion, outbound mapping, and goal response separately. Avoid resending notifications merely to make a report change: an Every conversion goal can count repeated calls. See postback troubleshooting for the inbound side.

Where Tracked is today

Tracked supports custom platform click-ID capture, tracked offer-click macros, inbound conversion postbacks, reports, and event journeys. These let you distinguish the ExoClick source ID from the click ID returned by an affiliate network.

A native or automatic ExoClick outbound workflow is not verified. This article does not establish automatic goal delivery, ExoClick spend sync, API campaign controls, or compatibility with the documented HTTP callback. A generic postback template is not a shipped provider connector.

If ExoClick goal feedback is required before moving campaigns, confirm the exact sender, supported endpoint, event-to-goal mapping, and value handling first. Read native integrations versus postbacks versus conversion APIs to separate these connection layers.

Frequently asked questions

What is ExoClick's conversion-tracking token?

{conversions_tracking} is the campaign URL token. ExoClick expands it into a 150–700-character source ID. Capture the complete result under the receiving tracker's configured parameter.

What is the difference between goal and tag?

goal selects the ExoClick Conversion Goal using its 32-character hexadecimal ID. tag contains the stored source ID generated for the ad interaction. Neither field should contain Tracked's offer-click ID.

Does a conversion recorded in Tracked automatically reach ExoClick?

No automatic ExoClick delivery is established here. The affiliate network's callback records the conversion in Tracked. Outbound ExoClick notification requires a separately supported sender and mapping.

When should I add value to the ExoClick postback?

Add value when the goal uses Dynamic conversion value. Substitute the sender's documented payout or amount token. No Value and Fixed goals use their own configured value behavior.

Can I copy Voluum's externalid token into Tracked?

No. {externalid} is Voluum-specific syntax in ExoClick's official manual. ClickFlare documents {external_id} instead. Use only the actual sender's documented output token for the stored ExoClick ID.

Sources and update history

Published and source-checked October 28, 2026. Documentation review only; no real conversion callbacks were sent.

• ExoClick: Conversion Tracking — goal settings, source ID length, current endpoint, HTTP GET syntax, response bodies, and pixel fields.
• ExoClick: Voluum tracking manual — sender-specific {externalid} and {payout} mapping, separate network callbacks, and goal-column visibility. Use the main conversion guide for the fuller current goal settings.
• ClickFlare: ExoClick as a traffic source — secondary implementation reference for ClickFlare's {external_id} syntax, not evidence of Tracked integration support.

Start free with one page you own and one offer. Inspect the network-to-tracker click and conversion journey before moving paid traffic. Signup does not establish automatic ExoClick conversion delivery.