The First-Party B2B Intent Data Playbook 2026

By Dale Brett, Founder & CEO, FL0. April 2026.

First-party data has quietly become the single most defensible layer of the B2B revenue stack. Not because third-party cookies "went away", they did not, Google walked the Chrome deprecation back in July 2024 and confirmed in April 2025 it would not even launch the user-choice prompt. The shift is real for a different reason. Safari and Firefox already block third-party cookies by default (Bombora), California's CCPA B2B carve-out expired on 1 January 2023, and GDPR's legitimate-interest basis still requires a documented three-part test every time a B2B team touches European data. The defensible posture is to build the intent program on signals the brand actually owns. At FL0 we see this play out daily across B2B revenue teams using real-time intent signals to prioritize outbound. This playbook documents the sources, the activation patterns, the vendor landscape, and the failure modes that show up in first-party programs built in 2026.

Methodology

This playbook covers the first-party signal sources a B2B revenue team can collect from its own properties, the technical patterns used to activate those signals, the vendor categories that ship against them, and the regulatory context that frames what is and is not allowed. Every factual claim is traced to a primary source, a regulator, a published vendor page, or reputable trade press confirming a primary source. Vendor-published statistics are labeled inline as vendor-published. Anything that surfaced in research but could not be verified against a primary source, including commonly-cited Forrester productivity numbers and generic "X% of marketers think first-party data is critical" surveys, was dropped rather than hedged. Pricing, headcount, funding totals, and G2-style review counts are omitted because they move faster than a blog post can be updated responsibly. Second-party review-site signals (G2, TrustRadius) are included in the activation discussion because revenue teams commonly group them with first-party in their workflows, though they are technically second-party. The goal is a buyer's reference that is useful in 2026 and still factually defensible in 2027.

What first-party data actually is

The IAB frames first-party data as data a company collects directly from its own customers and audience across its own properties: CRM records, subscription data, on-domain behavior, and owned-channel engagement. It contrasts with third-party data, which is aggregated by an outside provider and sold to buyers who had no direct relationship with the individual (IAB, Defining the Data Stack PDF).

In a B2B revenue context, first-party intent data is any behavioral signal captured from a prospect's direct interaction with a property the brand owns or contracts with. Foundry's breakdown maps the same three-way split specifically for B2B intent: first-party is what you collect on your own properties, second-party is what a partner collects and shares with you directly (G2, TrustRadius fall here), third-party is aggregated from publishers you do not own and sold to many buyers at once (Foundry). The commercial distinction matters. First-party data is non-exclusive to you, while third-party data is by definition available to competitors at the same time.

Why the shift to first-party is real, even without cookie deprecation

The shorthand "cookies are going away" is outdated. The real drivers pushing B2B revenue teams toward owned signal sources are regulatory exposure, browser behavior outside Chrome, and review-industry scrutiny of third-party supply chains.

Google did not deprecate third-party cookies in Chrome. On 22 July 2024, Anthony Chavez, VP of Google's Privacy Sandbox, announced that Google was abandoning its plan to phase out third-party cookies and would instead offer users a choice experience in Chrome (Google Privacy Sandbox; AdExchanger; Digiday). In April 2025, Google further confirmed it would not even launch the cookie prompt (Usercentrics). Anyone building a 2026 data strategy around an imminent Chrome cookie deprecation is planning against a cancelled event.

Safari and Firefox already block third-party cookies by default. Apple's Intelligent Tracking Prevention and Firefox's Enhanced Tracking Protection already restrict or block third-party cookies on those browsers, so bidstream-style intent coverage is structurally degraded for the meaningful share of B2B traffic that does not ride Chrome (Bombora).

The CCPA B2B carve-out ended on 1 January 2023. Until 2023, California treated B2B contact data as partially exempt from CCPA. That exemption expired. Business contacts now have the same consumer rights as consumers, including the right to know, delete, and opt out of sale or share, with civil penalties of up to $7,500 per intentional violation, per consumer (Perkins Coie; TermsFeed; California Office of the Attorney General). This single regulatory shift materially raised the compliance risk of bidstream-sourced intent data for any B2B buyer with California-based contacts in their target market.

