Application Launcher

Acquia CDP

Standard - Web Analytics or Google Analytics 4 (GA4) Connector

Acquia CDP

Standard - Web Analytics or Google Analytics 4 (GA4) Connector

What data does Customer Data Platform (CDP) pull from Google Analytics 4?

Google Analytics API-based connectors provide access to the Last-touch Revenue-Attribution feed. For information about the logic used by Google Analytics for revenue attribution, see this document.

To obtain the report, CDP pulls the following data from Google Analytics:

Dimensions

Date: The date of the event.
Source: The source of referrals to your property.
When using manual campaign tracking, this is the value of the utm_source campaign tracking parameter. When using AdWords auto-tagging, the value is google. Otherwise, the domain of the source refers to the visitor to your property. For example, document.referrer. The value may also contain a port address. If the visitor arrived without a referrer, the value is (direct). (source: Google Analytics).
Medium: The type of referrals to your property.
When using manual campaign tracking, this is the value of the utm_medium campaign tracking parameter. When using AdWords auto-tagging, the value i ppc. If the user comes from a search engine detected by Google Analytics, the value is organic. If the referrer is not a search engine, the value is referral. If the visitor came directly to the property, and is empty, the value is (none). ().

What data does Customer Data Platform (CDP) pull from Google Analytics 4?

To obtain the report, CDP pulls the following data from Google Analytics:

Dimensions

Date: The date of the event.
Source: The source of referrals to your property.
When using manual campaign tracking, this is the value of the utm_source campaign tracking parameter. When using AdWords auto-tagging, the value is google. Otherwise, the domain of the source refers to the visitor to your property. For example, document.referrer. The value may also contain a port address. If the visitor arrived without a referrer, the value is (direct). (source: Google Analytics).
Medium: The type of referrals to your property.
When using manual campaign tracking, this is the value of the utm_medium campaign tracking parameter. When using AdWords auto-tagging, the value i ppc. If the user comes from a search engine detected by Google Analytics, the value is organic. If the referrer is not a search engine, the value is referral. If the visitor came directly to the property, and is empty, the value is (none). ().

What data does Customer Data Platform (CDP) pull from Google Analytics 4?

To obtain the report, CDP pulls the following data from Google Analytics:

Dimensions

Date: The date of the event.
Source: The source of referrals to your property.
When using manual campaign tracking, this is the value of the utm_source campaign tracking parameter. When using AdWords auto-tagging, the value is google. Otherwise, the domain of the source refers to the visitor to your property. For example, document.referrer. The value may also contain a port address. If the visitor arrived without a referrer, the value is (direct). (source: Google Analytics).
Medium: The type of referrals to your property.
When using manual campaign tracking, this is the value of the utm_medium campaign tracking parameter. When using AdWords auto-tagging, the value i ppc. If the user comes from a search engine detected by Google Analytics, the value is organic. If the referrer is not a search engine, the value is referral. If the visitor came directly to the property, and document.referrer is empty, the value is (none). (source: Google Analytics).
Campaign: When using manual campaign tracking, this is the value of the utm_campaign campaign tracking parameter.
When using AdWords auto-tagging, the name(s) of the online ad campaign that you use for your property. Otherwise, the value (not set) is used. (source: Google Analytics).
AdWords AdGroup: The name of your AdWords ad group.
TransactionId: The transaction ID for the shopping cart purchase as supplied by your e-commerce tracking method. (source: Google Analytics).

Metrics

Purchase Revenue : This is not leveraged in any parts of the CDP applications. CDP relies on the more accurate revenue received from either your daily data feeds or CDP’s WebTag. CDP pulls this information to generate a report that helps CDP to extract the rest of the information from the Google Analytics API.

Mapping

The following tables lists the mapping of Google Analytics API data with the corresponding CDP entity. The Source column represents the Google Analytics API fields. The Destination column represents the fields in CDP entities. These tables represent the data coming to CDP from Google Analytics API.

Destination entity: promotion

Source	Destination
sessionCampaignName	SourcePromotionNumber
sessionCampaignName	Name

Destination entity: promotioncampaignxref

Source	Destination
sessionCampaignName	SourcePromotionNumber
sessionCampaignName	SourceCampaignNumber

Destination entity: campaign

Source	Destination
sessionCampaignName	SourceCampaignNumber
sessionCampaignName	Name

Destination entity: dispatch

Source	Destination
sessionCampaignName	SourceCampaignNumber
sessionCampaignName	SourceDispatchNumber:campaign
sessionMedium	SourceDispatchNumber:medium
sessionSource	SourceDispatchNumber:source
sessionCampaignName	Name
sessionMedium	Type
sessionSource	SubType

Destination entity: message

Source	Destination
sessionCampaignName	SourceMessageNumber:campaign
sessionGoogleAdsAdGroupName	SourceMessageNumber:adGroup
sessionMedium	SourceMessageNumber:medium
sessionSource	SourceMessageNumber:source
sessionCampaignName	SourceDispatchNumber:campaign
sessionMedium	SourceDispatchNumber:medium
sessionSource	SourceDispatchNumber:source
sessionCampaignName	Name
sessionGoogleAdsAdGroupName	Content

Destination entity: transactionmessagexref

