Start with a business question, then inspect the evidence
Which campaign brought revenue? Did a landing page attract paying visits or only traffic? Did refunds change the result? A Stripe revenue attribution report helps you examine these questions alongside collected traffic, rather than treating a purchase-button click as a completed sale.
Use the same reporting period, currency and payment environment when comparing results. A matched payment supports an attribution relationship; it does not prove that a campaign caused the purchase. Keep unattributed revenue visible when judging the coverage of a report.
How Stripe revenue reaches Zijra
Connect your own Stripe account using a restricted key with the required read permissions. Zijra verifies the selected merchant and environment before saving the connection. Its import reads captured payments and succeeded refunds. Configured, signed webhooks can also deliver supported payment and subscription updates; connecting a key alone does not configure webhook delivery.
A payment needs a valid visitor link to become attributed. After accepted consented activity, the tracker can issue an encrypted checkout reference scoped to that website. Pass it through a supported checkout path. A provider-verified payment can then be associated with the matching visit without changing the financial receipt.
Choose the path that matches your checkout
Automatic checkout attribution may need additional Checkout Sessions and Invoice Payments read access. If those optional reads are unavailable, captured payments and refunds can still sync while the interface explains the attribution gap. Follow the guide for your checkout implementation instead of assuming every Stripe payment will match automatically.
| Checkout flow | What connects the payment to a visit |
|---|---|
| Checkout created by your server | Your server passes the consent-bound checkout context in the documented Stripe metadata fields. |
| Stripe Payment Links | The tracker can add its reference to eligible buy.stripe.com links after accepted consented activity. Existing merchant references are preserved. |
| A return page after checkout | A supported return check verifies a paid Checkout Session against Stripe and the original reference. A success URL alone is not payment proof. |
| An imported payment without a valid link | The payment remains in revenue totals as unattributed. Zijra does not invent a source or match customers by email. |
Read net revenue without confusing it with a bank payout
Zijra's net collected revenue subtracts succeeded refunds from captured payments in the selected currency and period. Test receipts remain separate from live receipts. Currencies are not silently combined or converted into a single total.
That figure is not your profit, Stripe balance or bank settlement. Fees, taxes, disputes, settlement timing and other accounting adjustments can produce different numbers. Stripe remains the authoritative payment record. Supported failed-payment lifecycle events can be recorded through configured delivery, but a failed attempt is not captured revenue.
Cookieless traffic and payment-linked visits have different boundaries
Aggregate tracking is the default and does not create a persistent cross-visit visitor identifier. Optional attribution links visits to payment references, which can point to an identifiable customer. Cookieless collection does not automatically establish a consent exemption for that processing.
Zijra requires valid visitor consent before storing optional attribution identity, linking visits or accepting identity supplied through checkout metadata. The short-lived checkout reference is kept in memory and may use the current tab's sessionStorage for return verification. These mechanisms are separate from aggregate-only tracking.
Withdrawal clears the tracker's reference and requests removal of linked history. Financial records and provider metadata have separate retention boundaries. Review your notices, lawful basis and withdrawal controls, and use the DPA when assessing Zijra as a processor for your business.
Looking for a Stripe and Google Analytics connection?
GA4 can report ecommerce revenue when purchase and refund events are implemented. Its ecommerce reports do not require a BigQuery export. If you need revenue inside GA4, follow Google's ecommerce event specification and use an implementation appropriate to your checkout.
Zijra is a separate analytics product with a native Stripe import and its own reporting model. Connecting Stripe to Zijra does not send purchases into Google Analytics or migrate GA4 audiences. It suits a focused traffic-and-revenue workflow; keep GA4 where you need its advertising ecosystem or broader ecommerce analysis.
Revenue attribution starts on Free
Free includes 10,000 events per month, one website, six months of detailed history, three goals and one funnel. Stripe revenue attribution is included. The allowance is measured in events, including accepted pageviews and custom events, rather than pageviews alone.
Founder starts at $5 per month for 100,000 events. Paid plans add journeys, API and MCP access alongside higher allowances. Choose a plan by your expected usage and workflow; you do not need a paid plan simply to unlock Stripe revenue reporting.
Verify the connection before using the numbers
Begin with the installation and Stripe guides. A verified import is a useful first milestone; a verified match is a separate attribution check. Keep both visible as your checkout changes.
- Check that the connected Stripe merchant and live or test environment match the report you intend to read.
- Complete the required sync and inspect a known captured payment and any succeeded refund against Stripe.
- Verify a consented checkout reference through your chosen setup path. A payment without a valid visit link should remain unattributed.
- Compare like-for-like dates and currencies. Do not treat missing delivery, a connection error or an incomplete sync as zero sales.
Common questions
Sources & further reading
This is a Zijra product guide. We sell one of the products discussed, and we link to the other providers’ own documentation so you can assess the trade-offs.
A CLEARER NEXT STEP
Start with your own activity.
10,000 events a month, one website and Stripe revenue attribution on Free. No card required.