RedTrack Conversions API: One Conversion, Several Platforms

The RedTrack conversions API setup answers a question every media buyer eventually asks: one funnel produces one conversion, but three ad platforms sold the clicks - how do all three hear about it without the events turning into a mess? RedTrack's answer is configuration: S2S postbacks bring conversions in, CAPI integrations send them out per platform, and the clickid token guarantees each conversion stays a single, matchable fact. This guide walks that multi-platform setup with the documented fields, the matching rules, and the pitfalls that create duplicates.

Underneath, the general contour - network postback in, server event out - is the chain described in the postback-to-CAPI guide; here it is RedTrack's implementation, platform by platform.

The Token That Makes It Work: clickid

RedTrack assigns "a newly generated unique ID for this session" to every click. The offer URL carries a macro - &affsub={clickid} in the documented example - so the affiliate network stores RedTrack's click ID and returns it in its postback when the user converts (RedTrack postback documentation).

The receiving side is the offer source setup, keyed by the click ID: with a network template, you copy the generated postback URL into the network's settings; from scratch, you create a custom offer source and "clarify the correct CLICKID and SUM macros essential for tracking." That postback URL then carries the identifier (clickid), optionally the event type (&type=conversion event name), and the conversion amount via the SUM macro. Notably, RedTrack documents S2S as cookie-free - "does not rely on cookies" - which is what makes the whole contour robust on junk-hostile browsers.

Inbound: S2S Postbacks From the Network

Setup splits by network capability:

1. With a template: add the offer source template, copy the postback URL from settings, paste it into the network's postback field - macros pre-mapped.
2. Custom from scratch: define the CLICKID and SUM macros to match the network's own parameter names, then paste the generated URL.

Conversion types registered through the type parameter become reportable columns, and they become the raw material for the platform integrations: each platform event RedTrack sends is built from a matched conversion of a given type.

Outbound: CAPI Integrations per Platform

Meta's integration documents the field set every platform variant follows: Pixel ID, API key (the CAPI access token), a default event name - blank means conversions are sent as Purchase - a default Event URL, and an Action source, which the documentation marks as required "or conversions fail." Optional additions include a Data Quality API Token for Event Match Quality scores, Custom Conversion Matching (mapping RedTrack conversion types to Meta event names), payout customisation, and payout-threshold postback filters (RedTrack Meta integration).

Multi-platform means this section repeats: a TikTok integration from the TikTok template carries its own credential and event mapping (TikTok integration), and each additional platform adds its own row. One conversion, matched once, delivered to every configured platform - each in that platform's vocabulary.

Meta-Specific Requirements That Shape the Setup

Meta's requirements reach back into the landing setup, and RedTrack documents them precisely:

1. A custom tracking domain (CNAME, Free SSL on) with no-redirect tracking - redirects are not allowed on Meta traffic by default.
2. If you must redirect: the Redirect for Meta toggle plus the clickupd_fbp_fbc.js script - the documented combination for carrying browser identifiers across a redirect.
3. Parameter roles: fbclid is "required for sending the conversion data back to Meta" and must be the last parameter in the ad URL; sub 19 and sub 20 are hard-coded to fbp and fbc and must not be edited, "as CAPI requires them in exact format"; the Meta macros carry required roles - {{ad.id}} as Aid, {{adset.id}} as Gid, {{campaign.id}} as Cid - and the External ID role forwards a deduplication value (RedTrack's clickid by default).
4. Connection maintenance: authorize via Connect Meta and reconnect every 2-3 months, as Meta drops connections.

Each of these is a documented configuration item, not a workaround - the identifier mechanics behind them are covered in the click ID guides.

Dedup: The One-Pixel-One-Home Rule

The sharpest edge of the multi-platform setup is double assignment: RedTrack's documentation states it plainly: assign the pixel to either the traffic channel or the offer/store - "both causes duplicate events." The same problem class appears in every tracker: one conversion with two delivery routes becomes two platform events unless the platform's own cross-channel dedup catches them - and cross-channel dedup only works when both copies share identity.

The external ID role remains as the defense: with a stable external ID per conversion, Meta can deduplicate browser-and-server pairs; within server-only delivery, the routing rule above is what keeps counts honest.

RedTrack Conversions API: Frequently Asked Questions

Sources