Disclaimer: This page is provided for informational purposes only and does not constitute legal advice. For questions about compliance with privacy or data protection laws, seek professional legal counsel.
1. Cometly domain and cookies
The Cometly pixel is a single script tag. The domain it loads from is the one in thesrc of your snippet, which you find under Setup > Install the Cometly pixel > Install the pixel:
js.comet-serve.com: the default for current snippets.- Your own subdomain (for example
data.yourdomain.com): if you turned on First Party Domain Tracking. t.cometlytrack.com: older snippets that have not been replaced since they were installed.
cometly_tracker_session: unique session tokenXSRF-TOKEN: security token- Other random identifiers: used for analytics or marketing metrics
2. Block the Cometly script until consent
- Identify the domain: Configure your Consent Management Platform (CMP) or cookie banner to block your Cometly script domain (see above) by default.
- Use a “Marketing” or “Analytics” category: In your CMP settings, classify Cometly under a category that is disabled unless the visitor opts in.
- Allow on opt-in: If the visitor accepts cookies, your CMP unblocks the domain and the Cometly script loads.
- Test: Before consent, confirm no Cometly cookies load. After consent, verify the cookies appear.
3. No consent = no tracking
Because the Cometly pixel relies entirely on being loaded by your cookie banner:- No pixel = no data collection. If the banner keeps blocking the script, Cometly never tracks anything.
- Consent given = tracking starts. Once the visitor opts in, Cometly cookies are set and attribution data begins.
4. Your responsibility under our Terms of Service
- Legal compliance: Our Terms of Service outline that you bear full responsibility for adhering to privacy regulations in your jurisdiction.
- No sensitive data: Cometly prohibits sending confidential or protected information (health data, credit card data).
- Policy references: Mention Cometly in your cookie or privacy policy and explain how visitors can opt out or manage consent.
More information about our policies
- Terms of Service
- Privacy Policy
- Cookie Policy
- Acceptable Use Policy
- Data Processing Addendum (DPA)
- End User License Agreement (EULA)
- Third Party Sub Processors
Check it worked
Open your site in a private browser window and, before you answer the banner, look at the cookies in your browser’s developer tools: no Cometly cookies should be there. Accept the banner and check again:cometly_tracker_session now appears. You can also open the Cometly Pixel Helper after accepting, which shows an Init event on each page where the pixel loaded.
Frequently asked questions
Do we have to mention Cometly’s cookies by name?
Yes. For transparency, list any cookies or tokens (cometly_tracker_session, XSRF-TOKEN) your site may set, including their domain and purpose. Your browser’s developer tools show the exact names and domains set on your site after consent.
Can we treat some Cometly tokens as strictly necessary?
Typically, they are considered non-essential. If unsure, consult your legal counsel.Does declining the banner prevent all Cometly tracking?
Yes, if correctly configured: the banner blocks your Cometly script domain until the visitor accepts.Next steps
- Install and verify the Cometly pixel: find your snippet and confirm the pixel loads.
- Check the pixel with the Cometly Pixel Helper: see whether the pixel fires on a page.
- Exclude an event from the Conversion API: keep a conversion from being sent to ad platforms when a person opts out of sharing.
- Contact support with technical questions. We will do our best to help, but depending on your consent provider and tech stack we may not be able to.