> For the complete documentation index, see [llms.txt](https://docs.devtodev.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devtodev.com/integration/autocapture.md).

# Autocapture

Autocapture is a set of features in devtodev that allows you to collect data automatically, without manually sending events from the client side. It is designed to simplify integration, reduce engineering effort, and ensure data consistency across platforms.

Currently, Autocapture supports purchase tracking, refund tracking, and AI-assisted integration. Web auto-tracking is in development.

## How it works

Each Autocapture feature collects data from validated sources such as the App Store, Google Play, or SDK behavior. In most cases, you only need to enable the feature in the devtodev settings and initialize the SDK accordingly. No additional coding is required.

## How to set up

* [Automatic payment tracking](/integration/autocapture/automatic-payment-tracking.md)
* [Automatic refund tracking](/integration/autocapture/automatic-refund-tracking.md)
* [AI-assisted integration for Unity](/integration/integration-of-sdk-v2/sdk-integration/unity/ai-assisted-integration-beta.md) 

## Compatibility and limitations

* Autocapture is available only for native payment systems (Google Play and App Store).
* Unity Android refund tracking is not supported due to store receipt limitations.
* Do not mix manual and automatic event tracking for the same transaction types.
* Web tracking will be available via the [devtodev Web SDK](/integration/integration-of-sdk-v2/sdk-integration/web.md) (currently in development).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devtodev.com/integration/autocapture.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.