Third-party data is audience information collected by entities with no direct relationship to the end user and sold or licensed to marketers — including data broker profiles, intent signals, and programmatic audience segments.
Quick Answer
Third-party data is audience information collected by entities with no direct relationship to the end user and sold or licensed to marketers — including data broker profiles, intent signals, and programmatic audience segments.
Third-party cookie-based audiences are losing 50–80% match rates as browser privacy restrictions tighten
IP-based B2B intent data (Bombora, G2 Buyer Intent) is more durable than cookie-based segments post-deprecation
Use third-party data for account identification (top of funnel) — switch to first-party for retargeting and nurture
Key Takeaways
Third-party cookie-based audiences are losing 50–80% match rates as browser privacy restrictions tighten
IP-based B2B intent data (Bombora, G2 Buyer Intent) is more durable than cookie-based segments post-deprecation
Use third-party data for account identification (top of funnel) — switch to first-party for retargeting and nurture
How Third-Party Data Works
Third-party data is created when companies (data brokers, publishers, demand-side platforms, intent data vendors) aggregate behavioral and demographic signals from across the web and package them into audience segments for sale. Classic third-party data includes: cookie-based behavioral segments (users who browsed competitor sites), demographic overlays (firmographic data about company size or industry), and intent signals (Bombora Company Surge data, which tracks surging content consumption around topics). This data has no direct relationship to your brand — the individuals profiled have generally not opted in to being included in your targeting.
Why Third-Party Data Matters for B2B Marketing
For B2B advertisers, third-party data's primary value is in prospecting — reaching accounts or personas that haven't yet discovered your brand. Intent data (Bombora, G2 Buyer Intent, TechTarget Priority Engine) is particularly valuable because it identifies companies actively researching topics related to your solution right now — shortening the effective prospecting window. Third-party data is less valuable for performance marketing and remarketing, where first-party behavioral signals are always more accurate.
Third-Party Data: Best Practices & Strategic Application
The structural problem with third-party data is its dependence on third-party cookies, which are being eliminated. Safari and Firefox have blocked third-party cookies for years; Google Chrome began restricting them in 2024. As a result, cookie-based third-party audience segments are losing accuracy as cookie matching rates decline — many segments that nominally target 500,000 users may only actually reach 20–30% of that population post-deprecation. Intent data vendors that use non-cookie signals (IP-based matching, authenticated publisher networks) are more durable.
Agency Perspective: Third-Party Data in Practice
B2B teams should view third-party data as a supplement to first-party data, not a substitute. The optimal strategy is to use third-party intent signals (Bombora, G2) to identify in-market accounts, import those account lists into LinkedIn and Google Ads as target account lists, and then layer your own first-party retargeting on top for accounts that have visited your site. This combines the prospecting reach of third-party data with the accuracy and personalization of first-party signals.
Frequently Asked Questions: Third-Party Data
Third-party data is audience information collected by entities with no direct relationship to the end user and sold or licensed to marketers — including data broker profiles, intent signals, and programmatic audience segments.
It depends on your deal size and sales cycle length. For companies with ACV above $20K and sales cycles over 90 days, intent data typically delivers positive ROI by helping SDRs prioritize outreach to in-market accounts. For high-velocity SMB sales, the cost ($2,000–$50,000+ annually for Bombora or G2) may not be justified. Always run a 90-day pilot with defined success metrics before committing to an annual contract.
Cookie-based third-party audience segments will continue to decline in accuracy and reach. The industry is transitioning to identity solutions like UID2 (The Trade Desk) and authenticated publisher data pools (logged-in users on publisher networks). B2B-specific vendors like Bombora and Demandbase are shifting to IP-based and authenticated graph approaches that don't rely on third-party cookies.
Third-party cookies are the technical mechanism (browser cookies set by a domain different from the one being visited) that enables cross-site tracking. Third-party data is the broader category of externally sourced audience information — which can be delivered via cookies, device fingerprinting, IP matching, authenticated ID graphs, or data broker file uploads. Eliminating third-party cookies disrupts cookie-based third-party data but not IP or authenticated-identity-based approaches.
MV3 Marketing helps B2B companies apply these strategies to drive measurable pipeline growth. Our team executes analytics setup for technology, SaaS, and professional services companies.
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
_gac_
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