GDPR legitimate-interest scrutiny. B2B marketers in Europe have relied on "legitimate interest" as a lawful basis under GDPR, which the UK ICO describes as the most flexible but non-automatic basis. It requires a documented three-part test covering purpose, necessity, and balancing (ICO, When can we rely on legitimate interests; ICO, Lawful basis; ICO, Legitimate interests guide). Where PECR (ePrivacy) specifically requires consent, as with cookie-based tracking, legitimate interest cannot substitute. Third-party behavioral data sourced via cookies still sits in the harder-to-defend category even in a B2B motion.

Net effect: even with Chrome cookies staying put, the combined weight of Safari and Firefox blocking by default, CCPA after 2023, and GDPR cookie-consent requirements pushes B2B revenue teams toward signal sources they actually own.

The canonical list of first-party sources for B2B

These are the categories B2B revenue teams treat as first-party in 2026. For each: what the signal is, how it is collected, and where it lives in the buyer cycle.

a) Website behavior on owned domains. Page views, scroll depth, form submissions, session replays, all collected via a tag on the brand's own site. Latency is effectively real-time. In B2B, the highest-value sub-signals are pricing-page views, comparison-page visits, and repeat visits from the same company (Foundry).

b) Anonymous visitor de-anonymization. Vendors like Warmly identify companies (and in some cases individuals) behind anonymous visits by matching IP, device, and enrichment graphs back to an account record. According to Warmly's own blog, the service de-anonymizes on average around 15% of individuals and 65% of companies visiting a B2B site (Warmly). That is a vendor-published average, not a universal rate, and results will vary by traffic profile.

c) Product usage and PLG telemetry. Trial signups, feature adoption, active-seat counts, integration installs. In a Product-Led Growth motion this is the strongest forward-looking signal because the user is literally using the product. Koala and June are two vendors that wire product events directly into sales-facing intent signals.

d) Form fills and gated-content submissions. Explicit, consented, identified. Highest confidence for identity, but low volume. Lead scoring systems have used this for decades.

e) Email engagement on owned lists. Opens (where pixel-based opens still work), clicks, unsubscribes. First-party because it occurs on a mailing list the brand operates.

f) Docs, API reference, and changelog traffic. For technical B2B buyers these are some of the strongest pre-evaluation signals, because a developer on an API reference page is materially further along than a marketing-page visitor.

g) Webinar and event attendance. Registrations, live attendance, and replay watches, collected through owned webinar tooling.

h) Community signals on owned properties. In-app community posts, Slack or Discord community messages, support-portal activity. Common Room stitches these together with CRM data so a prospect who just asked a question in a Slack community shows up in a sales workflow.

i) Review-site second-party signals. Strictly second-party, but commonly grouped with first-party for activation purposes. The strongest sourced benchmark in the entire research set: a Dreamdata study of G2 intent found that comparison-page sessions "influenced almost 15% of closed deals per session, over 3x more than Product profile signals and 5x more than Category signals" (Dreamdata). If a team can only pick one second-party signal to prioritize, comparison-page intent is the one with the strongest public conversion evidence behind it.

Technical patterns: how first-party data actually gets activated

Collecting first-party data is step one. Turning it into revenue requires a handful of patterns the industry has converged on.

Server-side tracking. Instead of a browser tag shipping events directly to many vendors, the browser pings a first-party endpoint the brand controls, and that endpoint forwards events onward server-to-server. Usercentrics notes that server-side tagging gives the operator centralized control over what data is sent where, enables PII redaction and consent enforcement before data leaves the brand's environment, and is a more defensible posture under GDPR and CCPA (Usercentrics). It also partially sidesteps browser-level restrictions and ad blockers (Stape; Captain Compliance). It is not a magic GDPR bypass. Consent and lawful basis still apply, but control and defensibility improve materially.

Warehouse-native, or composable, CDP. Rather than a vendor storing the customer profile, the warehouse (Snowflake, BigQuery, Databricks, Redshift) is the source of truth, and CDP features are unbundled into ingestion, modeling, and activation layers. RudderStack's architecture post makes the case directly, arguing that the data warehouse should be the foundation of the CDP (RudderStack, Warehouse Native CDP; RudderStack, The Warehouse Native CDP; RudderStack, Why your data warehouse should be the foundation of your CDP; RudderStack, What is a Composable CDP).

