I’ve been implementing Server-side tracking for one of our clients, everything seems to be working FACPI, GA4 SS container and Google Ads Conversion tracking. However I cannot seem to send Enhanced Conversion data to my Server-side Google Ads conversion action.
I used the following guide Server side Conversion tracking in Google Ads for implementation. But I believe the video’ and information in this guide is not adequate. The video cuts short at the end where I believe we are supposed to test the Enhanced Conversions implementation and see the correct event_data + user_data for the purchase hit.
From what I’ve gathered I think the problem is as followed for my implementation:
[sGTM] = Web Google Tag Manager
[server] = Server-container
- We use the GA4 SS Configuration tag in the [sGTM] container to send user_data to the server-container.
- In the [server] container we use the Google Ads Conversion tag + Conversion Linker, with the ‘include user-provided data’ setting enbaled.
- Google Ads Conversion tag is currently being fired on the following trigger: Client = Data Client Event = purchase
a. Before I had this trigger on the normal GA4 SS purchase event. However I tried using the Data Client to
resolve this issue.
[sGTM] GA4 SS Configuration
[sGTM] Data Client
[server] Google Ads tag
[server] Pageview on order page containing user_data
[server] Purchase not containing user_data GA4 SS Ecommerce Events
Google Ads (Enhanced Conversions is enabled in this tag + the EULA is accepted in the account)
user_data is defined on the GA4 SS Configuration tag and not the GA4 SS Ecommerce Events tag. So user_data is available in the event_data for the pageview, but not for the purchase event.
However this is how every guide for Enhanced Conversions for Server-side explains how to implement it.
(In my case the only difference is that now I am using the Data Client instead of the GA4 Client, but I’ve tried the GA4 Client and had the same problem)
Fire the [server] Google Ads Conversion Tracking tag on the page_view containing the user_data, however because the purchase data is defined after, this is not possible without a workaround. I could store the user_data maybe and once the purchase event has fired append this user_data to the purchase data?
Could anyone possibly explain what the best solution would be to get Enhanced Conversions working for this implementation? If more information is required please ask and I will do my best to provide this information.