Skip to main content

Redtrack Conversion Tracking

Learn about server-to-server (S2S) postback conversions from RedTrack.io to Rumble Ad Center (RAC), including how to capture Rumble’s _raclid in RedTrack and how to build the postback.

Server-to-Server Conversion Postbacks​

Choose one method only: either the Rumble ad tag or S2S postbacks. Using both will double-count conversions for “track every conversion” actions.

What you'll need​

  • Rumble Conversion Action ID (caid): copy this from RAC’s Conversion Tracking page. Rumble Advertising Center
  • A Rumble click ID per visitor (_raclid): RAC appends this to your landing URLs automatically. You’ll capture it in RedTrack.
  • Your desired value token from RedTrack (e.g., {sum} or {offer_payout}), if you want to pass dynamic revenue. RedTrack Help

Step 1. Capture Rumble’s _raclid in RedTrack (map to RedTrack {ref_id})​

  1. In RedTrack, go to Traffic channels → New from scratch (create “Rumble” or similar).

  2. Open Additional parameters / aliases.

  3. Create a parameter alias for the incoming URL param _raclid and assign the role “Click ID” so it maps to RedTrack’s {ref_id} (this is RedTrack’s canonical “traffic source click id”).

    • From RedTrack docs: {ref_id} is the token that stores the traffic-source click ID; aliases/roles can be reassigned. RedTrack Help

  4. Save the traffic channel.

After completing these steps, any visit from RAC that hits your RedTrack link (or is tracked via RedTrack’s no-redirect setup) with ?_raclid=... will populate {ref_id} in reports and postbacks.

Step 2. Build the RedTrack → Rumble postback URL​

Rumble S2S endpoint accepts GET or POST and expects at minimum:

  • cid: the click/conversion ID (use the RAC _raclid you captured as {ref_id})
  • caid: your Rumble conversion action ID
  • Optional: value (USD), ip (end-user IP)

Rumble endpoint​

  • https://a.ads.rmbl.ws/v1/conversions
  • https://a.ads.rmbl.ws/v1/conversions?cid={ref_id}&caid=[YOUR_CONVERSION_ACTION_ID]&value={sum}&ip={ip}
  • {ref_id}: the RAC _raclid you mapped in step 1. RedTrack Help
  • <YOUR_CONVERSION_ACTION_ID>: paste your RAC caid. Rumble Advertising Center
  • {sum} (or {offer_payout}): choose your revenue token depending on how you store payout/value in RedTrack. RedTrack Help
  • {ip}: RedTrack token for the end-user IP. RedTrack Help

Rumble’s public examples show the same structure (cid, caid, value) in the query string for partner integrations. Rumble Advertising Center

Step 3. Important: About User-RumbleAdvertisingCenter​

  • The Rumble endpoint uses the HTTP User-Agent header (not a query parameter) to enrich device data.
  • RedTrack TS postbacks are typically GET URLs where you can’t set custom headers. That means adding &user_agent={useragent} to the URL will not be read by Rumble unless they explicitly accept a UA query param.
  • Good news: UA is optional; conversions still record without it. If you want UA accuracy, use one of the two patterns below.

Example of RedTrack tokens you may see:

  • {useragent}: RedTrack token that can expose UA as a value (but again, Rumble expects it as an HTTP header, not a query param). RedTrack Help

If you require User-Agent attributions​

Option A. Keep it simple: omit UA; send cid/caid/value/ip only.

Option B. Relay with headers: Point RedTrack postback to your tiny relay (Cloud Function / server) that:

Following option B preserves UA and keeps RAC attribution.

Step 4. Paste the postback into RedTrack (Traffic Source postback)​

  1. In RedTrack → Traffic channels → (your Rumble channel), locate Postback / S2S settings to traffic source.
  2. Paste your URL template, e.g. https://a.ads.rmbl.ws/v1/conversions?cid={ref_id}&caid=[YOUR_CONVERSION_ACTION_ID]&value={sum}&ip={ip}
  3. Select Save.

RedTrack notes you can pass payout to a traffic source via tokens like {offer_payout}; use whichever token represents your desired conversion value. RedTrack Help

Step 5. Verify end-to-end​

  1. Click flow: Launch a test click from RAC so your landing URL contains ?_raclid=....
  2. Check RedTrack: In Logs → Clicks, confirm ref_id is populated. If empty, ensure the _raclid alias is mapped to “Click ID”. RedTrack Help
  3. Fire a conversion in your flow (or simulate one) so RedTrack sends the S2S postback.
  4. Confirm in RAC: The conversion should show under your Conversion Action with the expected value.
  5. Optional: Use RAC’s Integration Test on the conversion action to generate a test click ID and validate your postback. (Feature referenced in RAC docs/videos.) Rumble Advertising Center

Step 6. Example​

Count-only conversion (no value)​

https://a.ads.rmbl.ws/v1/conversions?cid={ref_id}&caid=[YOUR_CONVERSION_ACTION_ID]

Dynamic value from RedTrack (choose one)​

https://a.ads.rmbl.ws/v1/conversions?cid={ref_id}&caid=[YOUR_CONVERSION_ACTION_ID]&value={sum}

or

https://a.ads.rmbl.ws/v1/conversions?cid={ref_id}&caid=[YOUR_CONVERSION_ACTION_ID]&value={offer_payout}

And IP if available:

...&ip={ip}

Rumble accepts both GET and POST; partners commonly use GET with cid, caid, value. Rumble Advertising Center

Step 7. Avoid duplicates​

If you used the Rumble ad tag previously, remove/disable it once S2S is live; otherwise you’ll double-fire for “Every” count conversions.

Step 8. Troubleshooting​

No conversions in RAC​

  1. Confirm cid is present (RedTrack {ref_id} was filled from _raclid).
  2. Confirm you used the correct caid. Rumble Advertising Center

Value is 0​

  1. Ensure your chosen token ({sum}, {offer_payout}, or another) actually contains a number for that conversion in RedTrack. RedTrack Help.

Geo/device looks generic​

  1. Add &ip={ip} (helps location). UA requires the header (see §3). RedTrack Help.

Audit in RedTrack​

  1. Check Postback/API logs and Clicks logs (ref_id column) to verify data is flowing. RedTrack Help.

Copy-paste templates​

Replace <YOUR_CONVERSION_ACTION_ID> with your RAC caid.

  • https://a.ads.rmbl.ws/v1/conversions?cid={ref_id}&caid=[YOUR_CONVERSION_ACTION_ID]&value={sum}&ip={ip}

Count-only​

  • https://a.ads.rmbl.ws/v1/conversions?cid={ref_id}&caid=[YOUR_CONVERSION_ACTION_ID]

With {offer_payout} instead of {sum}​

  • https://a.ads.rmbl.ws/v1/conversions?cid={ref_id}&caid=[YOUR_CONVERSION_ACTION_ID]&value={offer_payout}&ip={ip}

You can append a UA query like &user_agent={useragent}, but Rumble’s endpoint reads UA from the HTTP header, so the query param won’t be used. Use the relay workaround if UA is required. RedTrack Help, Rumble Advertising Center.

References​