Public-page stack intelligence
B2B SaaS Companies Using Segment: Public Website Signals
We found 27 claim-ready Segment signals in 243 normal-status B2B SaaS and software domains. This page highlights selected companies and co-signals from the reviewed public-page crawl. It is not a list of confirmed Segment customers or internal customer-data platforms of record.
Segment public signals
27
B2B SaaS denominator
243
Visible share
11%
Verdict
Segment was a meaningful but selective B2B SaaS public-page signal. It usually appeared with tag management, analytics, and paid acquisition signals rather than as a standalone clue. Read Segment as customer-data or event-routing context, not as proof of a full internal CDP architecture.
Selected B2B SaaS Companies With Segment Signals
These are reviewed examples with enough surrounding public-page evidence to interpret. We prioritized profiles where Segment appeared alongside analytics, paid-media, automation, support, or behavior-research signals.
Dialpad
dialpad.comSegment on homepageSegment appeared alongside Marketo, GTM, GA4, and paid media tags from Google, LinkedIn, Meta, Microsoft, and TikTok.
9 signals
Published profile
Gorgias
gorgias.comSegment on homepageSegment appeared with HubSpot, Hotjar, GTM, GA4, and paid media tags from Google, LinkedIn, Meta, and Microsoft.
9 signals
Published profile
Bubble
bubble.ioSegment on homepageSegment appeared with Intercom, Hotjar, GTM, LinkedIn Insight, Meta Pixel, Microsoft Ads, and TikTok Pixel.
8 signals
Published profile
Cockroach Labs
cockroachlabs.comSegment on homepageSegment appeared with Marketo, GTM, GA4, Google Ads, LinkedIn Insight, and Meta Pixel, giving the profile customer-data and acquisition context.
7 signals
Published profile
Close
close.comSegment on homepageSegment appeared with GTM, GA4, Google Ads, LinkedIn Insight, Meta Pixel, and Microsoft Ads in the reviewed public-page crawl.
7 signals
Published profile
Meilisearch
meilisearch.comSegment on homepageSegment appeared with HubSpot, Hotjar, GTM, GA4, Google Ads, and Meta Pixel across the public-page crawl.
7 signals
Published profile
Common Co-Signals Around Segment
Segment rarely appeared alone in stronger examples. The table below shows selected co-signals found among the 27 B2B SaaS domains with Segment evidence.
Google Tag Manager
89%
24 of 27. Most Segment-signal pages also exposed tag-management infrastructure.
Google Analytics 4
59%
16 of 27. GA4 was the most common analytics co-signal in the Segment subset.
Google Ads
44%
12 of 27. Google Ads signals showed paid-search context around many Segment pages.
LinkedIn Insight
44%
12 of 27. LinkedIn Insight matched Google Ads in the Segment-signal subset.
Meta Pixel
41%
11 of 27. Meta Pixel rounded out the visible paid-social and retargeting layer.
Microsoft Ads
41%
11 of 27. Microsoft Ads appeared often enough to matter for B2B acquisition tracking.
Other Reviewed Segment-Signal Examples
The reviewed Segment-signal set also included companies such as PandaDoc, incident.io, Nutshell, Buildkite, Bill.com, New Relic, Box, MongoDB, Contentful, Buffer, WorkOS, and Clearbit. We are not publishing this as a raw directory because public-page evidence is most useful when paired with context and caveats.
How to Use This Page
For account research
Use Segment signals as a clue for event collection, analytics routing, attribution, or product-led customer-data workflows that should be verified.
For stack interpretation
Compare Segment examples against HubSpot and Marketo examples to see how customer-data signals sit beside CRM and automation signals.
For methodology
Keep the claim narrow: visible public-page signals do not prove paid customer status or internal systems of record.
Related Research
B2B SaaS GTM Stack Benchmarks
Review the broader 250-domain B2B SaaS benchmark data.
B2B SaaS Companies Using HubSpot
Compare Segment public-signal examples against CRM-led HubSpot public-page signals.
B2B SaaS Companies Using Marketo
Compare Segment public-signal examples against enterprise automation Marketo signals.
B2B SaaS Marketing Stack
Read the editorial explanation of how these public-page signals fit together.
Company Stack Profiles
Browse selected public-page stack profiles for B2B SaaS companies.
Best Marketing Automation Software for B2B GTM
Use the benchmark context to shortlist automation platforms by operating model.
Methodology Notes
This page uses the B2B SaaS/software cohort from the SoftwareInspect public-page stack study. The denominator is 243 normal-status domains from a 250-domain reviewed sample.
A domain appears in the Segment-signal set only when the crawl found high-confidence Segment evidence that passed exclusion checks for headline claims and customer claims. Low-confidence-only rows, non-normal status domains, and excluded detections are not counted here.
These are browser-visible public-page signals. They should not be read as Segment market share, customer counts, paid account status, internal CDP adoption, or private application usage.
Frequently Asked Questions
Are these confirmed Segment customers?
No. This page shows B2B SaaS companies with reviewed public-page Segment signals. A signal can support account research, but it does not prove paid customer status, internal CDP ownership, or current contract status.
What counts as a Segment signal?
A Segment signal means the reviewed public-page crawl found high-confidence Segment evidence that passed SoftwareInspect exclusion checks. Evidence can come from scripts, network requests, browser globals, analytics libraries, or other visible public-page signals.
Why not publish all 27 domains as a directory?
A raw list would be less useful and easier to overread. This page keeps the claim narrow, shows aggregate counts, and highlights selected reviewed examples where Segment appears with enough surrounding GTM context to interpret.
Does a Segment public-page signal prove Segment is the internal CDP?
No. A company can expose Segment on a public page for event collection, analytics routing, campaign attribution, or tag coordination while using other internal data systems. Treat the signal as a clue that needs verification.