> For the complete documentation index, see [llms.txt](https://doc.commandersact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.commandersact.com/features/destinations/destinations-catalog/google/google-floodlight-mobile-app-conversion.md).

# Google Floodlight Mobile App Conversion

[Floodlight](https://support.google.com/searchads/answer/7298761?hl=en) provides you insight into the actions that users take after they view or click on ads. Using this destination you can track installs of your app or activities that take place in the app.

## Key features

The Google Floodlight Mobile App Conversion destination provides the following key features:

* **Events structure**: our [Events reference](https://doc.commandersact.com/developers/tracking/events-reference) covers [Floodlight ability to track in-app actions](https://support.google.com/sa360/answer/14442341?hl=en), meaning that your data is properly bridged to the expected fields in an optimized way.
* **Prebuilt mappings**: data mapping for event-based destinations happens automatically, which simplifies user inputs.
* **Refined data**: you can freely push additional custom event properties based on your specific needs.
* **Smart mapping**: data mapping can be readjusted using your datalayer defined fields.
* **Support for multi-item data**: information included in the [item](https://doc.commandersact.com/developers/tracking/events-reference#item) array is dispatched to Floodlight.

## Destination setup

{% hint style="warning" %}
Some setup is required on the Floodlight side before configuring this destination. See more details by following this [LINK ](https://support.google.com/sa360/answer/14442341?hl=en)(See section <mark style="color:blue;">`Set up Floodlight in apps`</mark> → <mark style="color:blue;">`Ensure ad tags pass proper values from publishers`</mark>).
{% endhint %}

### Configuration

<table data-header-hidden="false" data-header-sticky><thead><tr><th width="300">Settings</th><th>Description</th></tr></thead><tbody><tr><td><code>Advertiser Id</code></td><td><em><strong><code>Required</code></strong></em><br>This is the value of the <code>src</code> parameter. More details are available following this <a href="https://support.google.com/tagmanager/answer/6107168">LINK</a>.</td></tr><tr><td><code>Group Tag String</code></td><td><em><strong><code>Required</code></strong></em><br>This is the value of the <code>type</code> parameter. More details are available following this <a href="https://support.google.com/tagmanager/answer/6107168">LINK</a>.</td></tr><tr><td><code>Activity Tag String</code></td><td><em><strong><code>Required</code></strong></em><br>This is the value of the <code>cat</code> parameter. More details are available following this <a href="https://support.google.com/tagmanager/answer/6107168">LINK</a>.</td></tr><tr><td><code>Custom Event Properties</code></td><td>Send custom properties ( <code>u</code> , <code>tran</code> , <code>num</code> , <code>u1</code> , <code>u2</code> , etc...) related to events.</td></tr></tbody></table>

## Quick reference

| Commanders Act Events  | Floodlight conversion       |
| ---------------------- | --------------------------- |
| `[Any Event]` **\[1]** | `[Any Conversion]` **\[1]** |

{% hint style="info" %}
**1.** Use [Destination filters](https://doc.commandersact.com/features/destinations/destination-filters) to refine events matching your specific needs.
{% endhint %}

## Field mappings

<table data-header-hidden="false" data-header-sticky><thead><tr><th>Smart Mapping Fields</th><th>Commanders Act Default Properties</th><th>Floodlight Properties</th></tr></thead><tbody><tr><td><code>-</code></td><td><code>Advertiser Id</code></td><td><code>src</code> <strong>[*]</strong></td></tr><tr><td><code>-</code></td><td><code>Group Tag String</code></td><td><code>cat</code> <strong>[*]</strong></td></tr><tr><td><code>-</code></td><td><code>Activity Tag String</code></td><td><code>type</code> <strong>[*]</strong></td></tr><tr><td><code>Device Mobile Identifier</code></td><td><code>context.device.advertising_id</code></td><td><code>dc_rdid</code> <strong>[*]</strong></td></tr><tr><td><code>Child Directed Treatment</code></td><td><code>partners.google.cdt</code></td><td><code>tag_for_child_directed_treatment</code></td></tr><tr><td><code>Ad Tracking Enabled</code></td><td><code>context.device.ad_tracking_enabled</code></td><td><code>dc_lat</code></td></tr><tr><td><code>Transaction Revenue</code></td><td><code>revenue</code></td><td><code>cost</code></td></tr><tr><td><code>Transaction Id</code></td><td><code>id</code></td><td><code>ord</code> <strong>[1]</strong></td></tr><tr><td><code>Item Quantity</code></td><td><code>items.X.quantity</code></td><td><code>qty</code> <strong>[2]</strong></td></tr><tr><td><p><code>Item Id</code></p><p><code>Item Price</code></p><p><code>Item Quantity</code></p></td><td><code>items.X.product.id</code> <br><code>items.X.product.price</code> <br><code>items.X.quantity</code></td><td><code>prd</code></td></tr><tr><td><code>-</code></td><td><code>Your value</code> <strong>[3]</strong></td><td><code>Floodlight property name</code> <strong>[3]</strong></td></tr></tbody></table>

{% hint style="info" %}
**\*** Mandatory property.\
**1.** If no property is provided, a random generated number is used.\
**2.** Sum of each product quantity.\
**3.** See <mark style="color:blue;">`Custom Event Properties`</mark> in [Configuration ](#configuration)for more details on how you can add custom properties.
{% endhint %}


---

# 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://doc.commandersact.com/features/destinations/destinations-catalog/google/google-floodlight-mobile-app-conversion.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.