[Addison]

This discrepancy might be arising due to differences in the timing of data availability between Google Analytics 4 (GA4) and BigQuery. In GA4, data usually shows up in reports within a few hours of it being collected, but sometimes it can take longer. However, with BigQuery, exported data is typically available in just a few minutes. Therefore, it’s possible that you’re seeing the excluded data in BigQuery before it’s had a chance to show up in your GA4 reports. Additionally, if the filters have been applied recently in GA4, it could take up to 24 hours for changes to affect the data in your reports. Hence, consider checking later to see if the excluded data displays correctly. Lastly, make sure that the same exact filters are being applied in both platforms for a fair comparison.

[Addison]

Sure, all this is saying is – See if you’ve got something like AdBlock working or if Firefox is set to block marketing tags. Because in these cases, even though GTM Preview shows that everything’s good to go, the browser might be stopping the data from actually heading out. Another thing to check out is if you have a filter set up in your GA account/property. This could stop the data even before GA has a chance to process it.

[Addison]

It’s not uncommon to see a difference between the numbers in BigQuery (BQ) and Google Analytics 4 (GA4) API reports. Actually, a 3% difference is relatively small.

This discrepancy can occur because GA4 reports are based on sampled and pre-aggregated data, rather than raw data. Conversely, your query in BQ is running on raw data.

If you need to cross-verify data between GA4 and BQ, I recommend working within the Explore section of GA4 and building out dashboards there. The preset GA4 reports don’t always give a detailed view of the data compared to what you might get from BQ, since they’re more catered towards those who may not be as versed in data analysis. So, no need to worry, you’re on the right track!

[Addison]

Certainly, mate. The basic idea is to push the event data into the data layer which GTM can access and then send it to GA4. To do this, you’d modify your “doThis” function to push your event data into the ‘dataLayer’ like so:

`javascript
function doThis() {
window.dataLayer = window.dataLayer || [];
window.dataLayer.push({
‘event’: ‘event_triggered’,
‘custom_param’: ‘custom_value’
});
}
`
Where ‘event_triggered’ is the name of the event that you want to track, and ‘custom_param’/’custom_value’ represents any additional data you want to track.

Next, in GTM, create a new User-Defined Event trigger with the event name matching ‘event_triggered’ from your code. Then, create a GA4 Event tag for your event, with the above trigger. The “event name” in the GA4 Event tag should read directly from the dataLayer as well.

To test if it’s working, go to the Preview Mode in GTM, trigger your custom event on your site, and then check if your GA4 Event tag fires in the GTM preview panel. Once confirmed, you should be able to view those events in your GA4 in real-time report as well as in the event reports.

[Addison]

Yo, in step 5 there’s a slight mix-up. Instead of userId, you should be using user_id. It’s a little quirk of GA4. Check out this doc for a rundown on how GA4 works with user IDs. Happy coding!

[Addison]

The error message you received indicates that the ‘google.rpc’ module was not found. This module is included in the ‘grpcio’ library. The version 1.51.1 of this library you are currently using might not have been installed correctly, thus causing the import error. I would recommend you to uninstall the ‘grpcio’ and ‘grpcio-tools’ libraries and then reinstall updated versions. Following this, repackage your AWS Lambda function and its dependencies. If this does not work, try adding the ‘googleapis-common-protos’ Python package to your AWS Lambda package as well, as the ‘google.rpc’ error might be related to protocol buffers, which are covered by this package.

[Addison]

It sounds like the issue you’re experiencing could be related to how Google Tag Manager (GTM) is interacting with the modal that your video lives in. Once the first video is played, GTM might not be recognizing the other videos as new components because they’re loaded dynamically within the same modal and, as a consequence, only the first video gets tracked. Try setting up ‘Observer Tags’ in GTM which is specifically designed to monitor changes in the elements of the page, like the loading of a new video in an existing modal. This tag can trigger whenever a new video gets loaded in the modal. Also, ensure that all your videos are appropriately tagged. Lastly, in your GA4 settings, make sure that ‘Enhanced measurement’ is turned ON and the specific video tracking feature is enabled under that setting. By trying this, the event should fire with the tag every time you click on a video, not just the first one.

[Addison]

It sounds like you’re having trouble with the custom dimensions not showing up in your reports in Google Analytics 4. For custom dimensions to work, you not only need to set them up in the GA4 interface, but you also need to make sure you’re sending the correct parameter values within your tracked events. From what you shared, it seems like you’re sending the ‘event_category’ and ‘event_label’ parameters correctly in your events.

However, in your report call, it looks like you’re asking for ‘customEvent:event_category’ and ‘customEvent:event_label’ instead. I think this might be the issue, as your events are not sending those exact parameters. Instead, try asking for ‘event_category’ and ‘event_label’ within your dimensions array and see if that makes any difference.

Additionally, keep in mind that there can be delays in reporting in GA4, so it could very well be that the custom dimensions have simply not had time to populate in your reports yet.

[Addison]

Yes, this can be accomplished through Google Analytics. For both Universal Analytics and GA4, Google provides a JavaScript code, known as the tracking code, which collects data about your site.

For Universal Analytics, the tracking code could be customized for specific events. However, instead of directly manipulating the code, custom events are typically created within the Google Analytics (GA) interface. You can set up new goals via the “Admin” section under “Goals” and then set the type as “Destination”. You would then specify the URLs of the pages which would count as an achievement of the goal.

In GA4, Google has moved towards an event-based model. The global site tag (gtag.js) that GA4 uses allows you to send event data to Google Analytics. Event tracking can be configured directly in the interface without requiring modification of the tracking code on your website. Both these scripts (Universal and GA4) should be placed in the footer of your website pages to track all necessary data for a session.

However, as you are trying to setup an event or a goal that includes viewing of multiple pages, it is recommended to make use of ‘Funnel Analysis’ in GA4 as it allows for a sequence of actions a user took, while goals in Universal Analytics work better for single action targets.

Please note that getting this setup right may require more than just a simple copy-paste of the tracking code. To fulfil your specific need, understanding the setup, configuration, and interpretation of these data collection tools is essential. It’s advisable to consult with a Google Analytics certified professional or a similar expert for proper setup and utilization of these tools.

[Addison]

Your problem seems to be related to an SSL Certificate not being recognized by Firebase/Google Analytics. One of the primary causes of SSLHandshakeException is that the SSL certificate presented by the server is not trusted.

If you are using a self-signed certificate or a certificate issued by an internal certificate authority (CA), make sure it’s imported and properly set up in your Android key store. If that doesn’t work, consider using an SSL certificate from a well-known CA to ensure Firebase recognises and trusts the server’s certificate during the SSL handshake.

Additionally, the problem may also be due to restrictions caused by VPN. Google uses your device’s IP to deliver the analytics data. If you are using a VPN, it can interfere with, or block, traffic between your app and Firebase.

Lastly, it may be beneficial to try running your application on a real device instead of a simulator. Certain network-related operations can return different results on real devices and emulators.

Without further details and specifics about your project’s setup and settings, it’s difficult to provide a more precise solution. However, I hope this general advice helps you understand possible steps to resolve the issue.

[Addison]

Yes, you can get the GA4 Measurement ID by inspecting the website’s source code similar to how you would with the Google Universal Analytics Tracking ID. Open the source code of the website (CTRL+U in most browsers), then search (CTRL+F) for “G-“. The GA4 Measurement ID usually starts with “G-” followed by a series of numbers and letters. However, this may not work if the website has chosen to hide the ID or is loading it dynamically. You could also use Google Tag Assistant, a Chrome plugin, to identify Google tags, including GA4 Measurement ID, used on the webpage.