Google Floodlight Mobile App Conversion
Last updated
Was this helpful?
Last updated
Was this helpful?
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.
The Google Floodlight Mobile App Conversion destination provides the following key features:
Events structure: our covers , 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 array is dispatched to Floodlight.
Some setup is required on the Floodlight side before configuring this destination. See more details by following this (See section Set up Floodlight in apps
→ Ensure ad tags pass proper values from publishers
).
Advertiser Id
Group Tag String
Activity Tag String
Custom Event Properties
Send custom properties ( u
, tran
, num
, u1
, u2
, etc...) related to events.
[Any Event]
[1]
[Any Conversion]
[1]
Advertiser Id
src
[*]
Group Tag String
cat
[*]
Activity Tag String
type
[*]
context.device.advertising_id
dc_rdid
[*]
partners.google.cdt
tag_for_child_directed_treatment
context.device.ad_tracking_enabled
dc_lat
items.X.quantity
qty
[1]
revenue
cost
id
ord
[2]
items.X.product.id
items.X.product.price
items.X.quantity
prd
Your value
[3]
Floodlight property name
[3]
Required
This is the value of the src
parameter. More details are available following this .
Required
This is the value of the type
parameter. More details are available following this .
Required
This is the value of the cat
parameter. More details are available following this .
[1] Use to refine events matching your specific needs.
[*] Mandatory property.
[1] Sum of each product quantity.
[2] If no property is provided, a random generated number is used.
[3] See Custom Event Properties
in for more details on how you can add custom properties.