If you’re required to obtain user consent before running analytics or marketing cookies (e.g., GDPR, ePrivacy, CPRA), you can integrate Cometly with your consent banner so that no data is tracked until the user opts in.
Disclaimer: This document is provided for informational purposes only and does not constitute legal advice. For questions about compliance with privacy or data protection laws, please seek professional legal counsel.
Important: Per our Terms of Service (“TOS”), and End User License Agreement (EULA) ("EULA"), you (the customer) are responsible for ensuring compliance with all applicable data protection laws and implementing appropriate consent mechanisms.
1. Cometly Domain & Cookies
Cometly typically delivers its scripts and cookies from t.cometlytrack.com. When the pixel runs, you might see:
cometly_tracker_session– unique session tokenXSRF-TOKEN– security tokenOther random identifiers – used for analytics or marketing metrics
Because these are generally considered non-essential cookies, they shouldn’t load until the user consents.
2. Blocking Cometly Scripts Until Consent
Identify the Domain: Configure your Consent Management Platform (CMP) or cookie banner to block
t.cometlytrack.comby default.Use a “Marketing” or “Analytics” Category: In your CMP settings, classify Cometly under a category that is disabled unless the user opts in.
Allow on Opt-In: If the user accepts cookies, your CMP unblocks
t.cometlytrack.comand the Cometly script is loaded.Test: Before consent, confirm no 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 continues blocking the script, Cometly never tracks a thing.Consent Given = Tracking Starts
Once the user opts in, Cometly cookies are set and attribution data begins.
4. Your Responsibility Under Our TOS
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 info (health, credit card data).
Policy References: Make sure to mention Cometly in your cookie/privacy policy and explain how users can opt out or manage consent.
5. Frequently Asked Questions
Q: Do we have to mention Cometly’s cookies by name?
A: Yes. For transparency, list any cookies or tokens (cometly_tracker_session, XSRF-TOKEN) your site may set, including their domain (t.cometlytrack.com) and purpose.
Q: Can we treat some Cometly tokens as “strictly necessary”?
A: Typically, they’re considered non-essential. If unsure, consult your legal counsel.
Q: Does declining the banner prevent all Cometly tracking?
A: Yes—if correctly configured, the banner blocks t.cometlytrack.com until the user accepts.
6. Need Assistance?
Technical Questions: Reach out to support@cometly.com. We will do our best to help but depending on the provider and your tech stack we may not be able to help.
CMP/Consent Banner Docs: Check your provider’s documentation on script/domain blocking.
Legal Advice: This guide is not legal advice. Consult an attorney if you have questions about your obligations.
More Information About Our Policies
Disclaimer: This document is provided for informational purposes and does not constitute legal advice. Always consult legal counsel to ensure you meet applicable data protection regulations. By using Cometly, you agree to our Terms of Service.