> For the complete documentation index, see [llms.txt](https://docs.truecaller.com/truecaller-sdk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.truecaller.com/truecaller-sdk/mobile-websites/getting-release-ready/instrumentation.md).

# Instrumentation

Quick guide on how to properly track and instrument funnel for the verification flow of users via Truecaller on your mobile website

For proper tracking of the verification funnel via Truecaller on your app, you should implement tracking events for the following states :

1. Total users coming to your verification flow.
2. Number of cases when the Truecaller app is present on your device - can be appropriately known using the javascript condition as described in the [invoking verification](https://docs.truecaller.com/truecaller-sdk/mobile-websites/integrating-with-your-mobile-website/invoking-verification) section.
3. Number of users who proceed with this flow and click Continue on the Truecaller dialog \[ for these cases, you receive a success response with user's access token on the callback URL configured by you ]. For details, refer [here](https://docs.truecaller.com/truecaller-sdk/mobile-websites/integrating-with-your-mobile-website/fetch-user-profile).
4. Number of cases where you received any error, where you receive an error response with 'user\_rejected' message on the callback URL configured by you. For details, please refer [here](https://docs.truecaller.com/truecaller-sdk/mobile-websites/integrating-with-your-mobile-website/handling-error-scenarios).
5. Number of successful profiles fetched by your backend post receiving the access token from Truecaller's backend on your callback URL. For details, refer [here](https://docs.truecaller.com/truecaller-sdk/mobile-websites/integrating-with-your-mobile-website/fetch-user-profile).
6. Number of successful communications between your backend and frontend post fetching the user's profile information to complete the verification flow.


---

# 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.truecaller.com/truecaller-sdk/mobile-websites/getting-release-ready/instrumentation.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.