Objective
- To prevent data from all calls being sent to every GA4 property.
- To only send call data to each GA4 property that is associated with the property.
Applies To
- Customers with multiple GA4 properties.
- Customers setting up a net new Google Analytics integrations.
- Customers migrating from Universal Analytics who currently filter call data to multiple UA properties.
Procedure
- Sync with your Invoca rep on what the best lookup field to use is to determine which GA4 property the call data will be filtered to (in this case it is "Location," other common use cases are "Detected Destination" or "Domain").
- Create new Short-Text MDFs for the lookup field, GA4 Measurement ID, and GA4 API Secret (Partner Names: ga_measurement_id, ga_api_secret)
- Create a Lookup Table with the lookup field in column A, the Measurement ID field in Column B, and The API Secret field in column C.
- Compile the lookup field values and the associated GA4 property Measurement IDs and API Secrets into the table.
- When setting up your GA4 integration Connect App, insert the Measurement ID and API Secret fields as substitution parameters into the Measurement ID and API Secret fields.
Additional Information
- Multiple tables may be necessary if it is determined that different lookup fields are needed to determine the proper GA4 property.
- Ensure that the values added to the lookup field column match the formatting seen in Invoca reporting, i.e. Domain = www.site.com, rather than https://www.site.com/.
