Use Hoko with Google Tag Manager
The Hoko Tag Manager path is a consent-gated attribution script. It does not send analytics events or create a click on its own.
Before you start
- Use a web container where you can edit tags.
- Have Preview permission and a test page.
- Define granted, denied, and unset consent states in your consent manager.
Configure Preview
- Download the Hoko attribution template.
- Open Templates in Tag Manager and import the downloaded template.
- Inspect the template permissions. Keep
inject_scriptbounded to the approved origin. - Create a tag and trigger for the page. Use Preview before you submit or publish changes.
- Run Preview with each consent state.
- With consent granted, verify that the fixed
https://hoko.to/analytics.jsscript can preserve an existinghoko_idfrom the query or cookie.
Verify and clean up
Check repeated execution, an absent identity, denied consent, and an unset state. The script must not send analytics without explicit consent. Remove tags or templates that you no longer need.
Troubleshoot
If the script does not load, check the approved origin and template permissions. If a denied state sends data, remove the trigger and review the consent condition. Preview results do not prove a published container.
See the Tag Manager technical guide for template permissions and consent behavior.