[William]

Great! You managed to handle pagination in the Azure Data Factory foreach loop using the new Google Analytics GA4 version 1 beta by using a unique solution. To start, you created three set variable activities: you set the offset to 0, the limit to 100,000, and the total rows received to 0. Then, you added an activity that continues until the total rows received and the row count (from the response) are the same. Inside this activity, you updated the three variables. This is indeed a clever and practical way to resolve the issue of not receiving the nextPageToken value in the API response in the new Google Analytics version. Your method could definitely help others facing the same challenge.

[William]

In GA4, you can send event data using the Measurement Protocol API and add different parameters to gather the desired data. However, GA4 does not need to send user agent, referral URL, and user IP data in the same way as Universal Analytics. This data is collected automatically. To track user interactions more granularly, you can create custom events and parameters. For example, you can send a ‘page_view’ event and add parameters to the event to include data like the page’s URL. It might be different from the way Universal Analytics operates, but GA4 is designed to provide a richer set of reports to describe your users’ behavior. Be aware that you might need to adjust your implementation or potentially use Google Tag Manager to gather the desired data. Make sure to refer to the GA4 documentation for details on using the Measurement Protocol API and setting up custom events and parameters.

[William]

One way of separating all the memberships in GA4 (Google Analytics 4) is by using custom dimensions to track each membership type. While setting up each subscription as a product would be a perfect way to arrange them ideally, GA4 doesn’t have this setup built in. However, you can employ custom dimensions to achieve similar results.

Custom dimensions will allow you to tag and categorize each purchase as a separate type of membership. When the purchase event is sent to GA4, you can add a custom parameter to differentiate between main memberships and bonus memberships. This will essentially let each membership have its own identity, distinct from the others.

To implement this, you’ll need to tweak the purchase event code to include the custom dimension of membership type. Each purchase should then also include the type of membership purchased. This data can then be included in your reports and analyses to determine separately the impact of each membership type.

Please be reminded that these adjustments should be made by a web development professional to ensure accuracy and compliance with Google terms and conditions.

[William]

Wow, that is quite a difference between those two numbers, huh? Doesn’t really seem right, even with GA4’s tendency to count more users. And you checked for any double GA4 codes so it’s not that. Hmm…

Let’s see, here’s a few things we can do to figure out what’s going on:

1. Take a look at your UA property. Make sure no weird filters are messing with the numbers.
2. Are you comparing the exact same periods for both? Worth double checking.
3. Check all the hostnames you’ve tracked during that time. Maybe GA4 is counting some that UA isn’t?
4. GA4 counts mobile app traffic which UA doesn’t, might that explain the difference?
5. Try checking per section of the site. Maybe GA4 is tracking some places UA isn’t?

After trying all of that, if we got no answers, we might be a bit stuck. It’s not like it’s easy to overcount users, it doesn’t really happen unless you’re trying to make it happen.

Our last resort might be to use the Adswerve’s datalayer debugger extension. This bad boy should allow you to see what’s firing on your pages. Keep in mind that GA4 events are batched, so you need to dive inside the event and double check it’s not counting twice with a different client id. It’s a bit of a long shot, but with numbers this skewed, who knows?