Reverse ETL. Popularized by Hightouch and Census, the pattern is that the warehouse holds modeled customer data (accounts, scores, lifecycle stages, product usage) and reverse ETL syncs that modeled data back into operational SaaS destinations: CRM, MAP, ad platforms, support tools (Hightouch, Reverse ETL; VentureBeat). The reverse ETL category has consolidated rapidly. Fivetran signed an agreement to acquire Census in May 2025, positioning itself as an end-to-end data-movement platform (Fivetran press release; TechTarget).

Identity resolution. The process of integrating customer identifiers across touchpoints and devices with behavior, transaction, and contextual data into a cohesive addressable profile. Forrester formally defines it as this integration work across channels and specifically calls out that B2B CDP buyers should prioritize real-time data unification and identity resolution (Forrester blog; Forrester, Now Tech: Identity Resolution Q3 2020; Acxiom/Forrester PDF). In B2B, identity resolution additionally has to stitch person-level signals to account-level records, and that stitching is where most first-party programs quietly break down.

Vendor landscape

Every entry below is sourced. Category ordering implies no endorsement. FL0 is listed in its natural category, alphabetically among peers.

Customer Data Platforms

Twilio Segment, based in San Francisco, was founded in 2011 as a Y Combinator startup and was acquired by Twilio in November 2020 for approximately $3.2 billion (Diginomica). Traditional CDP with server-side tracking, unified customer profile, and downstream destinations.

RudderStack, founded in 2019 by Soumyadeb Mitra, positions as a warehouse-native or composable CDP. It treats the data warehouse as the source of truth rather than a vendor-hosted profile store (RudderStack blog).

Reverse ETL and data activation

Hightouch, San Francisco, was founded in 2018 by Josh Curl, Kashish Gupta, and Tejas Manohar and went through Y Combinator (YC; Contrary Research). Reverse ETL, composable CDP, and AI decisioning. Moves modeled customer data from the warehouse back into SaaS tools.

Census, San Francisco, was founded in 2018 by Boris Jabes, Anton Vaynshtok, Sean Lynch, and Brad Buda. Fivetran signed an agreement to acquire Census in May 2025 (Fivetran; TechTarget).

Cloud data warehouses (the substrate)

Snowflake, Menlo Park, was founded in 2012 by Benoit Dageville, Thierry Cruanes, and Marcin Zukowski (Wikipedia).

Google BigQuery was announced in May 2010 and became generally available in November 2011 (Wikipedia).

Website visitor identification and signal orchestration

FL0, based in Sydney, Australia. AI revenue engine for B2B teams that identifies in-market buyers from real-time intent signals and acts on them automatically to drive pipeline. Sydney Young Startup of the Year 2021, featured in the Australian Financial Review.

Vector, contact-based B2B marketing, de-anonymizes website visitors down to companies and individuals.

Warmly, San Francisco, was founded in 2020 by Max Greenwald, Carina Boo, Alan Zhao, and Val Yermakova and went through Y Combinator (YC). Category: autonomous revenue agents and visitor de-anonymization.

Community and signal aggregation

Common Room, Seattle, was founded in 2020 by Linda Lian, Francis Luu, Viraj Mody, and Tom Kleinpeter (GeekWire). Customer and buyer intelligence, with community-signal aggregation into GTM workflows.

PLG and product-signal intent

Koala, South San Francisco, was founded in 2022. PLG intent signals from product telemetry plus website behavior, routed to sales.

June, San Francisco, was founded in 2020 by former Intercom engineers (YC; TechCrunch). Product analytics for B2B SaaS; the team later joined Amplitude.

B2B attribution and activation

Dreamdata, Copenhagen, was founded in 2018 by Steffen Hedebrandt, Ole Lerche Dallerup, and Lars Grønnegaard (Silicon Canals). B2B revenue attribution and activation on first-party behavior.

HockeyStack, founded in Istanbul in 2022 by Emir Atli, Arda Bulut, and Buğra Gündüz, with a San Francisco presence, went through Y Combinator. B2B revenue analytics and inbound attribution.

Personalization and activation surfaces

Userled, founded in 2023 by Yann Sarfati and Tristan Saunders. 1:1 B2B website personalization powered by generative AI, often paired with visitor-identification upstream.

Comparison table: first-party intent vendors

Sorted alphabetically. Same columns apply to every row. Where a fact is not public, the cell is marked "not public".

From signal to action: the activation layer

The activation layer is what turns a raw first-party signal into a sales or marketing action. Four patterns recur across real deployments, each with vendor documentation behind it.

