Tags
Package projects is where your sites live: create one, deploy a build, roll back to any release.
Package projects is where your sites live: create one, deploy a build, roll back to any release.
| Base URL | https://api.hanzo.ai |
| Operations | 1 |
| Auth | Authorization: Bearer $HANZO_API_KEY |
tags
GET /v1/tags
The site's browser tag set for the hosted tag — which pixels to inject, by publishable key
Returns the client-side pixels the SITE has connected (GA/Meta/TikTok/X) with their NON-SECRET ids, so the hosted tag injects them first-party and stamps each browser event with the same event_id the server-side Conversions API uses — deduping the two. Resolved per site: by the publishable key on ?key= when it names a project, else by the request host, so hanzo.ai and hanzo.chat carry different tags under one org. WITHOUT a resolvable site it answers an empty set at 200 — a page never breaks on its tag config.
How is this guide?