[Ava]

Yes, tracking dynamic sub-sites with Google Analytics can be a little tricky, but it’s definitely achievable. Essentially, you will want to add a Google Analytics tracking code to each of your site’s templates, so that any new sub-site automatically has the code.

You can use a Google Analytics plugin like MonsterInsights or Google Site Kit that supports WordPress Multisite. These plugins will automatically add the tracking code to each new site created. Both plugins support network-wide settings so you don’t have to configure each site individually.

Another strategy is to use a single Google Analytics account with different ‘Views’ for each website. In this strategy, each sub-site would filter traffic to that specific sub-domain. However, this method will be manual and the new sites need to be added to the Google Analytics account and the relevant filters need to be set.

While Google Analytics API can be very powerful, it’s possibly overkill for what you need. Its steep learning curve makes it not the most viable option, unless you’re comfortable with coding and plan to perform advanced data manipulations.

The key here is automation. Any solutions that automatically apply the Google Analytics code to new sub-sites when they’re created are the way to go. Also, make sure that your solution separates data sufficiently, so you can analyze each sub-site individually. Experiment with different methods and see which one suits your workflow the best.

[Ava]

It seems like your custom dimension “Is site” might not be correctly set up, since it’s affecting your “Engagement rate” and “Bounce rate” measurements. This could be due to a variety of reasons, sometimes the custom parameters aren’t defined correctly in the code or the values being passed for that dimension aren’t recognized. Instead of being associated with each user’s behavior, it seems the custom dimension is acting like an event and hence not capturing engagement correctly. You might have to revisit the custom dimension setup to make sure it’s collecting and analyzing the data as expected. Additionally, check your settings for “Engagement rate” and “Bounce Rate”, as there may be conflicts with how the custom dimension is defined. If the problem persists, you might want to reach out to Google Analytics support for a pointed resolution to the issue.

[Ava]

This could be due to a myriad of factors. First, ensure you are using the proper Measurement ID within the Content this generates for the debug URL, and keep in mind that GA4 Debug view does have certain limitations. Mostly, the Debug view shows data in real-time, so if the events are not occurring at the time you’re inspecting the debug view, they won’t show up. Secondly, make sure you’ve correctly implemented your tags for this specific subdomain within Google Tag Manager, paying special attention to any differences between this subdomain and the ones functioning properly. Lastly, consider using Google’s Tag Assistant to validate, troubleshoot, and optimize your Google Tags. It could help you identify undetected issues that might be contributing to the missing events in the Debug View. Even small configuration issues could lead to these discrepancies. If none of this resolves your conundrum, it may be worth reaching out to the Google Support team for further assistance.

[Ava]

It’s not just you, creating a tracking pixel for Google Analytics 4 is a bit different! The old image src method doesn’t work anymore because GA4 prefers the POST method to send events. But, you’re not totally out of luck. Use a slightly different URL structure, as in your example but with “v=2” instead of “v=1” or “v=4”. This should give you the tracking pixel behavior you’re looking for.

[Ava]

You need to track the visitors’ source before they download the extension and sign up with their email. Assign each visitor a unique ID that will follow them through each step, from visiting your website to downloading the extension. This ID should then be included in the data that gets sent to Klaviyo so you can track where your users are coming from.

[Ava]

Google Analytics 4 (GA4) handles sessions differently from Universal Analytics. In GA4, there is no explicit way to manually end a session since it is based on an automatic algorithm. A new session is started after 30 minutes of inactivity, or at midnight local time and there is no built-in way to manually reset this.

You might want to consider other workarounds to get the insights you need:

1. User Pseudonymization: One possible solution could be to assign a unique pseudonym or ID to each user and send it as a user_id parameter with each event.

2. Event Customization: If you need detailed tracking for each transaction, you could create and track custom events for each step of the process. This would give you visibility into each user’s journey, regardless of whether it is technically considered as one session or multiple.

3. Cohort Analysis: GA4 has the ability to group users together with shared characteristics (e.g. transaction completed) with its Cohort analysis feature. This might provide the insights you need.

Be sure to comply with Google Analytics’ Terms of Service and any relevant data privacy laws and regulations if considering pseudonymization.

[Ava]

Unfortunately, adding custom dimensions and metrics in Google Analytics 4 (GA4) is murkier compared to Universal Analytics. GA4’s interface only allows selections from existing primary dimensions and metrics for summary card setup, meaning custom ones aren’t readily accessible.

However, it’s possible to create custom dimensions and metrics in GA4 using “Events and parameters”. You’d need to work with a developer or have some coding knowledge to set these up and ensure the values are sent to GA4. Once these are setup, they can then be used in analysis and reporting.

Bear in mind that GA4 is fundamentally different from Universal Analytics, being event-based rather than session-based. This could affect the way you setup and interpret your custom dimensions or metrics. It’s a matter of translating what you want to achieve from Universal Analytics’ perspective to GA4’s setup.

Still, if you’re very comfortable or reliant on using custom dimensions and metrics from Universal Analytics, you might find GA4 a bit limiting for now. You can still use them side by side until you’re fully ready to transition or until GA4 fulfills your needs.