> For the complete documentation index, see [llms.txt](https://docs.humblytics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.humblytics.com/how-to-track-purchase-events/stripe.md).

# Stripe Revenue Attribution

Track revenue and attribute sales to your marketing campaigns, traffic sources, and A/B test variants with Stripe integration.

This guide covers:

* **Stripe API** - Pass visitor data through metadata
* **Stripe Payment Links** - Automatic tracking via session IDs
* **Other Stripe Methods** - Manual tracking with customer emails

Choose the method that best fits your Stripe implementation:

* [Stripe API](/how-to-track-purchase-events/stripe/stripe-api.md) - For custom checkout implementations
* [Stripe Payment Links](/how-to-track-purchase-events/stripe/stripe-payment-links.md) - For Stripe-hosted payment links
* [Other Stripe Methods](/how-to-track-purchase-events/stripe/stripe-other-methods.md) - For custom implementations, Stripe Elements, etc.

## Benefits

* **End-to-end attribution** - Connect sales to traffic sources and campaigns
* **Split test optimization** - Use revenue as conversion goals in A/B tests
* **Privacy-compliant** - Cookie-free tracking, no consent banners required
* **Real-time data** - Revenue data appears in your dashboard within \~30 seconds

## Prerequisites

* Your Stripe account is connected to Humblytics
* Your main website loads the Humblytics tracking script
* You have access to modify your checkout implementation

Check out the specific guides above to get started with your Stripe setup.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.humblytics.com/how-to-track-purchase-events/stripe.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.