Analytics and tooling
Pertento for RudderStack
One exposure event into RudderStack fans out to every destination already configured, without a second integration.
One script tag · 0.9 KB · no cookiesAll integrations
RudderStack exists so that an event is written once and delivered everywhere, and Pertento uses it that way: the exposure is sent as a track call, and RudderStack routes it to the warehouse and to whatever tools are already wired up. Adding a destination later then needs no change here. If RudderStack is self-hosted, the exposure never passes through anybody else’s infrastructure on its way to your warehouse.
How it connects
- Send the exposure as a track call with the experiment and variant.
- Let existing destinations pick it up rather than wiring each one separately.
- Use the visitor identifier RudderStack already uses, so events join up.
More in Analytics and tooling
All integrationsGA4Forward the experiment and variant a visitor was assigned, so every GA4 report you already have can be segmented by the version they saw.How it connectsMatomoExposures sent to a Matomo instance you host yourself, so experiment data never leaves infrastructure you control.How it connectsPiwik PROConsent-aware analytics with the variant as a custom dimension, which suits regulated and public-sector sites.How it connects