[Jackson]

It seems like you’re encountering a fairly common issue when dealing with custom dimensions or metrics in platforms like Google Analytics 4. When you create a new custom dimension or metric, the data collection for that specific dimension/metric starts from the point it was created, it won’t retroactively pull data from before that creation date.

In your case, it appears that even though your starting date for both evaluations started from May 1st, the new dimension (created on the 8th) only displayed data from its creation date forwards.

That’s why your second Event Count descriptor matches the data for the 8th and 9th in both scenarios – it started collecting data from the same point in time. It’s more or less behaving as it should be, restricting the data from the point of creation of the dimension or metric.

Unfortunately, there’s not a direct solution aside from planning your dimensions and metrics ahead of time. If retroactive data for the new dimension is crucial, you might need to look into exporting and reprocessing your raw data, depending on your data architecture and resources.

[Jackson]

To track how long a user has a modal window open, you can use the ‘Timer’ trigger in Google Tag Manager (GTM). Essentially, you want to start the timer when the modal is opened and stop it when the modal is closed. Send events to Google Analytics at these two points capturing the timestamp. The difference in time will give you the total time the modal was open. For your setup where you use a jQuery modal, use ‘Percent Visible’ to start the timer and ‘Click Classes’ (clicking outside the modal or the close button) to stop the timer.

[Jackson]

Sure, I’d be happy to explain. Essentially, Google Analytics uses a system of first party cookies. These cookies hold onto an ID that tags the user’s browser while they’re on your website, right? Unfortunately, these can’t be directly used in your Data Management Platform (DMP).

Moving or copying these cookie IDs to your DMP isn’t impossible though. Here’s what you can do: You must wait for the same user to return to your site. Once they’re on your site again, their browser will be recognized and you can then transfer their ID to your DMP cookie.

You also have another option. You could write your DMP’s userID as a custom dimension in Google Analytics. This will give you a way to build a bridge or link so to speak, between the data you have on GA and the data on your DMP.

Hope this makes more sense! Do let me know if you need any more help.

[Jackson]

It appears like you’re missing some essential fields for authentication: ‘refresh_token’ and ‘client_secret’. The refresh token is used to refresh the access token which is required for the authentication process. The client secret is used to authenticate the client. You’ll have to ensure you’re providing these in your authentication request. These tokens would have been provided to you when you set up your Google APIs account or when the app was registered to use the Google service. Check your Google API Console to ensure these values are not missing from your credentials settings and that they are being correctly incorporated in your authentication script.