[Oliver]

This issue might be happening because ‘screen_name’ is not a default dimension in Google Analytics, so it won’t automatically be included within your reports. To utilize custom parameters like ‘screen_name’, you would need to set up a ‘Custom Definition’ or a ‘Custom Dimension’ within your Google Analytics admin settings. After setting this up, you should start seeing data for ‘screen_name’ in your events reports. Also, keep in mind that custom dimensions only start collecting data from the day they are created and won’t work retroactively.

[Oliver]

In the place of ‘page_url’, you need to pass the current page URL in the form of a string. Right now, what it seems like you’re doing is passing a string literal ‘page_url’ instead of the actual page URL. You could use ‘location.href’ to get the URL of the current page. It would look something like this: ‘page_url’ : location.href.

As for the ‘button_text’, this should be the text that the button users click on is displaying. If you’re placing ‘button_text’ as a string, it will only display as just that – ‘button_text’. However, you likely want it to reflect the actual text. So you need to configure it to grab that, like this: ‘button_text’ : document.getElementById(“button-id”).innerText, assuming you have a button with the id of “button-id”.

Therefore, your gtag should look something like this:

`
gtag(‘event’, ‘CTA Click’, {
‘page_url’ : location.href,
‘button_text’ : document.getElementById(“button-id”).innerText,
‘event_label’ : ‘CTA Clicks’
});
`
This should solve your issue. The ‘page_url’ will then contain the actual URL of the page where the event is happening, and ‘button_text’ will show the actual text that exists on the button. ‘event_label’ can remain as ‘CTA Clicks’. Be sure to replace “button-id” with your actual button’s ID. If the text isn’t changing, make sure that the ID correctly corresponds to the button that’s being clicked.

[Oliver]

Your issue might have different sources. This could be due to data thresholds or data sampling in Google Analytics 4 (GA4) causing data discrepancies between real-time and historical data. This feature of GA4 helps protect user privacy, but can cause changes or distortions in the reported data. It could also be the result of a delay in the processing of data into BigQuery. Sometimes, you might see data in the intraday table that hasn’t yet appeared in the daily table because BigQuery processes large data sequentially and intraday data sooner than the rest. A third potential cause could be a technical glitch in GA4 or BigQuery leading to data loss. They are complex systems and occasionally do experience such issues. In all cases, you should reach out to Google support to investigate the matter further.