Mida + Segment integration

Two-way sync: stream Mida test events into Segment, and ingest Segment track events into Mida as goals.

Analytics & Data Two-way sync Client-side Works with Mida A/B Testing & Personalization

About Segment

Segment (now part of Twilio) is the most widely used customer data platform (CDP). It collects events from your website, mobile apps, and servers, unifies them into a single customer profile, and forwards them to 300+ downstream destinations — analytics, marketing, advertising, warehouses.

How the Segment integration works

Mida ↔ Segment is a true two-way integration. Outbound, Mida calls analytics.track() and analytics.identify() with mida_pageview, mida_execute, and mida_conversion events. Inbound, Mida wraps Segment's analytics.track() so every event you already send to Segment is mirrored into Mida and can be used as a goal — no extra instrumentation required.

Requirements

  • Segment Analytics.js loaded on the page (window.analytics).
  • Mida tracking code installed on the page.

Use cases

Use any existing Segment event as a Mida goal

If your engineers already track 'Order Completed', 'Trial Started', or 'Demo Booked' through Segment, Mida picks those up automatically. You can pick any of them as a conversion goal in the Mida dashboard with zero new code.

Forward Mida exposures to every Segment destination

Once Mida events land in Segment, they fan out to Mixpanel, Amplitude, GA4, Customer.io, Snowflake, BigQuery, and every other destination you've enabled — one integration unlocks them all.

Run experiments and personalization on Segment audiences

Use Segment Personas / Engage to define an audience like 'High-value enterprise leads' and target Mida tests and personalization campaigns at exactly that audience for cleaner uplift signals.

Stream experiment data to your warehouse

With Segment's Snowflake, BigQuery, or Redshift destinations, every Mida exposure and conversion lands in your warehouse — perfect for long-term lift analysis and CUPED.

Shared data

Mida and Segment exchange the following events:

Event Direction Description
mida_pageview Data out analytics.track() called on every page after variant assignment.
mida_execute Data out analytics.track() called when a test executes on the current page.
mida_conversion Data out analytics.track() called on Mida goal completion.
* Data in Every Segment analytics.track() event is mirrored to Mida and selectable as a goal.

Frequently asked questions

Will the inbound mirror double-count events I already track?

No. The mirrored events are stored separately under Mida goals — they don't increase your Segment volume or duplicate downstream destinations.

Does Mida support Segment's server-side tracking?

Inbound events from server-side libraries land in Mida only if you also forward them to the browser via analytics.js. Pure server-side Segment events are not currently mirrored.

Which Segment plan do I need?

Any Segment plan that gives you analytics.js and at least one destination works. The Mida integration uses standard track and identify calls.

Ship A/B tests 10x faster — connected to your stack

Mida is the lightweight A/B testing and personalization platform that integrates with the tools you already pay for.