Stripe

Track Stripe revenue and customer activity across every campaign.

Payment provider
Built by
Spectacle

Connect Stripe payments to marketing attribution

See which campaigns, channels, and touchpoints drive actual revenue—not just leads. Spectacle links every Stripe payment, refund, and subscription event to the full multi-touch journey, so you can optimize for what matters: cash in and LTV out.

TL;DR

  • Revenue attribution: Tie payments (not just form fills) back to the touchpoints that influenced them.

  • LTV & cohort tracking: Identify channels that drive longer retention and higher expansion.

  • Subscription insights: See trial-to-paid and upgrade paths by source/medium/campaign.

  • Refund-aware ROI: Adjust attributed value when refunds, chargebacks, or downgrades happen.

  • Ad platform feedback loops: Sync server-side conversions to Google Ads, Meta, and LinkedIn for smarter bidding.

Why Connect Stripe to Spectacle?

Most analytics stops at “lead.” Revenue often lands weeks or months later in Stripe. When you only optimize to MQLs or demo requests, you funnel budget to cheap signups instead of profitable customers. Connecting Stripe closes the loop:

  • True ROAS, not limited to proxy metrics: Evaluate campaigns by payments, MRR, ARR, refunds, and LTV—not clicks.

  • Multi-currency sanity: Report in one currency while selling in many. (Stripe supports 135+ currencies; we’ll normalize to your reporting currency.) Stripe Docs

  • CFO-friendly: Prove marketing’s revenue contribution with the same source of truth Finance uses—Stripe.

How it works

  1. Secure connection Connect Stripe to Spectacle using OAuth (read-only) or a Restricted API Key with read scopes only. OAuth supports read_only scope specifically for platform integrations; Restricted Keys can be configured per-endpoint for least-privilege. Stripe Docs

  2. Automatic sync (near real-time) We ingest payment events (e.g., payment_intent.succeeded) and continuously reconcile updates (refunds, disputes, cancellations). Stripe Docs

  3. Journey mapping Spectacle matches Stripe objects to people and accounts, stitching first-touch → assist → conversion using your tracking (GCLID/FBP/FBC/LI_FATID, UTMs, first-party IDs).

  4. Revenue insights Dashboards attribute payments, MRR, net revenue, and LTV to the journeys that caused them. Refunds and adjustments reduce attributed value automatically.

What we ingest from Stripe (and what we do with it)

Stripe Object / Event

Key Fields We Read

What Spectacle Uses It For

Payment Intent (payment_intent.succeeded)

id, amount, currency, customer, metadata, payment_method, status

Cash conversion attribution & revenue value. Stripe Docs

Refund (charge.refunded, refund.created)

amount, currency, reason, charge

Conversion value de-attribution, net revenue accuracy. Stripe Docs

We don’t consume other Stripe objects or events (e.g., invoices, subscriptions, disputes). If you need more, tell us and we can extend the integration.

LTV & multi-currency handling

  • Set a reporting currency (EUR, USD, etc.).

  • For multi-currency accounts, Spectacle can use Stripe’s FX/Exchange Rates or your preferred rate source to normalize values consistently. Choose daily FX rate windows to avoid noisy intraday swings. Stripe Docs

  • LTV is computed at account / company level (optionally person level), aggregating Stripe invoices and adjustments over time.

Sync conversions back to ad platforms (optional, but recommended)

Close the loop with server-side conversions so bidding algorithms optimize for revenue and LTV, not cheap leads.

  • Google Ads: Import offline conversions / enhanced conversions (with hashed email/phone) tied to GCLID/GBRAID/WBRAID or user data. Google for Developers

  • Meta (Facebook/Instagram): Send purchases and value via Conversions API, improving match and optimization without relying on the pixel. Facebook for DevelopersFacebook

  • LinkedIn: Send server-side conversions with value via LinkedIn Conversions API, including deeper-funnel events. Microsoft Learn

Meta and Linkedin Currently in Private beta, please reach out and we will connect to you.

You control which events get synced (e.g., initial payment only, every renewal, or upgrades >€X). You can also set complex conversions to reduce noisy signals.

Field mapping quick-reference

Spectacle Field

Stripe Source

Notes

transaction_id

payment_intent.id or charge.id

Prefer PaymentIntent as primary key. (Stripe Docs)

amount / currency

amount_received, currency

Normalized to reporting currency if enabled.

customer_id

customer.id

Used to stitch to user/account.

refund_amount

refund.amount

De-attribution logic on value. (Stripe Docs)

occurred_at

event.created

Canonical event time. (Stripe Docs)

Security & privacy

  • Least privilege by default: Use OAuth read_only. Stripe Docs

  • Verified webhooks: We verify Stripe signatures and require HTTPS. Stripe Docs

  • PII handling: When sending conversions back to ad platforms, Spectacle can hash PII (SHA-256) and respect platform-specific requirements for enhanced/offline conversions. Google Help

FAQs

Does this pull historical data? No, we synchronise data from first connect, meaning you will retrieve attribution windows from that moment.

What about refunds and chargebacks? We ingest refund events and disputes and reduce or zero out the attributed value depending on your rules. Stripe Docs

We sell globally—can we normalize to one currency? Yes. Stripe supports 135+ currencies; Spectacle converts to your reporting currency using a consistent FX source. Stripe Docs

Can we send conversions back to ads with value? Yes—server-side syncs are available for Google Ads, Meta, and LinkedIn, including value and order IDs. Google for Developers/ Facebook for Developers / Microsoft Learn

Connect Stripe Integration →

View Revenue Attribution →

View Spectacle on Stripe Marketplace →