Connect Stripe once and judge experiments on money instead of clicks. Mida links each successful payment back to the variant the buyer saw and reports revenue, RPV, and AOV per variant.
Stripe is the payments platform behind a large share of online checkouts, Payment Links, and subscription businesses. If your revenue runs through Stripe, this integration turns every successful payment into a conversion Mida can attribute to an experiment — no tag manager work and no manual revenue imports.
Mida registers a webhook on your Stripe account and records every successful payment server-side. Each payment is linked to an exposed visitor in one of three ways. (1) Metadata: set metadata.mida_uuid on the PaymentIntent or Checkout Session to the value of the optimize_uuid cookie. (2) Payment Links and Checkout: pass client_reference_id — the Mida tag decorates buy.stripe.com links automatically and reads ?session_id={CHECKOUT_SESSION_ID} on your thank-you page, so hosted Payment Links need no code at all. (3) Email: the customer email on the payment is matched to a visitor Mida has already identified. Linked payments become Purchase events, so a Revenue goal reports conversion rate, revenue, revenue per visitor, and average order value for every variant.
A variant can win on checkout starts and still lose on money. With Stripe connected, Mida reports revenue per visitor and average order value next to conversion rate, so you deploy the variant that actually earns more.
The Mida tag adds client_reference_id to buy.stripe.com links and reads the session id back on your thank-you page. Landing pages that sell through Payment Links get full revenue attribution without a developer.
Compare plan ordering, price anchoring, trial length, or a one-step vs multi-step checkout and measure the result in settled Stripe payments rather than button clicks.
Payments reach Mida over a signed Stripe webhook, so ad blockers, consent tooling, and client-side tag failures don't silently erase your revenue numbers.
Mida and Stripe exchange the following events:
| Event | Direction | Description |
|---|---|---|
Purchase |
Data in | One event per successful Stripe payment linked to an exposed visitor, carrying revenue, currency, order_id, stripe_payment_intent, and source. |
Not unless you switch them on in the integration config. The first invoice of a subscription always counts, so new subscribers are credited to the test that won them.
The refund reduces the revenue of the original payment but does not remove the conversion, so conversion rate and revenue stay internally consistent.
Use one purchase source per project. Running Stripe next to the Shopify pixel or your own Purchase events double counts revenue.
No. A restricted key with read access to payment objects plus write access to webhook endpoints is enough, and you can rotate or disconnect it from Mida at any time.
Mida is the lightweight A/B testing and personalization platform that integrates with the tools you already pay for.
Still deciding?
A quick screen share on your actual site — no slides, no generic tour. Just your questions answered.
30 min · no commitment · no sales pressure