One script on your own website. It measures what visitors do before the form, joins it to the requests and the signed quotes, and stores nothing on a visitor's device until they have agreed to statistics.
Put this line on every page, ideally in the <head>. The key is in the portal under Website → Install; it is public and identifies nothing but your site.
<script src="https://offerte.yourdomain.com/zv.js"
data-zv-site="YOUR_SITE_KEY"
defer></script>If your form lives on your own subdomain (offerte.yourdomain.com), use THAT address rather than app.zinevu.com. The measurement is then first-party: no blocklist knows the host, Safari does not shorten what it stores, and a visit is joined to its request without a parameter on any link.
All of this without configuring anything or writing a tag. Google Analytics sees most of it only if somebody builds a tag for it first.
This table is what belongs in your own cookie policy. Before a statistics decision there is nothing in it — that is not a caveat, it is the design.
| Name | Kind | What for | When | Retention |
|---|---|---|---|---|
zv_vid | Cookie (first-party, on your own domain) + localStorage | Recognises a returning visitor across days and joins a visit to a request. Holds a random number, no personal data. | Only after the visitor has accepted statistics cookies. | One year after the last visit. If the visitor withdraws consent, both copies are erased immediately. |
zv_vid_t | localStorage | The time of the last visit, so the retention above is true. | Alongside zv_vid. | Same. |
zv_test | sessionStorage | Silences this tab while testing. Holds only “1”. | Only when somebody types ?zv_test=1 into the address themselves. | Until the tab closes. |
Without consent the script still measures — but with a key derived on our server from the IP address and browser, renewed every day and never stored. Which means a visitor who returns tomorrow is a new visitor. That is the honest price of storing nothing, and the report says so beside the number.
The script reads the decision itself, or you hand it over. Three sources, in this order.
// in your own banner, on Accept
window.Zinevu?.consent({ statistics: true })
// and on Decline or Withdraw
window.Zinevu?.consent({ statistics: false })Calling consent() only after load is fine: the script waits, and does not read silence as a no.
Two ways to mark something we cannot guess.
<a href="/showroom" data-zv-track="showroom-button-hero">Visit our showroom</a>
<script>
window.Zinevu?.track("goal", { label: "brochure-downloaded" })
</script>Everything measured is also announced on your page. Your existing GA4, Ads or Meta setup can ride along for free.
document.addEventListener("zinevu:insight", (e) => {
// e.detail = { kind, label, url, page_group, href, at }
if (e.detail.kind === "click_tel") {
gtag("event", "phone_click", { label: e.detail.label })
}
})Open your site, watch your browser's network tab for a request to /api/zv/e and look for status 204. If it never appears, the script tag did not load or data-zv-site is wrong — the key is 24 characters and is in the portal.
Then the join between visit and form is the problem, not your site. The report says how many click-throughs could be matched, and warns below 60%. Serving the script from your own subdomain is what fixes it.
Almost always a proxy or firewall replacing the visitor's IP address. We would rather refuse to measure than show a thousand visitors as one person; get in touch and we will look at it.
Put your office IP in the portal under Forms → Ignored addresses. That same list applies to both reports, so you never type it twice.
Then there is nothing to do: route changes are noticed, and a page announced twice during hydration is counted once.
The key, the snippet and the status are in the portal under Website. Need help placing it? Send this page to whoever builds your website.