Conversions
From scan to sale.
See which scans led to a visit, a sign-up or an order. A signed click id travels from the scan to your site, a small script or your own server reports the goal, and the funnel shows scans, visits, conversions and revenue for every currency.
- 01
Register your site
Add up to 20 websites by hostname. Each one gets a public pixel key and, for reports from your server, a secret that is shown once.
- 02
Scans carry a click id
When a code points at one of your sites, the redirect adds a signed dw_sid to the address. Nothing else about the visitor travels with it.
- 03
Report the goal
Paste the pixel on your site, or send the conversion from your server. Name the event (purchase, lead, sign-up or one of your own, up to 20 goals), and add a value and a currency if it has one.
- 04
Read the funnel
Scans, visits and conversions by code, folder or tag, with revenue shown for each currency separately. The last scan inside the window gets the credit: 30 days by default, up to 90.
What you control
- Consent first: by default the pixel sets no cookie and sends nothing until your site’s consent tool says yes.
- A Global Privacy Control signal is always treated as a refusal.
- One first-party cookie on your own domain, holding only the click id.
- A server postback for orders your site records itself, and Shopify for revenue by code.
- Amounts are never converted between currencies: each one is reported as it was paid.
No personal data, by design
A conversion carries no name, email, phone number or address: the API refuses them, even inside a note. No IP address is stored, no fingerprint is taken, and nothing is shared between sites. You are the controller and we process the data for you; the docs give you a paragraph for your privacy notice.
Which plans have it
This table is read from the plans themselves, so it is always the current one.
| Feature | Free | Starter | Pro | Business | Enterprise |
|---|---|---|---|---|---|
| Conversion pixel, server postback and funnel | — | — | — | yes | yes |
| Revenue by code and the Shopify app | — | — | — | yes | yes |
Questions.
- Do I need a cookie banner for this?
- If your site already asks for consent, connect it to the pixel and it follows the answer. If you turn the consent setting off, you are stating that you have another legal basis for it, and that choice is recorded in your audit log.
- Does the click id slow the redirect down?
- No. It is one signature added on the way through, and nothing waits for the conversion side.
- Can I track without the pixel?
- Yes. Keep the click id from the landing address and send the conversion from your server when the order is confirmed.
- What if someone scans twice?
- The last scan inside the window gets the credit, and a newer scan replaces an older one.