New: The Agentic CDP

·Read the analysis

Tool · Personalization & Testing

Statsig integrations across CDPs

Directory data as of October 18, 2026

6 of the 44 customer data platforms in the CdpHub directory list an integration with Statsig, with 8 listings between them. Of those platforms, 2 both send data to Statsig and read from it and 4 only send data to it. 6 can run server-side and 2 in the warehouse. Every listing links to its platform's own documentation.

6of 44 CDPs list Statsig
8listings across them
2send data to Statsig and read from it
#138most listed of 2,243 tools

Which CDPs list Statsig

6 of 44
Sends data to Statsig Does both

Not listed by 38 CDPs: 6sense, ActionIQ, Adobe Experience Platform, Amperity, Bloomreach, BlueConic, Blueshift, Braze, CaliberMind, CleverTap, DinMo, Informatica, Insider One, Klaviyo, Leadspace, Lexer, Listrak, Lytics, Microsoft Dynamics 365 Customer Insights, NICE, Odie, Ometria, Optimizely, Oracle, Redpoint Global, Salesforce Data 360, SAP CDP, SAP Engagement Cloud, SAS, Simon Data, Snowplow, Spotler ActivatePro, Tealium, Teradata, Treasure AI, Upland BlueVenn, Zeotap and Zeta Global.

How each CDP connects to Statsig

6 CDPs · 8 listings
Chord (sends data to Statsig)1 listing
Chord → Statsig

Logs Chord events to Statsig through its server-side log_event API so orders and other events can act as experiment metrics, keyed to user and stable IDs.

All Chord integrations →
Fivetran Activations (sends data to Statsig)1 listing
Fivetran Activations → Statsig

Sends events from Fivetran Activations to Statsig, a partner-built destination that connects with an API key generated in Statsig.

All Fivetran Activations integrations →
Hightouch (sends data to Statsig)1 listing
Hightouch → Statsig

Syncs warehouse segments and logged events to Statsig for feature gates and experiments.

All Hightouch integrations →
mParticle (sends data to Statsig and reads from it)2 listings
mParticle → Statsig

Events. Forwards mParticle events to Statsig to measure feature flags and A/B tests.

Statsig → mParticle

Feed. Brings Statsig exposure events into mParticle as a feed.

All mParticle integrations →
RudderStack (sends data to Statsig)1 listing
RudderStack → Statsig

Sends RudderStack events of every type to Statsig to measure feature gates and A/B tests in production.

All RudderStack integrations →
Segment (sends data to Statsig and reads from it)2 listings
Segment → Statsig

Destination. Sends identify, track, page, group plus alias calls from Segment to Statsig for A/B testing and analytics in cloud mode.

Statsig → Segment

Source. Sends Statsig events into Segment as they happen, ready to route to other tools.

All Segment integrations →

Other Personalization & Testing tools

All tools on two or more CDPs →

About these numbers

CdpHub documents each integration from the platform's own catalog, so a listing records what the platform says it supports, not a test of the connector. Each one notes which way data flows and where the integration runs. A platform can list more than one connector for Statsig, so listings can outnumber platforms; a platform that both sends data to Statsig and reads from it is counted once, as doing both. The rank orders all 2,243 tools in the directory by how many platforms list them; tools listed on the same number of platforms share a rank. Counts are updated as catalogs change; this page reflects the directory as of October 18, 2026. CdpHub is independent and not affiliated with Statsig or any platform listed.

Connecting Statsig to a CDP?

Vendor-neutral help choosing the CDP that fits how you use Statsig, and getting the connection running in your stack.

Talk to CdpHub →

We use cookies to enhance your experience. By continuing to visit this site you agree to our use of cookies. Read our cookie policy