Routy

Postback parameter not recognised

A network's postbacks reached us and matched their click, but the event in them has a name we do not accept, so nothing in those postbacks was counted.

What it means

A postback says which click it belongs to (clickId or dyn) and what happened, for example firsttimedeposits=1 or depositamount=50. We count only event names on our list.

These postbacks matched a click, but every event name in them was one we do not know. The issue names the network, the account, the name we did not recognise, and the names we accept, with an example of the request.

Extra parameters next to a recognised event, such as a currency or your own sub-IDs, are fine. This issue is raised only when a postback has no recognised event at all.

Why it happens

The event name in the network's postback URL is close to ours but not exact. Names are not case-sensitive, but spelling must match exactly, and we do not accept alternative spellings. Common cases:

  • firsttimedeposit instead of firsttimedeposits
  • ftd instead of firsttimedeposits
  • signup or registration instead of signups
  • deposit instead of depositcount or depositamount

Accepted names: signups, firsttimedeposits, cpacount, depositcount, depositamount, withdrawalcount, withdrawalamount, chargebacks, chargeback_amount, netrevenue, earning, cpacommission, revsharecommission, downloads, disqualified_signups, disqualified_ftd, disqualified_cpa_count, disqualified_cpa_commission. The issue lists the current names too.

What you can do

  1. Open the issue and note the network, the account, and the name we did not recognise.
  2. Sign in to that network and open the postback settings for that account.
  3. Find the postback for that event and rename the parameter to an accepted name. For example firsttimedeposit=1 becomes firsttimedeposits=1.
  4. Save. The next postback from that network is counted.

Postbacks already sent with the wrong name are not counted, even after the fix, and reloading them does not help because they still carry the old name. If you need those conversions, ask the network to resend them.

When it clears

It closes by itself 3 days after the last postback that used the unrecognised name. You can also press Resolve once you have renamed it. If another postback arrives with the same name, it opens again.