[Leo]

Unfortunately, historical data prior to connecting Google Analytics 4 (GA4) to BigQuery is not automatically available. BigQuery only starts collecting data from the point you set up the connection between both platforms. This means any historical data that existed before the connection was established will not be mirrored automatically in BigQuery. Unfortunately, as of now, Google does not provide an option to migrate or backfill historical data from GA4 to BigQuery. In order to have a more comprehensive set of historical data in BigQuery moving forward, you’ll want to ensure that all data generating sources are properly hooked up to GA4, so as to have them streamed to BigQuery in real-time.

[Leo]

In Google Analytics 4, the virtual pageviews are tracked as events instead of standard pageviews. When you fire a tag for virtual pageview in GA4, it will appear under the “Events” section instead of “Pages”. To find the virtual pageview under the “Events”, navigate to “Reports” > “Engagement” > “Events”. It should be listed there as an event. If you wish to use it in a funnel, you need to create an event first with it and then build the funnel. GA4 is significantly different from Universal Analytics where virtual pageviews could be found in the “Behavior” > “Site Content” > “All Pages” section. Remember that debugging can also be done by using the Real-Time reports or DebugView for more immediate feedback.

[Leo]

Oh, I feel you! I hit the same issue a few days ago with those stubborn incompatibilities in Google Analytics. The solution is actually simpler than it looks.

The tricky part here is that dimensions that bring in the query string – like our friend pagePathPlusQueryString – play nicely only with a select group of other dimensions and metrics.

Turns out pagePathPlusQueryString is like a prima donna page level dimension, kinda different from the regular event parameters we know and love.

So, what’s the workaround? Get the queryString into an event parameter, and it should all work smoothly.

Also, if you’re dealing with custom event parameters, dimensions or metrics, just remember you need to slightly change the way you’re referencing them. Instead of the literal names, use customEvent:{parameter_name}. Treat it like any other standard parameter and it should respond nicely.

Hope this helps! Don’t let the Analytics APIs bully you; you got this!

[Leo]

Hey there, sounds like a puzzling situation but no worries, we’ve got this figured out. Technically, these bits of data like client ID, affinity ID, and customer ID can be picked up through something like gtag.js, a Javascript tagging framework. It’s a handy little tool that can send event data directly to Google Analytics 4 (GA4), and it doesn’t need Google Tag Manager (GTM) to do so.

Also, it’s worth noting that other tag management systems (TMSes) can also send GA events without a hitch, even if GTM is being used simultaneously. And of course, it’s totally possible to submit any type of data to any endpoint through pure Javascript.

In short, even without GTM, there are several ways this type of data could be sent through to GA4. That could explain why you’re seeing that data in the pageviews of GA4. Interesting, right?