Routy

Postbacks rejected: click reference unreadable

Some postbacks sent to your postback URL had a click reference we could not read, so we could not match them to a click and they were not counted.

What it means

Every postback has to tell us which click it belongs to, using one of two values:

  • clickId: the long click ID Routy created for the visit, for example a1b2c3d4-e5f6-7890-abcd-ef1234567890.
  • dyn: Routy's shorter tracking value for the same click, for example RT10000.

These postbacks had a value in clickId, dyn or both, but not one we recognise. Without a click we cannot tell which account, link or traffic source the conversion belongs to, so the postback was turned away. Rejected postbacks are not stored, so they do not appear on Events → Postbacks and cannot be reloaded later.

Because there is no click, the issue is attached to your postback URL rather than to an account. The issue's example request is the best clue to which network sent it.

Why it happens

Most common first:

  • The network sends its placeholder as typed. The value is literally {tracker}, SUBID, ${clickid} or subid1. The network does not recognise that placeholder, so it never swaps in a real value. Each network names its placeholders differently.
  • The network sends its own ID. The value is the network's transaction ID, a player ID, or an ad click ID such as a Google gclid, not the value Routy put in your tracking link.
  • The sub-ID the postback reads is not the one your tracking link fills. For example the postback sends {subid2}, but Routy's click ID goes into sub-ID 1.
  • clickId holds an unfilled placeholder, even though dyn looks right. We do not fall back to dyn in this case, so the postback is still rejected.

What you can do

The postback is built by the network that sends it, so this can only be changed in that network's postback settings. There is nothing to change in Routy, and our support team cannot change it for you.

If you want these conversions counted:

  1. Open the issue's details and look at the example request. Its other parameters and placeholders usually show which network sent it.
  2. Sign in to that network and open its postback settings.
  3. Make sure the placeholder in clickId= (or dyn=) is one that network fills, and that it reads the same sub-ID your tracking link uses to pass Routy's click ID. Remove any parameter the network cannot fill.
  4. Save, then send a test conversion if the network offers one. A correct postback appears on Events → Postbacks with a click and an account. See Postbacks event log.

Postbacks rejected before the fix are not recovered. Ask the network to resend them once the URL is right, if it can.

When it clears

It closes by itself 24 hours after the last rejected postback of this kind. You can also press Resolve. If another one arrives, it opens again.