[Noah]

In Google Tag Manager (GTM), it’s unfortunately not feasible to apply one set of tags and triggers to every client regardless of the domain. Tags and triggers are specific to each container which is specific to each website, meaning you have to individually specify them for every client. As for the issue of pushing a bunch of data into the data layer, it’s just how GTM works: it pushes event info into the data layer based on the activities on the website. If you want to push data into the data layer using JavaScript, you could use the dataLayer.push method to do so, yet you would need to implement this separately for each client due to the unique data structure of each website. As for reusing triggers and tags, when you create another container, it will always start as an empty workspace. You can, however, export a container (which includes the tags and triggers) and then import it into another container, which might help save some time.

[Noah]

Absolutely, I can help you better understand this. In the new GA4 version 1 beta, the nextPageToken you might be used to from the older versions has been replaced by an ‘offset’ parameter in the API. How this works is, the return size from Google has a limit of 10,000 rows.

Now, let’s say you’re dealing with larger data. Here’s a nifty trick you can use, get into a habit of running a query with a predefined iterator that increases by 10,000 for each return. You can pass this number into the ‘offset’ parameter of the API. If the return is less than 10,000 rows or elements, take it as a sign that there’s no further data you can extract from that particular query.

Just keep in mind, though it’s possible to have certain caps and quotas removed with payment, the return size cap of 10,000 rows is non-negotiable.

I hope this makes your work with Azure Data Factory a little less puzzling and bit more exciting. Don’t hesitate to dive in and experiment!

[Noah]

Hi Greg,

Your plan sounds pretty solid! If both sites share the same top level domain, it’s as simple as publishing the same GTM container on your WordPress site as you have on your Shopify site. Then Google Analytics 4 should take care of the rest assuming the tags are triggered as expected.

For different top level domains, you’d need to set up what’s called cross-domain tracking. It might sound complex but it’s a simple enough process in GA4. In your GA4 property, go to ‘Admin’, then ‘Data Streams’ and ‘Web’. From there, you head to ‘Configure tag settings’ and ‘Configure your domain’. You’ll need to modify the conditions under ‘Include domains that match ANY of the following conditions’ to enable cross-domain tracking. Once you’re done, hit ‘Save’. Here’s a [link](https://support.google.com/analytics/answer/10071811?hl=en) which explains it in more detail.

Hope this helps!

[Noah]

Google Ads conversion tracking involves multiple components and usually requires setup both in Google Ads and Google Analytics. Google Conversion Id is a part of this process and it cannot be considered separately. While GA4 does change the landscape a bit and encourages a more event-driven model of tracking, it doesn’t completely eliminate the need for a specific conversion Id. Since you’ve mentioned using Google Tag Manager (GTM), it’s good to know that GTM is essentially a more flexible tool, allowing you to manage tracking codes centrally, and it’s generally well-integrated with GA4. It’s not necessarily about finding an easier or harder way, it’s about understanding how these tools work together. Check out resources by Google Analytics Academy and Simo Ahava’s blog, these can provide very straightforward and explanatory tips on how to get one’s head around this.

[Noah]

You’ll need to do a few things. First, head to the “Events” section in Google Analytics and create a new event, that you’ll use to track when the form gets submitted.

Next, go to the “Conversions” section and create a “New Conversion Event”. You’ll want to use the same name as you used in the first step, for the custom event.

Lastly, there’s a setting that you need to check. Proceed to “Data Streams” and select your data stream. Find the “enhanced measurement” options, click on the gear icon and make sure that “form interactions” is switched on. And there you have it! Once you’ve done all this, your form submissions should start getting tracked as conversions.