Guides
Links and the click id
Every link in an Uncart message is built by Uncart. Your system never sends a finished address to put in a message. A link starts as a short Uncart address, and when the shopper taps it, Uncart records the tap and sends them on to the page on your domain, with its click id added.
Which destinations Uncart accepts
Uncart checks a destination when the link is made. It must be an absolute https:// address whose host is exactly one of your verified domains. A subdomain needs its own verification.
The rest of the address is held to these rules.
- No user name or password, no port other than 443, and no
#fragment. - A path of at most 1,024 characters, with no
.or..segment, no empty segment (//), and no encoded dot, slash or backslash. - At most 20 query parameters, each named once and each value at most 200 characters. A value may not itself be an address.
- The whole address at most 1,900 characters as written.
Only these query parameters are allowed. Anything that could send the shopper elsewhere, like url, redirect or next, is refused.
| Parameters | For |
|---|---|
variant, variant_id, product_id, sku | The product and its variant |
quantity, qty, size, color, colour | What the shopper chose |
lang, locale, currency, country | The shop's language and market |
utm_source, utm_medium, utm_campaign, utm_content, utm_term | Your own campaign tracking |
The click id
When the shopper taps, they arrive on your page with one more parameter at the end, uc_click. Its value is Uncart's click id for that link, the same on every tap of it: 43 characters of letters, digits, - and _. A destination that already carries uc_click is refused, because only the redirect may set it.
A page reached from an Uncart message therefore looks like https://shop.example.com/products/trail-runner?variant=42&uc_click= followed by the 43 characters.
When the shopper orders, the order you report to Uncart carries that click id. Uncart matches it to the tap, and that match is what your shop is billed on. An order is billed only when it was placed within 3 days of the tap.
The redirect sets no cookie. The click id is in the address, and nowhere else, until your page keeps it.
Keeping the click id needs consent
A shopper often moves through several pages before they buy. Keeping the click id in their browser until then, in a cookie, localStorage or sessionStorage, stores information on their device. That needs their consent first.
So without consent, don't write the click id to the browser and don't read an old one back. The only click id an order may carry is then the one in the address of the page where the order is placed. With consent, keep the click id from the landing page and read it back at checkout. When the shopper withdraws consent, delete it.