Status Update
Comments
ke...@google.com <ke...@google.com> #2
Hello,
Please check your inbox. I've sent you a separate email to request for more details. Let's continue our discussion on that thread moving forward.
Regards,
Kevin Soriano, Google Analytics API Team
wi...@motorway.co.uk <wi...@motorway.co.uk> #3
ke...@google.com <ke...@google.com> #4
Hello,
Please check your inbox as well. I've sent you a separate email to request for more details. Let's continue our discussion on that thread moving forward.
Regards,
Kevin Soriano, Google Analytics API Team
lo...@avantgarde-pmc.de <lo...@avantgarde-pmc.de> #5
ke...@google.com <ke...@google.com> #6
Hello,
Thank you for the additional information.
Based on this
If you have successfully met those conditions, but your data was still incorrectly attributed to organic traffic, I suggest you reach out to our
Regards,
Kevin Soriano, Google Analytics API team
wi...@motorway.co.uk <wi...@motorway.co.uk> #7
I have opened a ticket with the product support team. They have said because it is BigQuery export related it is not within their remit.
I also did not receive a direct email from you on the 9th August.
Could you please advise who can help with this. It seems as if no one wants to take responsibility, I'm sure that's not the case.
Thank you,
Will
ke...@google.com <ke...@google.com> #8
Hi Will,
Since you didn't receive my email, can you please provide a sample payload and any other details that you may have such as UI screenshots where you've observed the issue and then send it to our team via the
Regards,
Kevin Soriano, Google Analytics API team
ma...@edilportale.com <ma...@edilportale.com> #9
ke...@google.com <ke...@google.com> #10
Hello,
I suggest you reach out to our
If you're not a Google Analytics 360 user, please make sure that you are using the email address for your standard Google Analytics account and that the email address has a Google Ads account before reaching out to the product support team, since there is a required field for your customer ID.
Regards,
Kevin Soriano, Google Analytics API team
[Deleted User] <[Deleted User]> #11
ke...@google.com <ke...@google.com> #12
Hi Sophie,
I'm afraid I'm not aware if the users were able to resolve the issue with the product support team. I suggest you reach out to their
If you're not a Google Analytics 360 user, please make sure that you are using the email address for your standard Google Analytics account and that the email address has a Google Ads account before reaching out to the product support team, since there is a required field for your customer ID.
Regards,
Kevin Soriano, Google Analytics API team
[Deleted User] <[Deleted User]> #13
Thanks for the article about the differences between UA and GA4 - I'm already pretty well versed in this, and I don't believe that article provides any relevant info on the issue at hand here.
Can I try articulating the issue in a slightly different way and see if anyone can spare me months of getting nowhere with GA support?
When auto-tagging is enabled in Google Ads and linked to GA4, when traffic arrives at our website with a GCLID query parameter within the URL, the following happens...
In the GA4 UI, this session gets reported as follows (both at the session-level and first-user level)...
* default channel grouping = 'Paid Search'
* source = 'google'
* medium = 'cpc'
... This is expected behaviour and all OK
But in the GA4 BigQuery export, the auto-tagging doesn't work at all, and the presence of the GCLID query parameter does nothing to attribute the traffic to the Paid Search channel and the google / cpc combination of Source / Medium
* default channel grouping - this doesn't yet flow through in the GA4 BigQuery export which is a painful gap in the current product offering. When does the GA4 product roadmap plan to surface the default channel grouping in the GA4 BigQuery export?
Then it gets really weird because this traffic has a mixture of Source / Medium (when looking at the source and medium event parameters)
* Some of this traffic has Source = 'google' and Medium = 'organic' (This is the exact problem raised in the description of this issue)
* Some of this traffic has NULL values for Source and Medium
If using the GA4 BigQuery export, does this mean that we need to take a backwards step and turn off auto-tagging in the Google Ad platforms, and go back to manual tagging and using the utm_source, utm_medium and utm_campaign parameters?
Thanks,
Sophie
[Deleted User] <[Deleted User]> #14
ke...@google.com <ke...@google.com> #15
Hi Sophie,
Thank you for your response.
I'm afraid that I'm unable to comment on your concern. Please note that our team doesn't have visibility on Google Ads and Google BigQuery. This channel is intended for Google Analytics API specific issues only.
I understand that you might have had issues with GA support before, but since this is more on the product level, their team is better equipped to address the issue. Having said that, I hope that you get a response from their team soon regarding your concern.
Regards,
Kevin Soriano, Google Analytics API team
Description
Summary:
We have been using UA and BigQuery to analyze traffic data, and are now making the switch to GA4. However we are encountering an issue where events are attributed to organic traffic, event though they actually paid search.
To ensure it is not a BigQuery issue, we have collected events in the debug mode which produces the same results. There is an example of an incorrect event included in the attachments. (I have blacked out some customer specific data). That image is taken directly from the GA debug screen.
What is interesting is that the GA web-interface appears to correctly attribute these clicks to google-ads campaigns, though the raw event data would suggest otherwise.
Expected Behaviour
All generated events that have a GCLID parameter set should be attributed to "Google / Paid search".
Steps to Reproduce:
The event will have a gclid set in the page_url and also in the event_params but the event will still be attributed to organic traffic.
Any idea how this could happen?