Re: iBQML implementation, potential interference with domain tracking
Taige Eoff
Taige,Hope you're doing well and gearing up for a relaxing holiday season.I wanted to reach out related to a potential issue with our iBQML implementation across a number of the websites we're now testing. A few months ago, for our website www.kapre.com we identified a drastic increase in "(not set)" domain traffic (screenshot below). When we reached out to Google Ad Support (response below) they responded with the belief that the iBQML code may be interfering with domain, and page location parameters not being captured by GA4. I wanted to bring this to your attention in the event this is a known bug, or how we can escalate this for further review. Please let us know if there's any additional detail that would be helpful, or if it is best to find some time to connect and discuss.Best,TimDomain report for Kaptest (another website with iBQML implementation also experiencing this issue):Begin forwarded Google ads-support response:---------- Forwarded message ---------
From: <ads-s...@google.com>
Date: Tue, Dec 10, 2024 at 7:11 PM
Subject: Re: [8-1113000037275] Follow up to your email
To: <sarah....@kaplan.edu>
CC: <sarah....@kaplan.edu>, <adriana....@kaplan.edu>Hi Sarah,
Thank you for your continued patience and understanding while we collaborate with our wider team.
Our team has investigated the issue you reported regarding the (not set) reporting under the Hostname dimension and the blank entries for the Page referrer and Page location dimensions in the GA4 exploration report. We have determined that this issue is not a product defect, but rather stems from the implementation, specifically related to Instant BQML. Please refer to our explanation below.
Troubleshooting.
- Created a test exploration report, and found that maximum of these not set hostname and blank page dimensions are from the events: add_to_cart_propensity_iBQML & ibqml_kapre_purch_prop_iBQM for the reported date range starting from 1st Sept till date (9 Dec). Report link for your reference.
- We tried to trigger these events using the tag assistant by ghosting into the GTM GTM-W6WR56Z, but could not reproduce the exact steps made on the website (web stream = https://www.kapre.com/) which would lead us to view the parameters being passed.
- We could also see a few custom dimensions were created around the same date (first week of Sept 24) which strongly leads us to believe that this issue is related to your implementation of BQML. Report link for your reference.
- If we use one of these Custom Dimensions at the exploration report, we could see that they are populating values (please refer to the explorations report shared earlier) which confirms that Instant BQML is being used and the models are generating the predictions.
We recommend reviewing the associated tags, triggers, and variables that trigger these events. We believe the timing of these events is the primary reason why the hostname, page location/referrer parameters are not being captured and sent correctly to GA4.
There could also be a custom JavaScript code involved while implementing the Instant BQML which could be interfering with page_location/page_referrer parameters being captured, processed & sent.
So to conclude, this issue doesn't seem to be product related but in a way that you have implemented iBQML to capture and send values for the pages which capture the aforementioned events. I hope you find the above information helpful, please feel free to write back if you have any follow up questions.
Regards,
Tarun.gTech Customer ExperienceNB: If you need to reference this support ticket in the future, the ID number is 8-1113000037275This email may be confidential or privileged. If you received this communication by mistake, please don't forward it to anyone else, please erase all copies and attachments, and please let me know that it went to the wrong person. The above terms reflect a potential business arrangement, are provided solely as a basis for further discussion, and are not intended to be and do not constitute a legally binding obligation. No legally binding obligations will be created, implied, or inferred until an agreement in final form is executed in writing by all parties involved.1600 Amphitheatre Parkway
Mountain View, CA 94043, USA--
Tim Pamer
Taige Eoff
Instant BQML and Vertex Users
Hi Tim,
Thanks for reaching out and for the detailed information about the increase in "(not set)" domain traffic on your Kapre website.
The issue you're encountering is a known technical issue with GA4's session attribution when processing Measurement Protocol events. The good news is that our engineering team has already fixed this issue, and the changes are scheduled to be rolled out to production in January 2025.
So you have a couple of options:
-
Wait for the fix: The issue should resolve itself automatically in the next few weeks once the changes are deployed to GA4.
-
Remove reporting influence: If you prefer a more immediate solution, you can eliminate the impact of iBQML on your GA4 reporting:
- Upgrade to v1.5: Ensure you're using Instant BQML version 1.5. This version decouples the events and user property measurement protocol payloads.
- Remove "Events to GA4" job: In your prediction pipeline, remove the "Events to GA4" job. This will prevent iBQML from sending events that might affect your session attribution.
- Modify "Percentiles to GA4" job: In the "Percentiles to GA4" job, add a Job Dependency of "Define User Property" set to "success." This ensures the Prediction pipeline runs correctly after removing the "Events to GA4" job.
Important: This option is suitable if you're primarily using iBQML for audience segmentation and not for value-based bidding (VBB). Your audiences will continue to grow as the "Percentiles to GA4" job, which sets user property values, will remain active.
We apologize for any inconvenience this issue may have caused. Please let me know if you have any further questions or would like assistance with upgrading to v1.5 or modifying your pipeline.
Wishing you a happy and relaxing holiday season!
Best regards.
David Myers
--
You received this message because you are subscribed to the Google Groups "Instant BQML and Vertex Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to instant-bqml-verte...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/instant-bqml-vertex-users/2fbd4033-a38c-4ba9-b997-df728d49738dn%40googlegroups.com.
David Myers
+Akshit Arora +Malcolm Bonner (Data Transformation Lead and Analytical Lead respectively for Kaplan) for visability.
--
You received this message because you are subscribed to the Google Groups "Instant BQML and Vertex Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to instant-bqml-verte...@googlegroups.com.
Tim Pamer
David Myers
Hi Tim,
Thanks for reaching out and for the detailed information about the increase in "(not set)" domain traffic on your Kapre website.
The issue you're encountering is a known technical issue with GA4's session attribution when processing Measurement Protocol events. The good news is that our engineering team has already fixed this issue, and the changes are scheduled to be rolled out to production in January 2025.
Wait for the fix: The issue should resolve itself automatically in the next few weeks once the changes are deployed to GA4.So you have a couple of options:
Remove reporting influence: If you prefer a more immediate solution, you can eliminate the impact of iBQML on your GA4 reporting:
- Upgrade to v1.5: Ensure you're using Instant BQML version 1.5. This version decouples the events and user property measurement protocol payloads.
- Remove "Events to GA4" job: In your prediction pipeline, remove the "Events to GA4" job. This will prevent iBQML from sending events that might affect your session attribution.
- Modify "Percentiles to GA4" job: In the "Percentiles to GA4" job, add a Job Dependency of "Define User Property" set to "success." This ensures the Prediction pipeline runs correctly after removing the "Events to GA4" job.
Important: This option is suitable if you're primarily using iBQML for audience segmentation and not for value-based bidding (VBB). Your audiences will continue to grow as the "Percentiles to GA4" job, which sets user property values, will remain active.
We apologize for any inconvenience this issue may have caused. Please let me know if you have any further questions or would like assistance with upgrading to v1.5 or modifying your pipeline.
Wishing you a happy and relaxing holiday season!
Best regards.
Cheers,
