Grometrics
Log in
Back to Guides

Setup

8 min read

Set up revenue tracking with Stripe

Connect Stripe revenue so Grometrics can attribute new sales, renewals, and refunds back to acquisition.

The question

Stripe tells you that money arrived. Grometrics needs to know what caused that money to arrive.

Connecting Stripe closes the loop between traffic, behavior, and payment so revenue can show up beside source, campaign, page, and customer path.

The concept

Revenue tracking works when a payment event can be tied to the visitor or customer journey that created it. That lets reports show new revenue, renewals, refunds, and source context together.

Without the payment connection, you can still see traffic and conversions, but you cannot trust channel revenue, CAC, ROAS, or payback.

Before you connect

Make sure the Grometrics tracking script is installed on the site or app that sends people to checkout. Stripe can provide the payment event, but the visitor path needs to exist before payment.

If your product uses custom checkout flows, keep customer email, checkout session, or client reference identifiers consistent wherever possible. Matching identifiers make attribution cleaner.

1. Install tracking

Capture the visitor journey before checkout starts.

2. Confirm the domain

Make sure the checkout flow belongs to the same product you are analyzing.

3. Know your mode

Use live Stripe data for real reporting. Use test mode only for setup verification.

4. Decide revenue types

Know whether you need new sales only, subscriptions, renewals, refunds, or all of them.

The walkthrough

Open Integrations, connect Stripe, verify the account, then trigger or import a test payment so the revenue event appears in Grometrics.

After the connection is active, inspect a recent transaction and confirm that source context is present. The setup is only complete when payment and acquisition data meet.

Mock Integrations view showing Stripe connected before revenue attribution is trusted.

1. Connect Stripe

Use the Stripe integration card and complete the authorization or key setup.

2. Verify events

Confirm new payments, renewals, and refunds are arriving.

3. Check attribution

Open Revenue or Attribution and confirm payments have source context.

4. Review recent sales

Look at a few known transactions and make sure the source story matches reality.

What to verify

A successful connection does not automatically mean attribution is useful. Verify the data against a few real customer paths.

You want to see the transaction amount, currency, customer, revenue type, timestamp, and source context together.

1. New revenue

First purchases should appear as acquisition revenue, not renewals.

2. Renewals

Subscription renewals should count toward customer value without lowering acquisition CAC.

3. Refunds

Refunds should reduce net revenue so bad-fit campaigns are visible.

4. Source context

Payments should connect to source, campaign, landing page, or visitor history whenever available.

Troubleshooting

If payments appear without attribution, the payment connection may be fine while tracking or identity matching is incomplete.

Check whether the tracking script loaded before checkout, whether visitors move across domains, and whether the checkout flow strips identifiers before Stripe receives the session.

1. No payments

Recheck Stripe authorization, mode, permissions, and webhook status.

2. No source

Verify the visitor was tracked before payment and the checkout path preserves identity.

3. Wrong revenue type

Confirm whether the payment is a new sale, renewal, refund, or adjustment.

4. Missing refunds

Make sure refund events are enabled so net revenue stays honest.

Decision framework

Revenue tracking is not finished when payments import. It is finished when those payments can be grouped by source, page, campaign, and customer path.

Once Stripe is connected and verified, use attribution reports to judge channels by payment-backed revenue instead of signup or checkout counts.

Rule of thumb: Stripe data without source context is finance reporting, not growth reporting.

Try it in your data

Open Integrations to connect Stripe and start attributing revenue to sources.

Start tracking for free →

Related guides

Attribution

8 min read

Where did that sale actually come from?

Trace a sale back to the source, page, and session that created it without guessing from payment data alone.

CAC & ROAS

9 min read

Calculate your real CAC (not the one Meta reports)

Compare platform-reported acquisition cost with actual customers, refunds, payback, and payment-backed revenue.