Pixels and location
Measure the scan, with the visitor’s say.
Turn on a retargeting tag or a location request for one code. Dotwick puts a short page with a consent banner in front of it. Nothing loads, and no position is asked for, until the visitor chooses.
- 01
Turn it on for one code
Pick the tags this code needs, or switch on location. Every other code keeps the instant redirect, so the rest of your printing is unchanged.
- 02
The visitor chooses
A short page in your name shows the banner. Every choice starts off, Reject all is as easy to press as Accept all, and a visitor who declines still reaches the destination.
- 03
Tags fire after the choice
Only the tags the visitor allowed load, and the destination opens a moment later. A choice remembered on the device skips the banner.
- 04
Send events from our servers
GA4 and Meta can also be sent from the server, still only with consent, so an ad blocker does not hide the scan.
What you control
- GA4, Google Tag Manager, a Meta pixel, Google Ads, a TikTok pixel and the LinkedIn Insight Tag, each optional.
- Your name and privacy policy on the banner, as the controller.
- A geofence: open a code only inside an area, or send everyone else to another page or a message.
- A map of the scans that agreed to share a location, and the consent rates, in your analytics.
Privacy first, the map included
A location is rounded to about 100 metres before it is stored, and kept for 90 days unless you choose another period. The map is an outline drawn on the page: no map tiles are loaded from anyone, so showing it shares nothing with a map provider. The visitor’s choice is remembered in one first-party cookie for 180 days that holds no identifier.
Where consenting scans were
Sample data. Each marker is a cell of about 100 metres with a count of scans, never a single scan.
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 |
|---|---|---|---|---|---|
| Retargeting tags with consent | — | — | yes | yes | yes |
| Server-side GA4 and Meta events | — | — | — | yes | yes |
| GPS location and the map | — | — | yes | yes | yes |
| Geofence | — | — | yes | yes | yes |
Questions.
- Does a visitor have to accept?
- No. Declining takes them to the destination all the same, and nothing about a refusal is kept beyond the choice itself.
- Does it slow down the scan?
- A code with tags or a location request shows the page before the destination, and hands on quickly even when a tag is slow. Codes without them redirect instantly, as before.
- Is the location stored exactly?
- No. It is rounded to about 100 metres first, and a fix that is too vague is dropped.
- Who is the controller?
- You are. The banner names your business and links your privacy policy; Dotwick processes the data for you.