One tag in the head of any site.

01What Tally tracks

• Pageviews and visitors, with the source, channel, country, device and browser of each visit.
• Engaged time, counted only while the tab is in view and someone has moved in the last 30 seconds, and how far down each page they scroll.
• Goals from data-fast-goal attributes or tally() calls, and clicks on links to other sites.
• Payment Links on the page: in cookie mode the snippet adds the visitor's id to buy.stripe.com links on its own.

02Where the revenue comes from

• Stripe Payment LinksA plain site often sells with Payment Links. They link with no code, through the client_reference_id the snippet adds.
• Other checkoutsPaddle.js, Lemon Squeezy and Polar checkouts link when the page passes the visitor's id into them, a few lines the Coverage page gives you.

03What it can't read

04Adding the snippet

Where it goes: Paste it into the <head> of every page.

<script defer data-site="k3xq2mfa7twp" src="https://t.tallybyoutpost.com/script.js"></script>

This is an example site's tag. Your own, with your site's id, is on the snippet step when you add a site, and on its Setup page.

1. Copy the tag from your site's snippet step or Setup page and paste it into the head of every page.
2. Open the site in a browser: the live check turns green with the first visit, showing where it came from.
3. Connect your payment provider on the Integrations page.

05Questions

• Does the tag slow pages down?

  It's about 3 KB compressed and loads with defer, so the page renders first and links never wait for it.

• Can I test it on my own machine?

  Visits from localhost only count when the tag has data-allow-localhost, so your own development doesn't fill the dashboard by accident.

• Do I need a cookie banner?

  Not in cookieless mode, which sets no cookie. Cookie mode sets one first-party cookie, which in the EU and the UK usually needs consent; consent-first waits for your banner's yes.