HowToDoAffiliateMarketing.com
← All guides
Tracking & troubleshooting

Affiliate Postback Not Tracking Conversions? Trace the Click ID First

Find the broken handoff before changing your campaign.

By HowToDoAffiliateMarketing.com · · 5 min read

The quick answer

If an affiliate network shows a conversion but your tracker does not, follow one click ID through the entire route: tracker, outbound offer URL, network record and returning postback. Check the actual values sent, then check the report dates. A saved postback template does not prove the network sent a usable conversion request.

1. Locate the missing event

Start with one conversion you can identify in the network report. Write down its event type, recorded time, timezone, offer and reference number. Then establish where the evidence stops.

What you can seeWhat to investigate next
No conversion in the networkWhether the qualifying action happened and was attributed. There may be no event for the network to send yet.
Network conversion, no tracker conversionOutbound click-ID storage, postback delivery and tracker acceptance.
Tracker conversion, no ad-platform conversionThe separate tracker-to-traffic-source integration.
Tracker conversion with the wrong revenuePayout mapping, currency and event selection.

Keep the traffic source’s identifier separate from the tracker’s click ID. Voluum documents these as different values: its own click ID matches the network conversion back to a visit, while an external ID can be used to report back to the traffic source. [4]

2. Check that the network receives the tracker’s click ID

In Voluum’s standard S2S setup, {clickid} inserts the tracker’s identifier into the offer URL. The network must receive it in a field it supports. That field’s name comes from the network’s documentation, not from guesswork. [1]

Illustrative configuration, not a universal template:

https://network.example/offer?offer_id=42&sub2={clickid}

Here, sub2 is an invented network field for this example. Your network may require another field entirely. Do not paste this example into a live campaign.

Open your campaign through its normal entry link. If it uses a landing page, follow the normal CTA to the offer. Inspect the outbound URL and, where the network exposes it, the stored sub-ID in its report.

In a functioning setup, the placeholder is replaced with a concrete identifier. If the URL still contains the literal text {clickid}, or the network field is blank, investigate that handoff before editing the returning postback.

If the URL looks right but the network record does not, give support the test click’s time and destination. Ask whether the field was accepted and retained. A value visible in a browser address is useful evidence, but it does not prove the network stored it.

3. Inspect the request the network actually sends back

Voluum’s documented postback uses cid for its click ID. The value in that field must be the identifier previously stored by the network. The network’s macro retrieves that stored value; it is not automatically the same macro that Voluum uses. [2]

Illustrative template:
https://tracker.example/postback?cid=NETWORK_MACRO_FOR_STORED_SUB2

Illustrative rendered request:
https://tracker.example/postback?cid=the-original-tracker-click-id

Both lines are explanatory examples. Use the postback generated for your tracker account and the network’s documented macro syntax.

If the network offers delivery logs, inspect the rendered request for the specific conversion. Otherwise, ask support for the request time, destination, supplied click ID and response.

Look for a blank identifier, an unexpanded macro, the network’s own unrelated identifier or a different tracker domain. Voluum’s Error Log documentation specifically connects invalid conversion requests with missing or incorrect click-ID values. [3]

4. Separate a tracker test from an end-to-end test

Voluum documents testing a postback with a valid click ID. This helps establish whether the tracker can accept a callback for that click. It does not establish whether the affiliate network automatically fires the callback after the intended action. [1]

Use an isolated test campaign where practical. Follow the network’s approved test process, or ask your affiliate manager to generate a test conversion. Avoid creating self-referrals unless the programme explicitly permits the test.

Hypothetical troubleshooting example: A campaign visit appears in the tracker. The network stores its identifier under sub2, but the callback template retrieves sub1. The returning cid is empty. Correcting the return macro addresses that mismatch. A fresh, permitted test is still needed to confirm the repair.

Record the outcome at each stage. If a tracker-only test succeeds and the network test fails, focus on the network’s event selection, stored field and delivery settings. If neither succeeds, inspect the endpoint and tracker error evidence first.

Mark or remove test events using the tools’ supported process before using the data to judge campaign performance. Repeatedly replaying requests can muddy the report you are trying to understand.

5. Check report dates before declaring the event missing

A conversion can be received today but attributed to an earlier visit. Voluum offers reporting based on visit time or postback time. Expand the date range to cover both and align the report timezones before comparing totals. [4]

Once the event appears, verify what it represents. A lead, registration and approved sale can have different meanings. Then check revenue: Voluum supports passing a payout value in the postback, but its payout configuration determines how that value is used. [2]

Do not treat a correctly recorded callback as proof of a payable commission. Tracking demonstrates a data connection. Approval and payment remain separate checks in the affiliate programme.

What this process cannot prove

This workflow diagnoses a standard click-ID-based postback route. It does not cover every app attribution integration, campaign-level fallback or direct tracking implementation. A network may also withhold logs or support only certain events. In those cases, document the last verified handoff and ask the platform responsible for the next one to investigate.

Your next step

Choose one missing conversion and build a four-line record: original tracker click ID, network’s stored field, rendered callback and tracker response or report result. Fix the first mismatch you can demonstrate, then rerun one controlled test before increasing spend.

Sources & further reading

Primary documentation checked 18 November 2026. Example URLs and the troubleshooting scenario are illustrative.

  1. Voluum: Track Conversions Using S2S Postback URL
  2. Voluum: Parameters in Postback URLs
  3. Voluum: Error Log
  4. Voluum: Frequently Asked Questions

Real Affiliate Case Studies Are Being Discussed Inside

See traffic angles, monetization breakdowns, and campaign ideas from affiliates testing what actually works.

Real case studies. Real traffic angles. Real discussions from affiliates testing what actually works.

See What Real Affiliates Are Discussing