ChannelMix Multi-Touch Attribution - GA4 Requirements
Follow these steps to send ChannelMix Timestamp and ChannelMix Client ID with Page Views and Key Events, essential for ChannelMix Attribution reporting. Detailed instructions are provided for implementation through Google Tag Manager (GTM), which is the recommended approach. For users utilizing other tracking systems, generalized instructions are also included. Completing these steps will enable these values to be accessible via the GA4 API.
Requirements
- ChannelMix Client ID: Send a unique ChannelMix Client ID as a User Property with all Page Views* and ChannelMix Conversions.**
- ChannelMix Timestamp: Send a ChannelMix Timestamp as an Event Parameter with all Page Views* and ChannelMix Conversions.**
*Page view data may be sent through a dedicated tag (demonstrated below), or page views may be measured through GA4 Enhanced Measurement. In the latter case, add the required parameters to the Google Tag.
**ChannelMix Conversions may include either purchase or channelmix_conversion conversion events. In some cases, it may be possible to utilize a custom event name.
Google Tag Manager Steps
- Import GTM Dependencies: Import the provided GTM dependencies using the following export file: GTM Export - ChannelMix Timestamp & Client ID.json.
-
Add Variables to Tags:
- Add the ChannelMix Timestamp Variable to all Page View and Conversion Event Tags as an Event Parameter named "channelmix_timestamp".
- Add the ChannelMix Client ID Variable to the Page View and Conversion Event Tags as a User Property named "channelmix_client_id".
-
Define Custom Dimensions: In the GA4 Admin section, define the following Custom Dimensions:
- "ChannelMix Timestamp" as an Event-scoped dimension.
- "ChannelMix Client ID" as a User-scoped dimension.
-
Validation: Use GA4 DebugView to validate the implementation:
- Ensure that the ChannelMix Timestamp is received by GA4 as an Event Parameter on all page view and conversion events.
- Confirm that the ChannelMix Client ID is received by GA4 as a User Property on all page view and conversion events.
Google Tag Manager Screenshots
1. Import the Dependencies: Begin by importing the necessary dependencies into your GTM workspace.
GTM Container Import
2. Add Event Parameters to Tags: Ensure that the required variable values are sent with the relevant Event Tags (e.g., "GA4 Page View"). These values should be included in any tag that sends page view or conversion event data to GA4, such as the GA4 Google Tag.
- channelmix_timestamp: Sent as an Event Parameter.
- channelmix_client_id: Sent as a User Property.
GTM Page View Tag
3. Define Custom Dimensions: Define the following in the GA4 Admin section:
- "ChannelMix Timestamp" as an Event-scoped dimension.
- "ChannelMix Client ID" as a User-scoped dimension.
4. Validate Using Tag Assistant and GA4 DebugView:
- Validate that the ChannelMix Timestamp is being received as an Event Parameter on the page view and conversion events.
- Validate that the ChannelMix Client ID is being received as a User Property on page view and conversion .
GA4 DebugView
GA4 Debug View
5. Deploy to Production: Once validation is complete, submit all changes to the Production Container.
That concludes the implementation 🎉
Click here if you do not use GTM
If you're not using Google Tag Manager but still sending data to GA4, follow these steps:
- Generate ChannelMix Timestamp: Use the following function to dynamically generate the ChannelMix Timestamp, in Unix Epoch format, each time it is sent to GA4:
function() {
return ''+(+new Date());
}
-
Send Required Parameters:
- For all
page_view
andchannelmix_conversion
events sent to GA4, include the ChannelMix Timestamp as an Event Parameter named "channelmix_timestamp." - Send a unique User ID as a User Property named "channelmix_client_id" with all
page_view
andchannelmix_conversion
events.
- For all
-
Define Custom Dimensions in GA4: In the GA4 Admin section, define:
- "ChannelMix Timestamp" as an Event-scoped dimension.
- "ChannelMix Client ID" as a User-scoped dimension.
-
Custom Event Handling: If you're using a GA4 Custom event for conversions, ensure the required parameters are included with the custom event. For example, if your conversion event is based on the
page_view
event with a page path of "/confirm," include the required parameters with allpage_view
events.