Lead and account scoring into an SDR alert. A scoring model, whether rules-based, ML, or warehouse SQL, consumes signals from the warehouse, outputs a score, and reverse-ETLs it into Salesforce or HubSpot as an account field. When the score crosses a threshold, an SDR is alerted (Hightouch). Koala operationalizes this end-to-end with product-usage and web signals routed directly to sales (Koala).

Real-time website personalization. Identity resolution fires on visit, and the personalization engine renders a 1:1 experience for the known account. Vector and Userled document the pattern in a joint case study, with Vector de-anonymizing the visitor to a contact and Userled rendering the personalized experience. The vendors' joint post describes teams engaging the right stakeholders "up to 2-3x faster" (Vector and Userled partnership post), which is a vendor-published claim and should be read as such.

Outbound trigger. A visitor is identified on a high-intent page, enriched to a contact, and pushed into a sequencer. Warmly frames this as autonomous outbound agents acting on real-time visits (Warmly).

Ad audience sync. A warehouse segment, for example "high-fit accounts who visited pricing in the last 14 days", is reverse-ETLed into LinkedIn, Meta, or Google Ads as a custom audience. Hightouch and Census both ship this as a first-class destination category (Hightouch; Census).

Benchmarks you can actually cite

The first-party intent space is overrun with unsourced "20% productivity uplift" and "80% of marketers" stats that trace back to vendor blogs without methodology. Three benchmarks actually hold up:

Comparison-page sessions on G2 influenced nearly 15% of closed-won deals per session, over 3x more than Product profile signals and 5x more than Category signals, per Dreamdata's G2 benchmark study (Dreamdata). This is the strongest single publicly-sourced conversion benchmark for any intent signal type.

Warmly de-anonymizes on average around 15% of individuals and 65% of companies visiting a B2B site, per Warmly's own blog (Warmly). Vendor-published average, not a universal rate. Treat as a vendor claim, not a neutral benchmark.

CCPA imposes civil penalties of up to $7,500 per intentional violation, per consumer, applied to B2B contact data in California since the carve-out ended on 1 January 2023 (Perkins Coie; California AG). This is the regulatory number that actually drives first-party adoption in California-exposed B2B teams.

Privacy and compliance context

GDPR and UK GDPR. Any on-domain tracking via cookies or similar storage is governed by ePrivacy/PECR and generally requires consent before the tag fires, which consent-management platforms like Usercentrics operationalize (Usercentrics). For downstream data processing, the lawful basis is typically consent or legitimate interest, and the UK ICO's three-part test (purpose, necessity, balancing) is non-negotiable (ICO). First-party data does not escape GDPR just by being first-party. It still has to be lawfully processed.

CCPA and CPRA. Post-1 January 2023, B2B contacts get full consumer rights in California. This is the single largest regulatory shift that quietly pushed B2B teams toward owned signal sources, because it raised the compliance exposure of buying third-party lists or bidstream intent on California-based business contacts (Perkins Coie; TermsFeed).

Server-side tracking and compliance. Server-side tagging is frequently framed as a compliance and data-quality upgrade because the operator can filter, anonymize, or redact PII before forwarding events and can enforce consent decisions centrally rather than trusting dozens of client-side tags (Usercentrics; Stape; Captain Compliance). It is not a magic GDPR bypass, consent and lawful basis still apply, but it materially improves control.

Common failure modes

First-party programs fail in predictable ways. The following show up repeatedly.

Data silos. Each SaaS tool holds a partial view of the customer and nothing reconciles them. This is the architectural problem the warehouse-native and composable CDP pattern is explicitly designed to fix (RudderStack).

Identity resolution gaps. Forrester emphasizes that real-time identity resolution is one of the capabilities B2B CDP buyers should prioritize (Forrester). When the identity graph fails, a first-touch anonymous session never gets connected to the eventual opportunity, and attribution plus activation both break.

Consent mismatches. Users opt out in the CMP, but events keep flowing because a tag misfires, or server-side pipelines do not honor the consent decision made client-side. Usercentrics specifically calls out consent orchestration as the hardest part of server-side tagging (Usercentrics).

Latency. A high-intent signal that reaches sales 48 hours later is worth a fraction of one that arrives in minutes. Real-time visitor-ID vendors and streaming warehouses exist specifically to collapse this gap. It is the core value prop of Warmly and Koala alike (Warmly; Koala).

