Introduction
Below is a list of frequently asked questions about Cookie-based identification. Click the links below to learn more.
- As a customer, how do I benefit from the use of cookies?
- Does Demandbase offer an opt-out?
- How do I get access?
- How does cookie-based identification work?
- How does it work with Demandbase Tag?
- What about GDPR compliance?
- What can you tell me about Demandbase cookies?
- What is my obligation?
- What signals and sources drive our visitor-level data?
- Which solutions will use visitor-level data?
- Why does Demandbase sync with third parties?
As a customer, how do I benefit from the use of cookies?
- For identification purposes, Demandbase analyzes online identifiers (cookies) in the aggregate and applies AI and machine learning models to map them to companies and improve the overall quality of your experience with Demandbase solutions.
- Demandbase also syncs the cookie information with other cookies so that you're able to target users on relevant networks in the event you choose to run advertising through Demandbase. This cookie sync process involves setting 3rd party cookies as described below.
- When Demandbase uses cookie-based identification and sees that cookie again on one of your pages, we return information/identification for the associated company, thereby increasing identification.
- The use of cookies helps identify company users not using their corporate network and provides you with business intent, helps you to identify and count unique users, drive site optimization, and improve retargeting.
Does Demandbase offer an opt-out?
Yes. Users may opt-out of Demandbase cookies through the Digital Advertising Alliance's (DAA) WebChoices tool, available at: http://optout.aboutads.info/. You can opt-out of Demandbase ad tech partners via their respective websites or the DAA's WebChoices tool.
How do I get access?
- All Demandbase clients will have access by default, which is fired based on a pixel in your Demandbase Tag.
How does cookie-based identification work?
- Visitors are cookied on our ad network or on client pages which attach a unique ID to that user/device to it for future reference.
- Our IP API logs and IPOW bid/no-bid tell us when we see that cookie in association with a SID. When cookie IDs associated with company networks meet a threshold, the Demandbase rules engine maps them
- When Demandbase sees that cookie again, on one of your pages, we return information/identification for the associated company.
- You can expect to see an increase in identification, and can see your “remote” traffic in the Platform.
How does it work with Demandbase Tag?
- All Demandbase clients will have access to setting and reading cookies by default, which are fired based on a pixel in your Demandbase Tag.
- We highly recommend keeping this code on your site because it helps to improve overall site identification and helps reach the right individuals in the event you choose to run advertising in addition to the benefits listed above.
- If you would like to request a custom integration for cookies or to disable cookies, this decision may affect identification rates and advertising. Please inquire with your CSM if you have any concerns or additional questions.
What about GDPR compliance?
- This is GDPR compliant.
- We are able to disable cookies for your implementation. Please inquire with your CSM if you have any concerns or additional questions.
- This identification method has a higher accuracy & higher precision than standard cookies.
What can you tell me about Demandbase cookies?
Through the Demandbase Cookie Policy, customers can access the most updated details about Demandbase cookies.
Demandbase also syncs with third-party cookies, which allow these third parties to set or access cookies on users' devices. Demandbase and third-party cookies are both considered third-party persistent cookies.
Demandbase cookie details:
Cookie | Duration | Type |
---|---|---|
tuuid | 24 months | Third party persistent |
iuuid | 24 months | Third party persistent |
What is my obligation?
Under the terms of your agreement, you are required to properly disclose the use of Demandbase technology and data collection through your website, including obtaining consent for the use of our technology and data collection when required by law. Please consult your legal counsel for your specific obligations and make the time to ensure that your disclosures are up-to-date.
What signals and sources drive our visitor-level data?
- Ad Impressions on our network
- DB Customer sites with DB Tag placed
- DB Partner sites with DB Tag placed
Which solutions will use visitor-level data?
- Data collection:
- After IP verification of corporate network, Demandbase uses cookies to identify when a user is off-corporate network.
- Once a user is verified and cookied, we can understand their digital behavior and business intent.
- Targeting Solution:
- Identifying and counting unique users.
- Retargeting / remarketing individuals from target accounts from certain pages.
- Site Optimization:
- Understands the intent and engagement, both off-site and on-site at an individual level as well as at an account level. When it can, Site Optimization recommends website content based not only on a successful buyer’s journey for the visitor’s account or IP address, but specifically for that individual comparing their on-site and off-site web page visits with other people’s similar behavior.
Why does Demandbase sync with third parties?
By default, Demandbase syncs with the third-party ad technology partners so that if you decide to run an ad campaign with Demandbase, we can target these users on the relevant networks. Demandbase may send and receive personal data (cookies) to associate Demandbase assigned cookies or online identifiers with third-party partners’, such as DMPs and other adtech providers, cookies or online identifiers (also known as “cookie syncing”) which involves allowing our third-party partners to set cookies and assign online identifiers in furtherance of our Services and to increase performance of ad campaigns. These syncs may be removed upon request for customers that do not run advertising on Demandbase.
Cookie Name | Source | Purpose | Type |
---|---|---|---|
liveramp | Liveramp (24 months) | This cookie is used for analytics and advertising services provided by Demandbase products. | Third party persistent |
Bidr | Beeswax (5 years) | This cookie is used for analytics and advertising services provided by Demandbase products. | Third party persistent |
Bidswitch | Bidswitch (24 months) | This cookie is used for analytics and advertising services provided by Demandbase products. | Third party persistent |