Campaign setup
Click ID / SubID generator
Batches of unique IDs — UUID, NanoID, timestamp or a custom pattern — for testing a tracker–network integration or seeding test data.
Options
“Length” applies to the custom format only. Max 10,000 per batch. IDs are not stored — they disappear on reload.
Result
Frequently asked questions
What is a Click ID and why does it matter?
A unique identifier attached to every click. The tracker generates it, passes it to the landing page and on to the network, and the network sends it back in the postback so a conversion can be tied to its exact source, campaign and creative.
If the tracker generates IDs, why generate them here?
For testing. Wiring up a new tracker–network integration usually needs IDs known in advance — to fire a test postback, to check the network stores the value, or to print IDs on offline and QR campaigns.
Click ID, SubID, transaction_id — are they the same?
Click ID and SubID usually mean the same thing: the id your tracker assigns to a click. transaction_id is the network’s own id for the conversion, used on their side for deduplication. Both travel in the postback URL.
UUID or NanoID — which format?
UUID v4 is the universal standard and collision-safe at any realistic volume. NanoID is shorter (21 chars) and URL-safe, which keeps postback URLs tidy. Use UUID unless URL length is a concern.
What is a timestamp-based ID?
It encodes the current time (base-36) plus a short random suffix. IDs sort chronologically and are easy to eyeball for “when”, but they leak the creation time and are not suitable where unpredictability matters.
Are the generated IDs unguessable?
UUID v4, NanoID and the custom format use the browser crypto RNG, so they are practically impossible to guess. Timestamp-based IDs are partly predictable by design — do not use them as a security token.
Can I generate and export in bulk?
Yes — up to 10,000 per batch, with copy-all, TXT and CSV export. The CSV has a single click_id column so it drops straight into a spreadsheet or a test-data import.
Do you store the IDs I generate?
No. Generation happens entirely in your browser and nothing is sent to the server. The list is gone as soon as you reload or close the page.