Mistake: clickid collisions from a non-unique generator

Mistake: clickid collisions from a non-unique generator

Failure mode: you generate clickid from a short value — a sequential counter, a timestamp to the second, or a small hash. At scale two clicks share an id, the second conversion attributes to the wrong click, and your source/creative breakdown is quietly poisoned.

Fix — 5 steps:
— Use the tracker's native clickid (Keitaro subid, Voluum click ID). It is built to be globally unique; do not roll your own.
— If you must generate ids, use a high-entropy UUID, never a counter or second-resolution timestamp.
— Never reuse ids across campaigns or days — uniqueness must be global, not per-campaign.
— Audit for collisions: group conversions by clickid; any id with two unrelated clicks behind it is a collision.
— Keep the id opaque. Encoding readable data into it tempts shortening, which kills entropy.

Verify: pull a day of clicks, count distinct ids against total clicks. They must be equal — zero collisions.

Save this SOP. Run this before every launch.