Tape Documentation
Conversion tracking and ad pixels
Installation
Requirements, install, your first destination, and checking it fires.
Configuration
Every setting, per-environment overrides in config/tape.php, and environment variables.
Destinations and platforms
Every platform Tape supports, exactly which ID each needs, and where to find it.
Commerce
The funnel events that are automatic, the ones that take one line of Twig, refunds, and product IDs that match your feed.
Consent
Consent Mode v2, ten consent platforms or an expression of your own, the mirror cookie, and region defaults.
Server-side and webhooks
Conversions APIs, the queue, deduplication on a shared event ID, and signed webhooks.
Triggers
Conversions from clicks, forms, scroll depth and time on page, set up from the control panel.
Twig API
Placing the tags, firing any event with craft.tape.track(), custom events, and the Commerce funnel helpers.
JavaScript API
tape.track() for events after the page has rendered, tape.consent, tape.debug(), and the early queue.
Recovery and reports
The event ledger, the accuracy report, and sending the conversions browsers lost.
Caching
Why Tape is safe behind a full-page cache or CDN, and what to watch in your own templates.
Privacy
What Tape stores, what it hashes, what it sends, and what it never writes down.
Editions
What Lite (free) and Pro ($99, $59/year renewal) each include, and what happens on a downgrade.
Permissions
Viewing reports, editing destinations and triggers, running recovery, and allowAdminChanges.
Console commands
destinations, doctor, test, recover and prune, and which belong in a deploy check or a cron.
Extending Tape
Enrich or suppress events, register your own platform adapter, and swap the server-side transport.
Troubleshooting
Tags that do not appear, conversions that do not arrive, skipped server-side calls, and what to check first.
FAQ
Common questions about conversion tracking, consent and Commerce with Tape.