> For the complete documentation index, see [llms.txt](https://docs.adpage.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adpage.io/app-tracking/google-ads-app-conversions.md).

# Google Ads app conversions

Why app conversions for Google Ads do not run through the server container, and which route to use instead.

{% hint style="info" %}
**Status: outline.** The direction is settled, the exact steps are open.
{% endhint %}

## 1. What Google Ads needs for app conversions

Not a server container tag. The Google Ads conversion tag in a server container works with the click identifiers that a browser carries, `gclid`, `gbraid` and `wbraid`, stored in cookies. An app has none of these, so the tag has nothing to attribute the conversion with.

App conversions reach Google Ads over a different route: through the link between the GA4 property and Google Ads, or through an app attribution partner.

{% hint style="warning" %}
Building a Google Ads conversion tag on the App client anyway produces requests that leave with a 200 and land nowhere. Do not do it, and if you find one in an existing container, remove it.
{% endhint %}

## 2. What you set up on the Google side

* The GA4 property linked to the Google Ads account.
* The app conversion event imported as a conversion action in Google Ads.
* **Open:** write out the exact steps, and confirm how the imported app conversion appears next to the existing web conversions.

## 3. Tag configuration

None in the server container. The GA4 app event is the source, so what matters is that the GA4 page is correctly implemented.

## 4. Identifiers this platform accepts

Not applicable over this route. Attribution comes from the GA4 and Google Ads link.

**Open:** determine whether enhanced conversions for leads is usable with an app sourced email address, and under which conditions.

## 5. How to test

**Open:** describe how to verify an imported app conversion in Google Ads, and the delay to expect before it appears.

## 6. Known errors

Not applicable. The failure mode here is not an error but an absence: nothing arrives, because there is nothing to arrive.

## 7. Limits

* App install campaigns and in-app conversions are a separate area, with their own attribution model and, on iOS, SKAdNetwork.
* **Open:** decide whether AdPage supports this, or whether it is handed to an app attribution partner. Write down the answer here, because it is the first question a client asks.


---

# 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.adpage.io/app-tracking/google-ads-app-conversions.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.