TracerKit
Updated 2026-11-02
Why use it
TracerKit is a tag manager that keeps tag config outside your repo, then checks that each tag actually fires. Headstream loads through it as a normal script tag.
Setup
In your TracerKit site, add a tag with these values:
| Field | Value |
|---|---|
| Kind | script |
| Script / pixel URL | The src from your Headstream snippet |
| Script attributes | data-key=YOUR_KEY |
| Load strategy | afterInteractive |
| Placement | head |
| Fires on | pageload |
Get the URL and key from your snippet under Project settings in Headstream.
Leave Serve first-party unchecked. Headstream works out where to send events from its own script address, so proxying the file through TracerKit would send events to the wrong place.
Why the attribute matters
Without data-key, the script loads and tracks nothing. It's the same pattern TracerKit uses for other analytics tools, which is why the field accepts data-* values.
Single-page sites
TracerKit loads a script tag once, then only reports on later route changes. Headstream tracks those route changes itself, so you won't get double pageviews. Don't add an inline version as well, since inline tags run again on each trigger.
Don't install it twice
If the Headstream tag is also in your site's code, remove it from one place.
Check it works
Publish your config and load a page on a domain listed in your Headstream project. TracerKit should show the tag as loaded, and your project's setup status should show that events are arriving. Then see track events.