Does Brandwatch require consent?

Yes. Brandwatch's scripts on third-party sites serve an analytics purpose — measuring visitor engagement with social content and brand-related elements. The tracking cookies and behavioral data collection are not strictly necessary and require informed consent before being placed.

What does Brandwatch track on embedded pages?

Brandwatch's embedded scripts collect engagement metrics from social content displays: clicks on social feeds, time spent viewing brand-related elements, and interaction patterns. They may also set cookies to track returning visitors and build engagement profiles over time.

How does ConsentStack handle Brandwatch?

ConsentStack blocks Brandwatch scripts from loading until a visitor grants analytics consent. Because Brandwatch serves a data collection purpose that benefits the site operator rather than the visitor, ConsentStack ensures it never fires before explicit consent is obtained.

What tracker domains does Brandwatch use?

ConsentStack has catalogued tracker domains for Brandwatch including brandwatch.com. These are the network destinations Brandwatch's scripts contact, which a consent platform blocks until a visitor agrees.

Brandwatch - Social Intelligence & Consent Profile

Back to Vendor Library

Overview

Brandwatch, now part of Cision, is a social listening and consumer intelligence platform that helps brands monitor what people are saying about them across social media, forums, blogs, and news sites. While the platform primarily operates as a back-end SaaS tool for social media analysts and marketing teams, its scripts can appear on third-party sites through embedded social listening widgets and analytics integrations.

The third-party footprint is minimal compared to platforms that are designed for visitor-facing deployment, but when present, these scripts collect engagement and sentiment data.

What This Script Does

Brandwatch's scripts, when embedded on third-party sites, perform analytics-focused functions:

Social engagement widgets: Embeds aggregated social media engagement data, displaying metrics like mention volumes, sentiment trends, or social conversation summaries on dashboards or public-facing pages
Data collection scripts: Gathers engagement metrics from embedded social content, tracking how visitors interact with social media displays or brand-related content on the page
Analytics tracking: Records visitor interactions with Brandwatch-powered elements, including clicks on social content, time spent viewing embedded feeds, and engagement patterns
Cookie-based identification: May set cookies to track returning visitors and build engagement profiles over time, particularly when integrated with broader marketing technology stacks

The scripts communicate with Brandwatch's API infrastructure to pull social data and report interaction metrics.

Consent & Compliance

Brandwatch's analytics-oriented scripts carry standard tracking compliance requirements:

GDPR: Behavioral tracking and visitor identification through cookies constitute personal data processing. Brandwatch typically acts as a data processor, requiring a DPA. The analytics purpose generally requires consent as the lawful basis.
ePrivacy Directive: Cookies used for tracking visitor engagement with social content are not strictly necessary for the service and require informed consent before placement.
CCPA/CPRA: Engagement data collected through Brandwatch's scripts may constitute personal information subject to disclosure requirements and opt-out rights.

The analytics nature of these scripts places them firmly in the category that requires consent under most privacy frameworks.

Should You Block This Without Consent?

Brandwatch's scripts serve an analytics purpose — measuring how visitors engage with social content and brand mentions. This data benefits the site operator's marketing intelligence rather than providing functionality the visitor needs. The tracking cookies and behavioral data collection require consent under GDPR and ePrivacy rules. Your site's core functionality won't be affected by blocking these scripts before consent is obtained.

Yes.

Is Brandwatch GDPR compliant?

Brandwatch typically loads analytics trackers, which are not strictly necessary for your site to work. Under the GDPR and the ePrivacy Directive, non-essential cookies and trackers must stay blocked until a visitor gives clear opt-in consent. So Brandwatch can be fully GDPR compliant, but only if your site holds its scripts until consent is granted and lets visitors decline just as easily. Compliance depends on how your site loads Brandwatch, not on Brandwatch itself.

Visit website