Open Tyton
Tracking

Connect consent controls

Wait for the right permission before tracking, and stop when it is withdrawn.

Video walkthrough coming soonFollow the steps below for now.

What you need

Decide when your site may start tracking and find the consent manager’s grant and withdrawal actions. Tyton does not provide a cookie banner or decide your legal requirements. Seeing a banner does not show that tracking actually waits.

  1. Install the browser tracking code with data-consent="wait" or SDK consent: "wait". The compatibility default allows tracking, so set waiting explicitly if your site needs it.
  2. When your consent manager reports permission, call window.tyton.grant(). When someone withdraws it, call window.tyton.revoke(). Use the manager’s supported way to read a returning visitor’s saved choice too.
  3. Test before permission, after permission, after withdrawal, and after permission is granted again. Keep Tyton in verification mode while checking planned conversions without sending them to Meta.

Do not grant permission just because the script loaded or a form was submitted. Read the visitor's saved choice first. If the site has no banner, confirm the site's actual policy with its owner instead of assuming that tracking is allowed. Tyton does not require you to add a particular banner.

Success check

Before permission is granted, Tyton should make no tracking requests, read no tracking cookies, and call no Pixel. After permission in live mode, it can send a PageView and approved conversions. Verification mode still prevents PageView and Pixel calls.

Withdrawal stops future Tyton tracking and clears the identity held for that session. If you later grant permission again, identify the visitor again only when appropriate. Tyton does not replay conversions missed while consent was off.

Limits and troubleshooting

Tyton cannot recall requests already dispatched or control another tracker’s queued work. Check other Pixel/GTM installations and the Meta script separately. Server callbacks must also respect the required consent; a browser grant is not an automatic policy engine for every backend event.

Include both browser and server paths in your checks. Submitting a form after someone withdraws permission must not turn tracking back on.

If events appear before grant, identify which script sent them before changing settings. If the dashboard says consent is not checked, do not infer a fault or success: verify the behavior on the actual site. Keep personal data out of URL paths and diagnostic logs.