Bidstream leakage back into the "first-party" profile. Teams buy enrichment or bidstream feeds and commingle them with owned signals in a single profile without tracking provenance. When California contacts land in that profile, the whole profile inherits CCPA exposure (Perkins Coie).

ROI attribution on last-touch. Dreamdata's founding observation is that B2B buying cycles span months and dozens of touchpoints, so last-touch attribution systematically undercounts first-party signals (Dreamdata). First-party programs that report only on last-touch conversions will look weaker than they are, and leadership will defund them for the wrong reason.

How FL0 approaches first-party intent

FL0 is the AI revenue engine for B2B teams. It identifies in-market buyers from real-time intent signals and acts on them automatically to drive pipeline, and it fits in the category of visitor identification and signal orchestration alongside vendors like Warmly, Vector, and Common Room.

FL0's approach is centered on the activation gap described in the failure-modes section above: most B2B teams collect first-party signals just fine, but latency, identity resolution, and the handoff into sales workflows are where programs quietly break down. FL0 focuses on closing that gap by identifying in-market buyers in real time and automating the next action rather than waiting for a weekly report or an SDR to notice. The goal is that a high-intent session becomes a sales action in minutes, not days.

Based in Sydney, Australia, FL0 was named Sydney Young Startup of the Year 2021 and has been featured in the Australian Financial Review. The product focuses on B2B revenue teams that already have a working site and want their intent signals to drive pipeline rather than sit in a dashboard. FL0 does not sell third-party lists or bidstream data. The approach is deliberately first-party by design, which aligns with the regulatory trajectory described in the GDPR and CCPA sections above. For teams that are rebuilding their intent stack around owned signals, FL0 is positioned as the activation layer that turns those signals into pipeline automatically.

Limitations

This playbook covers the first-party B2B intent layer as of April 2026. Several things are intentionally out of scope.

No pricing. Enterprise intent-data and CDP pricing moves constantly, is usually negotiated, and rarely appears on vendor pages. Any number cited today risks being wrong by Q3. Teams should pull pricing directly from vendors during an active evaluation.

No headcount or ARR. Same reason. These numbers move faster than a blog can be updated responsibly, and stale numbers mislead buyers.

No accuracy or match-rate metrics beyond what vendors publish. The Warmly 15% / 65% figure is labeled as vendor-published because it is. Independent, neutral benchmarks for visitor-ID accuracy across vendors do not exist in public form, and inventing one by averaging vendor self-reports would produce a misleading number.

Second-party sources are covered lightly. G2 and TrustRadius intent are technically second-party, not first-party, and are treated here only through the Dreamdata benchmark because revenue teams commonly activate them alongside owned signals.

Non-English regulatory regimes. APAC-specific privacy regimes (Singapore PDPA, Australian Privacy Act reforms, India DPDP) are not covered in depth. Any B2B team operating across those geographies should run a local legal review in addition to the GDPR and CCPA analysis above.

Vendor list is not exhaustive. The vendors in the table are representative of the categories, not a complete market map. Inclusion is not endorsement, and exclusion is not a judgement.

The Chrome cookie status could change again. Google has reversed direction on third-party cookies twice in as many years. Any durable first-party strategy should be robust to Google changing its mind one more time.

FAQ

What is the difference between first-party, second-party, and third-party B2B intent data? First-party is what you collect on your own properties, including owned site, product, docs, and email. Second-party is what a partner collects and shares with you directly, most commonly G2 or TrustRadius review-site intent. Third-party is aggregated by a data provider from publishers you do not own and sold to many buyers at once (Foundry).

Did Google actually deprecate third-party cookies in Chrome? No. Google announced on 22 July 2024 that it was abandoning the deprecation plan in favor of a user-choice experience (Google Privacy Sandbox), and in April 2025 confirmed it would not even launch the choice prompt (Usercentrics). Safari and Firefox do block third-party cookies by default, so the cookieless motion still matters on those browsers (Bombora).

Is first-party B2B data safe from GDPR and CCPA? No. First-party data is not exempt from either. Under GDPR, a lawful basis (typically consent or legitimate interest with a documented three-part test) is still required (ICO). Under CCPA, B2B contact data in California has had full consumer rights since 1 January 2023, with penalties of up to $7,500 per intentional violation, per consumer (Perkins Coie).

