Routy

Postback values swapped (auto-corrected)

A network sent postbacks with its two click values in each other's places. We swapped them back and counted the conversion, so nothing was lost.

What it means

A postback to Routy can carry two values that tell us which click it belongs to:

  • 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.

In these postbacks, the click ID arrived in dyn and the tracking value arrived in clickId. We recognised both values, put them back in the right places, matched the click, and recorded the conversion.

The issue is attached to the account the click belongs to.

Why it happens

The postback URL saved at the network has the two placeholders the wrong way round. For example, the network's postback URL reads ?clickId={subid2}&dyn={subid1} when {subid1} is the sub-ID that holds Routy's click ID.

This usually happens when the URL was copied from another network, or the sub-IDs in your tracking link were reordered after the postback was set up.

What you can do

Your conversions are being counted, so this is not urgent. To stop the issue coming back:

  1. Open the issue's details and copy the example request. It shows exactly what the network sent.
  2. Sign in to that network and open its postback settings for the account named in the issue.
  3. Swap the two placeholders so the one carrying Routy's click ID goes in clickId= and the other goes in dyn=.
  4. Save. To check the result, use Generate on Events → Postbacks to see the postback URL Routy expects. See Postbacks event log.

When it clears

It closes by itself 3 days after the last postback that arrived swapped. You can also press Resolve once you have fixed the network's settings. If another swapped postback arrives, it opens again.