Collective Audience™ is a solution for creating and disseminating editorial or advertising content, also called components. This content is created via a dedicated platform, the DASHBOARD, while a WIDGET allows the content to be interacted with directly on the publishers’ websites.
Parties involved:
The publishers and their advertising agencies use Collective Audience for the purpose of creating content to collect opinions from their audiences, carry out surveys, organize contests - subject to rules or otherwise - or test users’ knowledge by creating quizzes. Collective Audience also allows them to monetize their space by activating the advertising tool, which allows them to disseminate content from partner advertisers. Collective Audience is committed to prioritizing editorial components; in addition, sponsored content will only use free space not utilized by partner media.
Advertisers and their agencies use Collective Audience to create sponsored content designed to collect information, conduct surveys, and measure user engagement and interaction with the advertised brand.
Users who browse the publishers’ websites utilize the Collective Audience WIDGET to interact with the component’s creator.
Finally, Collective Audience possesses its own advertising activity that receives orders from agencies and/or advertisers in order to create, schedule and disseminate sponsored campaigns on behalf of brands.
Data:
Collective Audience may be compelled to collect data on how Collective Audience WIDGETS are used by the user. Collective Audience distinguishes between two types of data:
1 - Service data:
Necessary for the proper functioning of our online services, these data are collected through proprietary Collective Audience tracking, and used by Collective Audience for Collective Audience. They represent how the WIDGET is used by the users, and, among other things, enable us to:
- Effectively collect information on user participation with components
- Create statistics in order to determine the results of diverse surveys
- Inform the user or the component's creator of a component's number of participants.
To further ensure the proper functioning of our online services, a cookie is installed on the publisher's domain ONLY to identify users and ensure they can browse properly using a Collective Audience widget. Among other things, this cookie enables us to:
- Effectively collect information on user participation with components
- Enable users to continue using a component at the point where they left it during a previous browsing session
- Keeps users from seeing the same sponsored component again if they have already provided responses
Without the users’ consent, Collective Audience will not use the service data collected to create user profiles in order to display targeted or personalized advertising.
2 - Additional data:
When users participate via Collective Audience forms, or when engaging or registering with our partners, their personal data are collected and stored by Collective Audience on European servers, and can be exported by the component's owner for a period of 13 months.
Collective Audience's partners may use third-party tracking services, which may subsequently be used to display personalized advertising to users via tools other than those of Collective Audience. These third parties are only authorized to use the collected information to ensure their services function properly.
Collective Audience acts in the capacity of technical service provider for these partners, and thus agrees to provide them with all the tools necessary to properly acquire user consent via the Collective Audience DASHBOARD. The component’s creator must decide whether it is necessary to include a means of acquiring consent to use personal data.
Finally, Collective Audience joined the IAB's TCF in September 2019 in order to acquire user consent for the following purposes:
- Storing and accessing a third-party cookie (see below)
- Personalizing the advertising/component based on a user's utilization of Collective Audience
- Targeted dissemination of the advertising/component based on the information collected via a Collective Audience third-party cookie
- Measuring the effectiveness of the advertising/component on users
- Using the geographic location of users to provide them with content adapted to their location
If users do not consent to the use of the third-party cookie, Collective Audience agrees not to fulfill the purposes mentioned above in order to disseminate a component that requests it. Advertising delivered back via the user’s WIDGET will be selected randomly from content not requiring these selective and restrictive criteria.
Cookie definition
A cookie is a small file stored on a user's hard drive in a transparent manner when browsing certain websites, and which stores information for subsequent visits. A technology present on website A and website B will be incapable of reading information from the other website.
A first-party cookie is used to store information for a single domain, that of the website the user is visiting when the cookie is installed, or for a third-party domain if the user consents.
A third-party cookie is used to store information for the entire Web and is specific to the technology that installed it at a given point in time. If this technology is present on website A and website B, it will be capable of reading information from both websites.
On the publisher domain
| Cookie name | Domain | Function | Duration |
|---|---|---|---|
caudid | Publisher domain | Preserve session information across reloads and identify users as unique (Collective Audience user ID, 24-char hex) | 1 year |
caudid_date | Publisher domain | Timestamp when the user ID cookie was set; used to support publisher requests to reset user state for a given date range | 1 year |
During a transition period, some browsers may still hold legacy cookies beopid and beopid_date with the same purposes and duration as caudid and caudid_date. They are being phased out and will no longer be set for new users.
On the advertiser domain
| Cookie name | Domain | Function | Duration |
|---|---|---|---|
beopSessionId | Advertiser domain | Count sessions correctly | Session |
beopConversionContext | Advertiser domain | Preserve conversion context information (campaign ID, referrer page…) across reloads | Session |
On Collective Audience domain, as third-party
| Cookie name | Domain | Function | Duration |
|---|---|---|---|
beopConversionRedirect | Collective Audience | Pass conversion context information (campaign ID, referrer page…) to the advertiser website | Session |
caud_sync | Collective Audience | Store a pseudonymous identifier to synchronize the technical identifiers (buyerUids) provided by advertising partners (SSPs/DSPs) in order to ensure proper campaign delivery and performance measurement via OpenRTB. | 7 days |
caud_hb_throttle | Collective Audience | Set by the header bidding (Prebid) bid endpoint so the next request does not hit infrastructure directly from the Cloudflare snippet (throttling). | 2 minutes |
On Collective Audience domain, as first party
| Cookie name | Domain | Function | Duration |
|---|---|---|---|
token | Collective Audience | Identify user | 15 minutes |
as | Collective Audience | Keep the user logged as the account they wish | Session |
language | Collective Audience | Show the platform in the preferred language | 1 year |
Website and desk observability (Grafana Faro)
On its corporate website and the desk.collectiveaudience.co desk, Collective Audience uses Grafana Faro with Grafana Cloud, where Grafana Labs acts as a processor. This replaces a traditional standalone web analytics product. It provides frontend observability: performance signals (for example Core Web Vitals–style metrics), errors and technical diagnostics, and aggregated usage of pages or areas of the application, in order to improve reliability, investigate incidents, understand how the site and desk are used in aggregate, and support fraud detection and security monitoring.
Depending on configuration, the Faro client may rely on cookies or similar browser storage, in addition to sending events to Grafana Cloud. Payloads are minimised where Collective Audience controls them. This processing is separate from widget, campaign, and advertising measurement described elsewhere in this policy.
Where personal data is transferred outside the European Economic Area, Grafana Labs provides appropriate safeguards, including EU Standard Contractual Clauses as set out in its Data Processing Agreement.
Use of data:
In general, the data can be used to correct errors, improve Collective Audience products, and, subject to agreement, transmit information to partners (cf. 2 - Additional data).
Simple campaigns
As part of its campaigns without retargeting purposes, Collective Audience agrees to extract browsing data only for dissemination at that moment and for statistical purposes, and not to create user profiles. Collective Audience does its best to anonymize the browsing IP address as early as possible in the data storage chain. Among browsing data used for dissemination and statistics, we list:
- the URL of the visited web page
- the location determined by the IP address
- hardware information (telephone, PC, brand, etc.)
- browser information (Name and browser version)
- a user identifier retrieved by a cookie that we may have installed for the user
These different data enable us to make sure the various services are functioning correctly in order to:
- Keep from presenting the same component to the same person for voting
- Semantically target the context in which the component is disseminated
- Geographically target the context in which the component is disseminated
- Analyze the context in which the component is currently, or has been, disseminated
Targeted campaigns
As part of its retargeting campaigns, and with the user's consent, Collective Audience collects the following information in addition to that which it collects for simple campaigns:
- A cross-site user identifier
- A history of the user's visibility with the Collective Audience components delivered to the user
- A history of the user's interactions with the Collective Audience components delivered to the user
These different data enable Collective Audience to:
- Perform cookie syncing with third-party data providers
- Accurately target users and their areas of interest for advertising selection
Users:
While browsing, users will be invited to consult this policy outlining the proper functioning of the Collective Audience services and how we use their data (cf. 1 - Service data).
For any additional data, the Collective Audience WIDGET or the publisher's Consent Management Platform (or CMP) displaying the component will request consent on a case-by-case basis according to the component parameters established by the partners.
Rights to the data:
Users can ask to view their participation history for Collective Audience components at any time. A button is available in the user account settings on the Collective Audience platform, or directly in the WIDGET on the publishers’ web pages. Accessing and viewing the history requires users to register for a Collective Audience account with a valid email address.
Right to be forgotten:
Users can ask to be forgotten/erased from the Collective Audience data storage systems at any time. A button is available in the user account settings on the Collective Audience platform, or directly in the WIDGET on the publishers’ web pages. Users are processed and definitively forgotten, which will make it impossible to use the data stored with Collective Audience. In order to conserve statistics, user votes will not be erased, but rather anonymized. It will be impossible to associate a vote with a user. Collective Audience agrees to send an email to any partner that has collected information on the user requesting to be forgotten. This email will indicate the user's desire to be forgotten and ask the partner to anonymize the user as well.
In addition, the button below enables the user to delete any cookie stored for the domain collectiveaudience.co