[Ella]

Hmm, it sounds like you’re experiencing a discrepancy between API values and the Explore Tab for User Engagement when paired with Medium. Without all details, it’s challenging to pinpoint an exact cause, but it might be a unique issue with how the API handles these specific dimensions. If everything else, including dates, conditions, and other dimensions, checks out perfectly fine, then it might be a good idea to reach out to Google support for assistance.

[Ella]

It is possible that the custom dimension data has not been fully processed yet. New or updated Google Analytics custom dimensions can take up to 24 hours to become effective, so you may need to wait for this processing period to pass. Moreover, ensure that you have set up and are using the custom dimension correctly. The name in the API request should match exactly with the one you specified during the custom dimension setup in Google Analytics. If you are still not seeing any data after waiting, it’s possible that your custom dimension isn’t capturing any data, or there might be an error in your setup or your API request. Double-check your approach and if everything seems correct, consider reaching out to Google Analytics support for further assistance.

[Ella]

Hi Will,
It seems like the issue has somewhat resolved itself over time. The discrepancy has reduced to a lower number that I think is reasonable. So, I’ve decided to just accept it and move on. These things happen sometimes. Cheers!

[Ella]

Absolutely, I’d love to help you with this. So, there is a solution. What you need to do is take advantage of the BigQuery export feature provided by Firebase. Once you link your Firebase app to BigQuery, you will have access to all your raw analytics data. Specific parameters, like the ‘message_id’ parameter you mentioned, will be readily available there. So that’s it! You’ll be able to get counts of ‘notification_open’ events per message ID without a problem. Isn’t that great?

[Ella]

Sure, happy to help explain the next steps! Good news is that you’re already halfway there. You successfully created an account using g4 analytics API and got your accountTicketId, which is great work!

So, what are you supposed to do with that accountTicketId, you might ask? Well, you should include this id in a special Terms of Service URL that would look like so: https://analytics.google.com/analytics/web/?provisioningSignup=false#/termsofservice/YOUR_ACCOUNT_TICKET_ID.

The cool part comes next. To finish the creation of your Google Analytics account, you or whoever will be using it just needs to visit this formulated URL, go through the Terms of Service agreement, and accept it. Once the TOS is accepted, voila! Your Google Analytics account creation will be complete. Hope this helps!

[Ella]

Hey there! It’s definitely interesting to hear about the issue you’re facing with the GA4 debugger and the drop in pageviews. One thing you might want to consider is that GA4 events can sometimes be batched together, meaning they wait a bit to be sent out, expecting more events to be included in the same packet.

If you’re still noticing an inconsistency with the pageview tag, I’d suggest taking a closer look with the GTM preview debugger. You can specifically check for cases where the tag should have fired and delve into the tag itself to identify any potential trigger issues. I really hope this offers you a bit more insight into what may be causing your problem!