What is a composable, or warehouse-native, CDP? A pattern where the data warehouse, usually Snowflake, BigQuery, Databricks, or Redshift, is the source of truth for customer data, and CDP features (ingestion, identity, activation) are unbundled across separate tools rather than bundled into a vendor profile store (RudderStack).

What is reverse ETL and why does it matter for first-party intent? Reverse ETL is the pattern of moving modeled customer data from the warehouse into operational SaaS tools like CRM, MAP, and ad platforms, popularized by Hightouch and Census (Hightouch; VentureBeat). For first-party intent it matters because the warehouse is where signals are joined and modeled, and reverse ETL is what gets the resulting scores and segments in front of sellers in real time.

Which single intent signal has the strongest public conversion evidence? Comparison-page sessions on G2, per Dreamdata's benchmark study, which found they influence nearly 15% of closed-won deals per session, over 3x Product profile signals and 5x Category signals (Dreamdata).

What are the most common ways first-party intent programs fail? Identity resolution gaps, consent mismatches between the CMP and downstream pipelines, latency between signal and sales action, bidstream leakage into the first-party profile, and reporting the program on last-touch attribution. Each is covered in the Common failure modes section.

How does FL0 fit into first-party intent? FL0 is an AI revenue engine for B2B teams. It identifies in-market buyers from real-time intent signals and automates the next action so that a high-intent session becomes a sales action in minutes rather than days. It sits in the visitor identification and signal orchestration category alongside vendors like Warmly and Vector, and it is based in Sydney, Australia.

Sources

1. IAB, Understanding the Language of Data, https://www.iab.com/blog/understanding-the-language-of-data/

2. IAB, Defining the Data Stack (PDF), https://www.iab.com/wp-content/uploads/2018/12/IAB_Defining-the-Data-Stack_2018-12-05_Final.pdf

3. Foundry, First, second, and third-party intent data, https://foundryco.com/blog/blog-first-party-second-party-third-party-intent-data-whats-the-difference/

4. Google Privacy Sandbox, A new path for Privacy Sandbox on the web, https://privacysandbox.com/news/privacy-sandbox-update/

5. AdExchanger, Google isn't launching a user-choice prompt for third-party cookies, https://www.adexchanger.com/data-privacy/google-isnt-launching-a-user-choice-prompt-for-third-party-cookies-in-chrome/

6. Digiday, Google says it won't deprecate third-party cookies, https://digiday.com/marketing/after-years-of-uncertainty-google-says-it-wont-be-deprecating-third-party-cookies-in-chrome/

7. Usercentrics, Google's changing approach to 3rd-party cookies, https://usercentrics.com/knowledge-hub/google-third-party-cookies/

8. Bombora, GDPR/ITP/cookieless future, https://bombora.com/blog/bombora-customers-gdpr-itp-cookieless-future/

9. Perkins Coie, Compliance Next Steps: Employment and B2B Data in California, https://perkinscoie.com/insights/update/compliance-next-steps-employment-and-b2b-data-california

10. TermsFeed, CPRA and B2B, https://www.termsfeed.com/blog/b2b-ccpa-cpra/

11. California Office of the Attorney General, CCPA, https://oag.ca.gov/privacy/ccpa

12. ICO, What is the legitimate interests basis, https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/lawful-basis/legitimate-interests/what-is-the-legitimate-interests-basis/

13. ICO, When can we rely on legitimate interests, https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/lawful-basis/legitimate-interests/when-can-we-rely-on-legitimate-interests/

14. ICO, Lawful basis, https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/lawful-basis/

15. ICO, Legitimate interests guide, https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/lawful-basis/a-guide-to-lawful-basis/legitimate-interests/

16. Dreamdata, Measuring G2 intent data impact, https://dreamdata.io/blog/benchmarks-report-measuring-g2-intent-data-impact-b2b-buyer-journeys

17. Dreamdata, About, https://dreamdata.io/about

18. Warmly, Identify Anonymous Website Visitors product page, https://www.warmly.ai/p/solutions/use-cases/website-visitor-identification

19. Warmly, Identify Website Visitors blog, https://www.warmly.ai/p/blog/identify-website-visitors

20. Warmly, main site, https://www.warmly.ai/

