# Google Analytics 4 + Stripe integration and analysis

Connect Google Analytics 4 and Stripe to Hendrik. Use GA4 observed purchase or funnel events with Stripe payment and refund data to distinguish website measurement from processor outcomes.

## The question this stack can answer

Do GA4 purchase events line up with Stripe payments?

## What Hendrik reads from each source

- **Google Analytics 4:** Traffic acquisition, landing pages, and on site events show where the website journey changed.
- **Stripe:** Payments, refunds, and disputes show whether money was collected after an order was placed.

## What you need to connect

- Use one explicit 28-day comparison window, time zone, market, and legal-entity scope before comparing values.
- Connected GA4 property with comparable acquisition and event reporting.
- Connected Stripe account with payment, refund, and dispute data for the same legal entity.
- Keep provider-specific definitions visible and use an identity or product mapping only where it is established for this workspace.

## Important limits

- GA4 events and attribution do not automatically establish a paid order, payment, or campaign relationship.
- Payments must not be added to storefront or marketplace revenue; transaction reconciliation needs a proven payment relationship.

## Illustrative example

### Google Analytics 4 + Stripe review

Previous: 1–28 January. Current: 29 January–25 February. Both periods contain 28 days. Monetary values use USD and all timestamps use UTC.

*About this example: Synthetic data · illustrative analysis · Hendrik only acts with the permissions you give it.*

- reported purchase events (count, 28 days) (Google Analytics 4): 1,420 → 1,230
- successful payment amount (USD, 28 days) (Stripe): 102,000 USD → 94,000 USD
- GA4 paid sessions (configured channel group, consecutive 28-day periods) (Google Analytics 4): 16,800 → 15,300

### What Hendrik checks

- **Traffic measurement:** Check GA4 property, timezone, consent coverage, source definition, and event configuration before comparing sessions or transactions.
- **Payment and refund scope:** Check Stripe payment, refund, dispute, and balance-transaction dates. Establish an order-to-payment reference before reconciliation.
- **Explain the divergence:** Google Analytics 4: reported purchase events (count, 28 days) changed from 1,420 to 1,230. Stripe: successful payment amount (USD, 28 days) changed from 102,000 USD to 94,000 USD. Compare the timing and definitions before attributing one change to the other.

### What Hendrik sees

GA4 reported purchase events and paid sessions fell. Stripe successful payment amount fell.

### What to do next

Check tracking and processor timing before drawing an acquisition conclusion; reassess after event and payment definitions are documented.

**Limit:** A GA4 purchase event is not automatically a Stripe payment or refund match.

## Provider documentation

- [Google Analytics 4 documentation](https://support.google.com/analytics/)
- [Stripe documentation](https://docs.stripe.com/reports)

## Start with this stack

[Create a workspace and connect Google Analytics 4 + Stripe](https://app.withhendrik.com/auth?mode=sign-up&acquisition_channel=marketing&return_to=%2Fonboarding%2Factivation&cta_location=integration_markdown&landing_page_id=combination-ga4-stripe&combination=ga4-stripe)