Source	Destination
sessionCampaignName	SourceMessageNumber:campaign
sessionGoogleAdsAdGroupName	SourceMessageNumber:adGroup
sessionMedium	SourceMessageNumber:medium
sessionSource	SourceMessageNumber:source
type	Type
transactionId	SourceTransactionNumber

Limitations

Google Analytics API does not provide individual sources for all customers, and it would not be very accurate if they did, given that it would be solely based on cookie-level information.
The CDP Google Analytics connector uses the TransactionID to directly tie your campaigns to your customers’ transactions, allowing Acquia to have better accuracy through deduping in case some customers placed transactions under different cookies. For example, transactions placed through mobile vs desktop websites.
Google Analytics TransactionID must match the OrderNumber that you are sending in the CDP Standard Data Feed for this integration to work correctly.
The traffic source for visitors who did not place an order is not available through the Google Analytics API. Additionally, CDP cannot do re-attribution between multiple sources for an order. CDP can only pull what Google Analytics says is the last touch for an order.
From the moment CDP starts the integration, the connector pulls the previous 14 months of transactions by default. If you need CDP to start a project to pull more data, contact your Customer Value Manager. However, remember that the more data CDP pulls, the more time it takes to refresh the application the first time when the integration is turned on.
The data available through the Google Analytics API typically refreshes every 12 hours for regular-sized websites. Sometimes, it can take more than 24 hours depending on the number of events processed. Therefore, the data available for the Google Analytics report usually lags the actual events by 12-14 hours. For information about Google Analytics 4 Data freshness and Service Level Agreement constraints, see this article.

source: Google Analytics

Campaign: When using manual campaign tracking, this is the value of the utm_campaign campaign tracking parameter.

When using AdWords auto-tagging, the name(s) of the online ad campaign that you use for your property. Otherwise, the value (not set) is used. (source: Google Analytics).

AdWords AdGroup: The name of your AdWords ad group.

TransactionId: The transaction ID for the shopping cart purchase as supplied by your e-commerce tracking method. (source: Google Analytics).

Purchase Revenue : This is not leveraged in any parts of the CDP applications. CDP relies on the more accurate revenue received from either your daily data feeds or CDP’s WebTag. CDP pulls this information to generate a report that helps CDP to extract the rest of the information from the Google Analytics API.

Destination entity: promotion

Source	Destination
sessionCampaignName	SourcePromotionNumber
sessionCampaignName	Name

Destination entity: promotioncampaignxref

Source	Destination
sessionCampaignName	SourcePromotionNumber
sessionCampaignName	SourceCampaignNumber

Destination entity: campaign

Source	Destination
sessionCampaignName	SourceCampaignNumber
sessionCampaignName	Name

Destination entity: dispatch

Source	Destination
sessionCampaignName	SourceCampaignNumber
sessionCampaignName	SourceDispatchNumber:campaign
sessionMedium	SourceDispatchNumber:medium
sessionSource	SourceDispatchNumber:source
sessionCampaignName	Name
sessionMedium	Type
sessionSource	SubType

Destination entity: message

Source	Destination
sessionCampaignName	SourceMessageNumber:campaign
sessionGoogleAdsAdGroupName	SourceMessageNumber:adGroup
sessionMedium	SourceMessageNumber:medium
sessionSource	SourceMessageNumber:source
sessionCampaignName	SourceDispatchNumber:campaign
sessionMedium	SourceDispatchNumber:medium
sessionSource	SourceDispatchNumber:source
sessionCampaignName	Name
sessionGoogleAdsAdGroupName	Content

Destination entity: transactionmessagexref

Source	Destination
sessionCampaignName	SourceMessageNumber:campaign
sessionGoogleAdsAdGroupName	SourceMessageNumber:adGroup
sessionMedium	SourceMessageNumber:medium
sessionSource	SourceMessageNumber:source
type	Type
transactionId	SourceTransactionNumber

Google Analytics API does not provide individual sources for all customers, and it would not be very accurate if they did, given that it would be solely based on cookie-level information.
The CDP Google Analytics connector uses the TransactionID to directly tie your campaigns to your customers’ transactions, allowing Acquia to have better accuracy through deduping in case some customers placed transactions under different cookies. For example, transactions placed through mobile vs desktop websites.
Google Analytics TransactionID must match the OrderNumber that you are sending in the CDP Standard Data Feed for this integration to work correctly.
The traffic source for visitors who did not place an order is not available through the Google Analytics API. Additionally, CDP cannot do re-attribution between multiple sources for an order. CDP can only pull what Google Analytics says is the last touch for an order.
From the moment CDP starts the integration, the connector pulls the previous 14 months of transactions by default. If you need CDP to start a project to pull more data, contact your Customer Value Manager. However, remember that the more data CDP pulls, the more time it takes to refresh the application the first time when the integration is turned on.
The data available through the Google Analytics API typically refreshes every 12 hours for regular-sized websites. Sometimes, it can take more than 24 hours depending on the number of events processed. Therefore, the data available for the Google Analytics report usually lags the actual events by 12-14 hours. For information about Google Analytics 4 Data freshness and Service Level Agreement constraints, see this article.

Did not find what you were looking for?

If this content did not answer your questions, try searching or contacting our support team for further assistance.

Did not find what you were looking for?

If this content did not answer your questions, try searching or contacting our support team for further assistance.