Install the tracker
Add one script tag and start collecting pageviews, channels and landing pages
The FullVision tracker is a small script you add to your website. It records each pageview and remembers which visitor it belongs to, so every later payment can be traced back to the traffic that produced it.
Use it when you are setting FullVision up for the first time — this is step one, and on a marketing site it is often the only step you need.
Add the snippet
Copy the snippet from the dashboard's Setup page. It arrives with your
publishable key and your cookie domain already filled in. Paste it as high in
<head> as you can, on every page of your site. It looks like this:
<script nowprocket>(function(){var n="fv_visitor_id",d="",m=document.cookie.match(/(^| )fv_visitor_id=([^;]+)/),id=m?m[2]:(function(){try{return localStorage.getItem(n)}catch(e){return null}})();if(!id){id="fv_"+Math.random().toString(36).slice(2)+Math.random().toString(36).slice(2);var h=location.hostname,seg=(d&&(h===d||h.endsWith("."+d)))?"; Domain="+d:"";document.cookie=n+"="+id+"; expires="+new Date(Date.now()+3.1536e10).toUTCString()+"; path=/; SameSite=Lax; Secure"+seg;try{localStorage.setItem(n,id)}catch(e){}}})();</script>
<script async nowprocket data-key="pk_..." src="https://db.fullvision.io/t.js?k=pk_..."></script>Two tags, two jobs:
| Tag | What it does | Why it is separate |
|---|---|---|
The inline <script> | Creates the visitor id (fv_visitor_id) while the page is still parsing, with no network call. | It runs before anything else, so the very first pageview already has an id — and so other tools on the page can read the same one. |
The async <script src> | Loads /t.js, which records the pageview and adopts the id the first tag set. | async means it never blocks your page from rendering. |
The key in the snippet is a publishable key
The pk_ key in data-key and ?k= is publishable: it is meant to be
visible to every visitor, and it can only record pageviews.
Never put a secret key (sk_) in this snippet or anywhere else the browser can
see. A secret key reads your revenue data — pasting one into a <script> tag
hands your analytics to anyone who views source. See
Authentication for the difference.
If you rotate the publishable key, the tag on your site goes stale and /t.js
starts returning 401. Re-paste the snippet with the new key.
Confirm the first pageview lands
Deploy and visit your own site
Open any page of your site in a normal browser tab.
Check the script actually loaded
In DevTools → Network, look for a request to t.js returning 200, then a
request to /v1/i returning 204. t.js at 401 means a wrong or rotated
publishable key.
Check the cookie was set
In DevTools → Application → Cookies, fv_visitor_id should be present.
Check the data arrived
The dashboard's Setup page counts pageviews as they land. It usually shows the first one within a minute.
If you have excluded your own traffic — your IP address or this browser — your test visit is dropped on purpose and never arrives. Check from another device or network instead.
What you get with nothing else installed
The tracker alone gives you the traffic half of FullVision:
- Pageviews, sessions and unique visitors — Visitors.
- Which channel each visit came from — Channel Report.
- Which landing page captured it — Page Report.
- Which Google search led to it — Keyword Report, once Search Console is connected.
To name the people behind those visits and to see your own product events, add server-side events. To attach payments to the visitor who produced them, wire revenue attribution.
Advanced
Serving the tracker from your own domain — which gets you past URL-based ad-blockers and switches identity to a first-party cookie that survives Safari ITP — is covered in First-Party Tracker Proxy. Most sites do not need it. Start here.