Click ID sent in the wrong place (auto-corrected)

A network sent Routy's click ID in the dyn part of its postbacks instead of clickId. We found it there and counted the conversion, so nothing was lost.

What it means

A postback to Routy carries the click it belongs to in one of two places:

• 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 the long click ID in dyn, and clickId was empty or held something we could not use. We used the value from dyn as the click ID, matched the click, and recorded the conversion.

Why it happens

The network's postback URL puts the click ID placeholder in the wrong parameter. Common shapes:

• ?dyn={clickid} with no clickId= at all.
• ?clickId={subid}&dyn={clickid}, where {subid} is a placeholder the network does not fill.

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. Move the placeholder that carries Routy's click ID into clickId=. If nothing else belongs in dyn=, remove it.
4. Save. You can compare with the URL that Generate builds on Events → Postbacks. See Postbacks event log.

When it clears

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