> 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.md).

# How to Track Purchase Events

You can now track purchase events in Humblytics - enabling you to connect end-to-end customer journeys from landing page to checkout.

This update allows you to:

* Attribute sales to traffic sources, campaigns, and split test variants
* Use completed purchases as conversion goals in A/B tests
* Build accurate funnels from first visit to final transaction
* Optimize for revenue, not just clicks

## Available Integrations

* [**Stripe**](/how-to-track-purchase-events/stripe.md) - Complete revenue attribution for Stripe payments
* [**Foxy**](/how-to-track-purchase-events/foxy.md) - Track Foxycart purchase events

Check out the setup guides above to get started with your preferred payment processor.


---

# 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:

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

The question should be specific, self-contained, and written in natural language.
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.