21. Koala, Intent Signals, https://getkoala.com/product/intent-signals

22. June, main site, https://www.june.so/

23. Common Room, main site, https://www.commonroom.io/

24. Diginomica, Twilio buys Segment for $3.2B, https://diginomica.com/twilio-buys-cdp-market-segment-acquisition

25. Crunchbase, Segment, https://www.crunchbase.com/organization/segment-io

26. RudderStack, Warehouse Native CDP, https://www.rudderstack.com/warehouse-native-cdp/

27. RudderStack, The Warehouse Native CDP blog, https://www.rudderstack.com/blog/the-warehouse-native-customer-data-platform/

28. RudderStack, Why your data warehouse should be the foundation of your CDP, https://www.rudderstack.com/blog/why-your-data-warehouse-should-be-the-foundation-of-your-cdp/

29. RudderStack, What is a Composable CDP, https://www.rudderstack.com/blog/what-is-a-composable-cdp/

30. Y Combinator, Hightouch, https://www.ycombinator.com/companies/hightouch

31. Contrary Research, Hightouch, https://research.contrary.com/company/hightouch

32. Hightouch, Reverse ETL, https://hightouch.com/platform/reverse-etl

33. VentureBeat, Hightouch reverse ETL, https://venturebeat.com/business/how-hightouch-uses-reverse-etl-to-sync-data-from-warehouse-to-saas-apps

34. Crunchbase, Census, https://www.crunchbase.com/organization/census-3975

35. Fivetran, Signs Agreement to Acquire Census, https://www.fivetran.com/press/fivetran-signs-agreement-to-acquire-census-delivering-the-first-end-to-end-data-movement-platform-for-the-ai-era

36. TechTarget, Fivetran adds reverse ETL with Census, https://www.techtarget.com/searchdatamanagement/news/366623554/Fivetran-adds-reverse-ETL-with-acquisition-of-Census

37. Snowflake, About, https://www.snowflake.com/en/company/overview/about-snowflake/

38. Wikipedia, Snowflake Inc., https://en.wikipedia.org/wiki/Snowflake_Inc.

39. Wikipedia, BigQuery, https://en.wikipedia.org/wiki/BigQuery

40. Google Cloud, BigQuery, https://cloud.google.com/bigquery

41. Y Combinator, Warmly, https://www.ycombinator.com/companies/warmly

42. Vector, Userled partnership, https://www.vector.co/blog/userled-vector-power-personalized-buyer-experiences-with-contact-level-intent-data

43. GeekWire, Common Room unveils platform, https://www.geekwire.com/2022/fueled-by-52m-in-funding-common-room-unveils-intelligent-community-growth-platform/

44. Contrary Research, Common Room, https://research.contrary.com/company/common-room

45. Y Combinator, June, https://www.ycombinator.com/companies/june

46. TechCrunch, June makes product analytics more accessible, https://techcrunch.com/2021/05/31/june-makes-product-analytics-more-accessible/

47. Silicon Canals, Dreamdata €6M round, https://siliconcanals.com/dreamdata-bags-6m/

48. Y Combinator, HockeyStack, https://www.ycombinator.com/companies/hockeystack

49. Userled, Series A announcement, https://www.userled.io/articles/userled-raises-4-million-to-deliver-ai-powered-personalized-marketing-campaigns

50. Usercentrics, Server-Side Tracking and GDPR, https://usercentrics.com/knowledge-hub/server-side-tagging-and-how-it-will-impact-consent/

51. Stape, Server-side tracking and GDPR, https://stape.io/blog/server-side-tracking-gdpr

52. Captain Compliance, Guide to server-side tracking, https://captaincompliance.com/education/the-complete-guide-to-server-side-tracking-advanced-strategies-for-privacy-first-data-collection-and-compliance/

53. Forrester, Identity Resolution blog, https://go.forrester.com/blogs/more-than-a-buzzword-master-the-identity-graph-to-unlock-the-value-of-identity-resolution/

54. Forrester, Now Tech: Identity Resolution Q3 2020, https://www.forrester.com/report/Now+Tech+Identity+Resolution+Q3+2020/-/E-RES162424

55. Acxiom / Forrester, The Strategic Role of Identity Resolution (PDF), https://marketing.acxiom.com/rs/982-LRE-196/images/The%20Strategic%20Role%20Identity%20Resolution_Forrester.pdf