[Grayson]

Try reviewing your Adobe Launch implementation for any tracking issues that could be causing this. Maybe the first party cookies aren’t getting set correctly or there could be issues with cross-domain tracking. Check for any incorrectly implemented filters in GA360 that could be excluding return visits. Also, consider any recent changes made to your website that may have impacted tracking. For instance, if you recently updated your site to force HTTPS, users who previously visited the HTTP version of your site will be considered new again on the HTTPS version. Look into browser related impacts as well – cookie policies of browsers can vary and this might affect tracking. Lastly, ascertain whether this issue is occurring across all browsers or is it localized to a specific few.

[Grayson]

You may be facing issues because your current variable setup doesn’t seem to be extracting the “item_name” data properly. You may need to adjust your JavaScript variable in Google Tag Manager so that it correctly accesses the “item_name” data from the dataLayer variable representing your “ecommerce.items”. After doing this, if you are still getting an array, you can use JavaScript’s join() method. This method can convert your array of “item_name” data into a single text string, with each item separated by a comma.

Here’s a snippet of how you may adjust your code:

`
var itemslist = [];
var products = {{dl – ecommerce.items}};
for(i=0; i < products.length; i++){
itemslist.push(products[i].item_name);
}

return itemslist.join(', ');
`

Doing so should give you the item names in a text format, separated by a comma.

[Grayson]

It’s clear you’re dealing with a complicated analytics set-up, and your hesitation to change the current dual configuration setup is justifiable. But, it’s also evident that your standalone properties and ‘the beast’ have different capabilities. ‘The beast’ is a more integrated, holistic approach, but might be too complex for some of your teams. The standalone properties are simpler but may be limiting for more complex analyses.

Let’s consider your two solutions, starting with ‘The Duplication Dance’. While it might seem more manageable in the short term, this method will likely become more difficult to maintain in the long run due to the double-work involved. However, it does cater to those who prefer a simpler analysis structure, allowing people to work in the analytics environment they’re most comfortable with.

Your second option, ‘The Sole Player’, is more forward-thinking and aligned with where analytics is headed, particularly with the phasing out of Universal Analytics. However, since GA4 is still relatively new and complex, this would involve a learning curve for your teams.

Taking all factors into account, it may be best to gradually transition to ‘The Sole Player’. While it will involve training and change management, utilizing just one, more advanced and integrated analytics platform will provide more comprehensive insights and could be a powerful tool for your organization in the long run. But consider doing this gradually – to ensure your teams have time to upskill appropriately. As for data stream permissions, this is something to check with GA4 since the view level permissions of Universal Analytics doesn’t exist in GA4. In the end, it’s about balancing the capabilities of the tool and the skill and comfort level of your teams.

[Grayson]

In the context of integrating GA4 with SSIS using KingswaySoft, I don’t have specific knowledge about KingswaySoft’s GA4 component. However, based on my experience with a UA to GA4 reporting project, I can provide some insights.

In Google Analytics, a metric represents a countable quantity, such as the number of cows. For example, if you have 10 cows, the metric is “I have 10 cows.”

On the other hand, a dimension provides additional details or descriptions about the metric. Using the cow example, you can have dimensions like the color of the cows. For instance, “I have 6 black cows and 4 white ones.”

It appears that when selecting a metric or dimension in the KingswaySoft’s GA4 component, there might be filtering implemented to exclude incompatible dimensions. For example, if you try to add the dimension “pagePathPlusQueryString” to your queries, you may receive an error message like:

“Please remove pagePathPlusQueryString to make the request compatible. The request’s dimensions & metrics are incompatible.”

Since you have purchased the product, it would be beneficial to reach out to KingswaySoft for assistance with the challenges you are facing. They should be able to provide guidance on how to access the necessary drop-down dimensions and metrics list for the Google Analytics Data API.

Please note that my response is based on general understanding of the concepts involved and may not directly apply to the specific implementation of KingswaySoft’s GA4 component.

[Grayson]

This sounds like a challenging, yet interesting problem. It appears that you have a well-functioning PHP service that utilizes the Google Analytics API. This service uses the same account and set of credentials to successfully run reports on manually created properties but hits a ‘PERMISSION_DENIED’ roadblock when it comes to properties that were machine-generated. Despite the account possessing admin access on all accounts and properties, the service-specifically denies permission for these properties. You’ve attempted troubleshooting by creating a GA4 property both manually and via script, and by playing around with the rights and permissions of the service account-all to no avail. Understandably, this boggles you, as the service seems to be able to manipulate data using the same credentials, yet fails to run reports. You’ve also confirmed that the credentials file, client request format, and service account permissions are all kosher. This surely is a perplexing situation.

[Grayson]

Unfortunately, without detailed information about the specific error message you’re encountering or the specific code you’ve installed, it’s difficult to provide a concrete answer. However, a common problem could be related to the set up of your conversion tracking. Make sure you created a conversion action in your Google Ads account, and that your GA4 tag is correctly linked to your Google Ads account. Another possible issue could be with the installation of the tag on your website. It needs to be placed on the correct page − the one after a conversion action has been taken by your users. Also, remember that it might take up to 24-48 hours for initial conversions to show. If the problem persists, it is recommended to seek the help of a professional or a Google-certified marketing expert.