[Mia]

In GA4, Google replaced the Multi-Channel Funnels Reporting API with the Google Analytics Data API, having made significant changes to the data model, analyses, and metrics. However, as of now, the GA4 Data API doesn’t offer a direct substitute feature to pull up the assisted conversion paths data like the old Multi-Channel Funnels Reporting API. GA4 only notably supports analyses based on the “first user source” and “session source” which somewhat limit the view of the conversion path. While you wait for Google to potentially roll out a feature for assisted conversion, you may indeed need to devise a new method to generate similar data. You might do so by piecing together user journeys from the user engagement data, but this can be complex and might not fully match the old assisted conversion paths metric.

[Mia]

It seems like you are looking to track your iframe’s interaction with your GA4 property. Firstly, make sure your gtag(‘config’,) command includes all the parameters you want to track like clientID and SessionID.

To set up cross-domain tracking through GTM, you’ll indeed need a GA4 configuration tag. However, initializing the GA4 property again in your custom HTML might lead to re-initialization, which is not the recommended way.

Instead, you should use the GA4 configuration tag in GTM and update that tag with your parameters. Adding your parameters there should send the information you need to GA4 when the tag fires. When it comes to event tracking, you need additional GA4 event tags in GTM for specific user interactions like clicks or form submissions.

So, instead of initializing GA4 again inside a custom HTML tag, consider using the Data Layer to push your clientID and SessionID, then use these values in your GA4 configuration tag. Remember that you’ll need to include these details in the GA4 configuration tag within Google Tag Manager, not in a custom HTML tag as that could indeed re-initialize your GA4 property.

[Mia]

This issue might happen due to several reasons. The first possibility could be something with the data processing in Google Analytics. Sometimes, they encounter issues that can temporarily affect data reporting. If it’s the case, it will likely be resolved by Google in a short time frame.

Another possibility may be that the specific user IDs whose data you’re trying to fetch might not have triggered any event recently causing the dimension data of those user IDs to be “(not set)”.

Finally, it is crucial to make sure that the custom dimensions are still active and not accidentally deleted or altered. Even if you haven’t made changes, it is still worth checking out if something has accidentally been modified or removed.

Overall, it would be best to thoroughly check your Google Analytics setup, maybe even involving a professional to analyze it. If everything seems fine, you might want to reach out to Google Analytics support.