Once you have published the tag and there is an active Enhanced signals configuration, it’s time to validate that the events are coming through and being processed as expected.
Regularly checking the output is a good way to ensure that the values reaching the destination platforms are as expected.
In addition to validation through the Enhanced signals dashboard, you can perform manual data validation for each specific target:
Data validation for Google Analytics 4: GTAG and Google Analytics 4: Firebase targets
Data validation for Google Analytics 4: GTAG and Google Analytics 4: Firebase targets
There are several methods to validate the data output:
If you are using a separate Google Analytics 4 property:
Ensure that you use the device ID as the reporting identity in both the Google Analytics 4 property created for Enhanced Signals and the regular Google Analytics 4 property you are comparing with.
Compare basic metrics such as pageviews, sessions, users, transactions, and revenue/profit.
Compare the attribution between the properties.
Investigate the item match rate using the Enhanced Signals quality metrics dashboard.
Examine values affected by the transformations in place. For example:
Is the total profit the expected value?
Is profit per transaction the expected value?
Is profit per SKU correct? Investigate using the Product cost list and Margin fallback .csv files.
Is the margin fallback applied correctly?
Is the Event lookup values as expected?
Is the Item lookup values as expected?
And so on.
Also, investigate the data using the reporting identity that will be used later on later on.
If using the regular Google Analytics 4 property and Data Stream with the event name 'precis_ecomm':
Compare the attribution between the regular 'purchase' event and the 'precis_ecomm' event.
Investigate the Item match rate using the Enhanced Signals quality metrics dashboard.
Examine values affected by the transformations in place. For example:
Is the total profit the expected value?
Is profit per transaction the expected value?
Are the event lookup values as expected?
And so on.
Data validation for Google Tag Manager: Server-side target
Data validation for Google Tag Manager: Server-side target
To validate the data flowing through your Server-side Google Tag Manager (ssGTM) container, use your preferred method of debugging events, just as you would with any other implementation in ssGTM.
If you don’t have a debugging setup, we recommend checking out this article on debugging Server-side GTM.
Data validation for Google Ads: Click conversion target
Data validation for Google Ads: Click conversion target
It takes about three hours for the conversion statistics sent by Enhanced signals to appear in your Google Ads account. When they do, they will show up in your 'Conversions' columns.
We suggest segmenting the 'Conversions' column by 'Conversion action name' so you can see the Conversion action set up for Enhanced signals.
To validate whether your setup is working, use the 'All conv. (by conv. time)' column. Unlike the other conversion columns, this column reports total conversions by the date of the conversion because your upload file records a conversion time.
Keep in mind that the longer the delay between your clicks and your conversions (including conversions sent by Enhanced signals), the longer you will have to wait to view the most complete conversion metrics.
Data validation for Facebook: Conversion API target
Data validation for Facebook: Conversion API target
The conversions sent from Enhanced signals will land in the Events manager. Just as any other implementation of tracking events in Meta, you can use the tools there to validate the events sent through Enhanced signals.
It takes a bit for Meta to process the events, but you should be able to verify them within 20 minutes after they were sent.