| A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | AA | ||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Updated 17/04/26 | Here is an offer for my CXL Institute GA4 Audit course: Use this link to enrol: http://cxl.com/institute/#_r_neal72 Get a10% discount by entering the coupon code: 10INSTRUCTOR in the checkout by reloading the checkout page with the coupon slug. ?coupons=yes to enable the coupons field. | Now updated with with dedicated section on Shopify stores | |||||||||||||||||||||||||
2 | Optional | No | Item | Status | Notes | Recommendation | Impact | Impact Reporting | Console Config or Tracking | GTM | Requires Dev | Rquires Client | Links | |||||||||||||||
3 | 1.0 | Planning and Performance Marketing | ||||||||||||||||||||||||||
4 | Yes | 1.1 | What are the business goals? | In progress | Combined template | H | Y | N | N | N | Y | |||||||||||||||||
5 | Yes | 1.2 | Has a measurement plan been created? | In progress | Combined template | H | Y | N | N | N | Y | |||||||||||||||||
6 | Yes | 1.3 | Is there a tag implementation plan? | In progress | Combined template | H | Y | N | N | N | Y | |||||||||||||||||
7 | Yes | 1.4 | What is their North Star Metric? | Not started | Having an agreed North Star metric helps companies ensure everyone is aiming for the same goal | M | Y | N | N | N | Y | https://datmark.gumroad.com/l/metric-algorithm?utm_campaign=viral-post&utm_medium=message&utm_source=linkedin | ||||||||||||||||
8 | No | 1.5 | Has the GA4 event structure been documented? | Not started | Documenting the events and custom parameters makes it easier for users to create custom reports | M | Y | N | N | N | Y | |||||||||||||||||
9 | No | 1.6 | How is GA4 installed? gtag.js, GTM or Measurement ID? | Not started | Check how GA4 or Firebase (for Apps) is installed and that the implementation is site wide. | H | N | Tracking | Y | N | Y | https://juliana-jackson.com/gtagjs-ga4-implementation-guide/ | ||||||||||||||||
10 | No | 1.7 | Has the site been scanned to measure GTM/GA4 coverage on the site? | Not started | Use custom search in Screaming Frog to check for GTM code on every page | H | Y | Tracking | N | N | N | https://www.tayloreddata.com/blog/how-to-use-screaming-frog-to-check-for-missing-google-analytics-tags | ||||||||||||||||
11 | No | 1.8 | Have Core Web Vitals been checked using Google PageSpeed Insights? | Not Started | Review PageSpeed Insights to understand if need to measure loadspeed metrics | H | Y | Configuration | N | N | N | https://pagespeed.web.dev/ | ||||||||||||||||
12 | Yes | 1.9 | Optional: Has the website been reviewed for accessibility? | Not Started | To decide if user experience metrics need to be monitored, check for accessibility issues | N | N | Configuration | N | N | N | https://chromewebstore.google.com/detail/silktide-accessibility-ch/mpobacholfblmnpnfbiomjkecoojakah | ||||||||||||||||
13 | No | 1.10 | For benchmarking, in Account details, has Modelling contributions and business insights been enabled? An industry category must also been selected | Not Started | Benchmarking is available in the Overview report for one metric at a time. Select the medal icon to enable benchmarking. | L | Y | Configuration | N | N | N | https://www.wix.com/seo/learn/resource/ga4-benchmarking | ||||||||||||||||
14 | No | 1.11 | Is there a concern that GTM is slowing the website load speed ? | Not Started | It is possible to implement a script to delay some non-critical GTM tag events | L | N | Tracking | N | Y | N | |||||||||||||||||
15 | No | 1.12 | Check website set up using Stape's free website evaluaiton tool | Not Started | Provides a score out of 10 and includes server-side GTM | H | Y | Stape | N | N | N | https://stape.io/website-tracking-checker | ||||||||||||||||
16 | 2.0 | Data Privacy & Controls | ||||||||||||||||||||||||||
17 | No | 2.1 | Does the website have a cookie consent banner and is it compliant with local or international laws (e.g. GDPR or data protection legislation)? | Not started | In the UK, the ICO requires all websites to give equal prominence to Accept and Reject cookies in their cookie consent banners | H | H | Tracking | Y | N | Y | |||||||||||||||||
18 | No | 2.2 | What level of cookie consent is required before tracking users in GA4? Google Consent Mode basic or advanced (v2) need to be implemented for all GA4 properties which use Google advertising platforms | Not started | GTM consent mode communicates your users' cookie or app identifier consent status to Google. Consent Mode is required by Google for any websites in Europe which use any Google advertising platform, such as Google Ads or Google Ad Manager. | M | Y | Tracking | Y | N | Y | |||||||||||||||||
19 | No | 2.3 | Are there any consent related errors in the Chrome console, such as "Refused to frame domainname.com because it violates the Consent Security Policy" | Not started | This can be caused by the Google Tag firing before or at the same time as the Conent mechanism tag | L | Y | Tracking | Y | N | N | |||||||||||||||||
20 | No | 2.4 | If using Microsoft Ads, Microsoft Consent Mode also needs to be implemented | Not started | Needed for EU and is in addition to Google Consent Mode. Parameter in Chrome called ASC, with D = Denied | L | Y | Tracking | Y | N | N | https://www.youtube.com/watch?v=XsxEa43sltE | ||||||||||||||||
21 | No | 2.5 | Has Google Signls been enabled? | Not started | When Google Signals is enbled this allows GA4 to collect more data for ad personalisation, including demogrphic data, which is required for ad retargeting via Google Ads. | L | Y | Console config | N | N | N | |||||||||||||||||
22 | No | 2.6 | Have advanced Ad Personalisation settings been configured to exclude certain countries? | Not started | Advanced settings, are ad personalisation disabled in certain countries? | L | N | Console config | N | N | Y | |||||||||||||||||
23 | No | 2.7 | Do we need to block personalised advertising for certain events/audiences (NPA)? | Not started | GA4 audiences/events can have NPA (non-personlised ads) enabled in Admin to prevent certain events and audiences using those events for being included in Google Ads campaigns. | L | N | Console config | N | N | Y | |||||||||||||||||
24 | No | 2.8 | Has Data Retention been changed from the default setting for Exploration reports? | Not started | Maximum of 14 months for GA4 Free and 50 months for 360 | H | Y | Console config | N | N | N | |||||||||||||||||
25 | No | 2.9 | Is the data retention period re-set every time a user visits the site? | Not started | The default is to enable this setting | L | Y | Console config | N | N | N | |||||||||||||||||
26 | No | 2.10 | Is User-provided data collection turned on? DO NOT TURN THIS ON | Not started | If you intend to export raw data to BigQuery and collect UserId, turning this on will prevent the UserId dimension from being exported to BigQuery. In addition, this feature has a tendency to think that company email addresses on a website are user email addresses, allocate it to all/most users and then traffic will collapse as GA4 thinks they are all the same users | Generally recommend not turning this on | L | N | Console config | N | N | N | ||||||||||||||||
27 | No | 2.11 | Redact most email information from event data | Not started | Enable in GA4 console | L | Y | Console config | N | N | N | |||||||||||||||||
28 | No | 2.12 | Redact URL query parameters from specific event parameters | Not started | Enable in GA4 console and specify individual query parameters such as gtm_debug and fbclid | L | Y | Console config | N | N | Y | |||||||||||||||||
29 | 3.0 | Property Settings: | ||||||||||||||||||||||||||
30 | No | 3.1 | Does the Property structure meet the needs of the business? | Not started | Recommend separate GA4 property is created for staging sites if GTM has been implemented on it. | L | N | N | N | N | N | |||||||||||||||||
31 | No | 3.2 | Has a test GA4 Property been created to test changes in console before they are implemented in GA4 Live Property? | Not started | Create new property and then add the Measurement ID as a new destination in Configure Tag Settings of Live Propery web data stream | Create test property | M | Y | Console config | N | N | N | https://www.optimizesmart.com/using-the-ga4-test-property/ | |||||||||||||||
32 | No | 3.2 | If you are on paid GA4, consider using subproperties as a replacement to views or create new collections for GA free | Not started | L | Y | Console config | N | N | N | ||||||||||||||||||
33 | No | 3.3 | Verify time-zone settings in the property | Not started | L | Y | Console config | N | N | N | ||||||||||||||||||
34 | No | 3.4 | Verify currency settings in your property | Not started | L | Y | Console config | N | N | N | ||||||||||||||||||
35 | No | 3.4 | Review user permissions | Not started | Keep Admin to users who need it | L | N | Console config | N | N | N | |||||||||||||||||
36 | 4.0 | Data Stream Settings | ||||||||||||||||||||||||||
37 | No | 4.1 | Review data stream(s) | Not started | Check only a single web data stream and separate streams for iOS and Android apps - For roll-up property see 12.0 | H | Y | Console config | N | N | N | |||||||||||||||||
38 | No | 4.2 | Is data being recieved by the GA4 property and use DebugView to test | Not started | H | Y | Tracking | Y | Y | N | ||||||||||||||||||
39 | No | 4.3 | Configure site search event in Enhanced Measurement | Not started | Specify up to 10 parameters in order of precedence, separated by commas. Only the first matching parameter will be used. | L | Y | Console config | N | N | N | |||||||||||||||||
40 | No | 4.4 | Has "Page changes based upon browser history events" been enabled? | Not started | This is designed for single page application content changes, but is best turned off so that we can control when page views are fired using GTM/data layer | M | Y | Console config | N | N | N | |||||||||||||||||
41 | No | 4.5 | Turn off duplicate Enhanced Measuement Events if configured in GTM | Not started | Form interaction is not a useful event and video start will often not work with YouTube videos | M | Y | Console config | N | N | N | |||||||||||||||||
42 | 5.0 | Configure Tag Settings | ||||||||||||||||||||||||||
43 | 5.1 | Manage Automatic Event Detection | Not started | This controls the Enhanced Measurement events and will overide settings in the Data Stream. | M | Y | Console config | N | N | Y | ||||||||||||||||||
44 | 5.1 | Set domain and cross-domain tracking | Not started | If users are taken to another domain to complete purchase, it is wise to add this domain to the GA4 console and for booking engine domains | M | Y | Console config | N | N | Y | ||||||||||||||||||
45 | 5.2 | Filter internal traffic | Not started | Specify IP addresses or create a landing page for staff. Check Test Data Filter dimension | L | Y | Console config | N | N | Y | ||||||||||||||||||
46 | 5.3 | Filter developer traffic | Not started | Configure to prevent users using GA4 Debug view (from GTM) from appearing in pre-built reports - Not always worth it, but can check Test Dev Filter | L | Y | Console config | N | N | N | ||||||||||||||||||
47 | 5.4 | Configure unwanted referrals | Not started | Review referrals and check unwanted referral list | L | Y | Console config | N | N | Y | ||||||||||||||||||
48 | 5.5 | Review session-timeout settings | Not started | Users often open a website and keep the tab open, returning after an hour or so. This would trigger a new session. Setting the session duration to something longer than 30 minutes would be a good idea, to the maximum of 7 hours 55 minutes | L | Y | Console config | N | N | Y | ||||||||||||||||||
49 | 5.6 | If needed, adjust timer for engaged sessions | Not started | How many seconds should a visitor stay on a page to be considered as an engaged user. This should depend on the nature of the site and user behaviour. Normally set the timer to at least 30 seconds or 60 seconds. The default is just 10 seconds on a page does is not long enough for a user show much engagement. | M | Y | Console config | N | N | Y | ||||||||||||||||||
50 | 5.7 | Do not use "Collect Universal Analytics events" option in the data stream | Not started | Not recommended as no control over set up and will replicate GA3 event structure | H | Y | Console config | N | N | N | ||||||||||||||||||
51 | 5.8 | Disable the “ignore duplicate instances of on-page configuration” setting | Not started | Admin > Manage Google Tag - The slider is OFF for older properties, and ON by default for newer ones. If you're using the Google Tag in GTM to fire page_view events in a single page application, this will break your implementation and you'll need to change the setting. | L | Y | Console config | N | N | N | ||||||||||||||||||
52 | 5.9 | Admin Tab - Changes | Not started | Check history for any major changes to discuss with client | L | Y | Console config | N | N | N | ||||||||||||||||||
53 | 6.0 | Data Settings | ||||||||||||||||||||||||||
54 | 6.1 | Userid | Not started | Consider sending userid to data layer via GTM to improve attribution | L | Y | Console config | N | N | Y | ||||||||||||||||||
55 | 6.2 | Channel groups - Up to 2 custom channel groups can be created in GA4 free and 5 in GA 360 - Also see Data Quality section below. | Not started | Have custom channel groups been created to adjust for source, medium, campaign ID and campaign name. Check for email clients in referrals and (not set). If the word "shop" appears in the utm_campaign parameter and the utm_medium includes the word "paid", the traffic is automatically classified as "Paid Shopping" — even if the source and medium would normally categorize it as "Paid Social.". As Paid Shopping is 3rd and so delete or move in your custom channel group. | M | Y | Console config | N | N | Y | https://kpplaybook.com/resources/how-to-report-on-traffic-from-ai-tools-in-ga4/?utm_medium=social&utm_source=linkedin&utm_campaign=dana+post&utm_content=20250729 | |||||||||||||||||
56 | 6.3 | Obtain a list of top affiliates or partner sites from client to compare against default channel groupings | Not started | Often UTMs are not fully utilised and some affiliates don't use them in links to websites | M | Y | Console config | N | N | Y | ||||||||||||||||||
57 | 6.4 | Check UTM parameters are used for campaigns and links provided to other websites (.e.g. affiliates and Progressive Web App) | Not started | Review source/medium in Traffic Acquisition report. UTM parameters are required to ensure accurate traffic attribution as custom channels can only be configured using source, medium, campaign ID and campaign name. For links from PWAs, add UTMs for attribution. | M | Y | Tracking | N | N | Y | ||||||||||||||||||
58 | 6.5 | Check if UTM parameters are being sent correctly to GA4: | Not started | Use Chrome extension to check for redirects as a) Server-side redirects can remove UTMs, b) JavaScript redirects may remove UTMs, c) GTM variables can be set to remove query parameters d) Not using the correct format "&"s and underscores | M | Y | Tracking | Y | Y | N | ||||||||||||||||||
59 | 7.0 | Shopify Stores Only - GTM | ||||||||||||||||||||||||||
60 | 7.1 | Do they use Shopify Plus or Shopify standard? | Not started | If on Shopify Plus: implement structured tracking in checkout.liquid or via controlled Web Pixel logic. If on Standard Shopify: use Customer Events and server-side tracking to compensate for limited checkout control. Document constraints clearly in architecture. | L | Y | Tracking | N | Y | N | ||||||||||||||||||
61 | 7.2 | GTM installation method – Mixed installs (theme, additional scripts, checkout custom pixel) can cause duplication or missed events. | Not started | Single documented GTM install in theme.liquid + Customer Events for checkout (non-Plus). Remove legacy “Additional Scripts”. If have GTM in theme, there is no need for a loader in the Custom Pixel in checkout | L | Y | Tracking | N | Y | Y | https://www.analyticsmania.com/post/install-google-tag-manager-and-ga4-on-shopify/ | |||||||||||||||||
62 | 7.3 | Legacy Additional Scripts in checkout – Can duplicate purchase events or conflict with server-side tracking | Not started | Remove entirely. Use Customer Events + Webhooks or server-side GTM (Stape server app and data layer in Custom Pixel). To identify how many loaders exist on the site use our script and paste into the Chrome console tab. | M | Y | Tracking | Y | N | Y | https://pastebin.com/9AMN2qiU | |||||||||||||||||
63 | 7.4 | Shopify Web Pixels behaviour – Sandbox iframe can overwrite page paths (e.g. /web-pixels@). | Not started | This happens when the Data Layer is enabled via Shopify Customer Events, but key parameters are not being sent to GA4; page_location, page_title and page_referer. | Send page_location, pate_title and page_referer to GA4 in GTM | L | Y | Tracking | Y | N | N | https://www.linkedin.com/feed/update/urn:li:activity:7382302311403999232/ | ||||||||||||||||
64 | 7.5 | App-injected tracking (Elevar, Littledata, Trackify, Triple Whale, YouTube app etc.) | Not started | Check DevTools: Sources for injected JS; inspect Network tab for duplicate event senders. Disable app tracking unless the app is the single chosen ecommerce provider. | L | Y | Tracking | Y | N | N | ||||||||||||||||||
65 | 7.6 | How are events sent to GA4? What is the client vs server-side event split? – Mixed ownership causes duplication or attribution gaps. | Not started | Define clear responsibility: client-side for browse events, server-side for cart/checkout/purchase. Document architecture. | L | Y | Tracking | Y | Y | N | ||||||||||||||||||
66 | 7.7 | What is the purchase event integrity? Missing or duplicate transactions distort revenue and ROAS | Not started | Unique transaction_id, no duplicates, GA4 purchase count within 3–5% of Shopify | L | Y | Tracking | Y | Y | N | ||||||||||||||||||
67 | 7.8 | What does the webhook reliability indicate (if using server-side/Littledata)? Failed webhooks will result in lost revenue events. | Not started | Monitoring and replay capability enabled. Validate webhook success logs. | L | Y | Tracking | Y | N | N | ||||||||||||||||||
68 | 7.9 | Has cross-domain tracking been configured. Checkout or myshopify domain can breaks sessions leading to Direct traffic inflation. | Not started | Configure cross-domain linking for storefront to myshopify and checkout domain. | L | Y | Tracking | Y | N | N | ||||||||||||||||||
69 | 7.10 | How good is UTM persistence – Shopify navigation strips UTMs after landing page. | Not started | Store UTMs in first-party cookie/local storage. Send via GTM or server-side to preserve attribution. | L | Y | Tracking | Y | N | N | ||||||||||||||||||
70 | 7.11 | Single source of page_view – Dual page_view firing breaks session attribution. | Not started | One page_view source only. Ensure Google Tag loads before event tags. | L | Y | Tracking | Y | Y | N | ||||||||||||||||||
71 | 7.12 | AJAX cart behaviour – Add to cart events may not trigger if tied to page loads. | Not started | Fire add_to_cart on actual cart update event, not URL change. | L | Y | Tracking | Y | Y | N | ||||||||||||||||||
72 | 7.13 | Data layer structure – App-modified data layers cause fragile tagging. | Not started | Standardised GA4 ecommerce schema. No GA3 category/action/label logic. | L | Y | Tracking | Y | N | N | ||||||||||||||||||
73 | 7.14 | Are Item ID & SKU consistent? A mismatch breaks Ads, Merchant Center & attribution. | Not started | Use SKU as item_id consistently across platforms. | L | Y | Tracking | Y | N | N | ||||||||||||||||||
74 | 7.15 | Do they use app-injected pixels? Shopify apps may inject tracking outside GTM. | Not started | Centralise control in GTM or server-side. Disable duplicate native tracking. | L | Y | Tracking | Y | N | N | ||||||||||||||||||
75 | 7.16 | Have Google Ads and other pixel tags been tested? | Not started | In Network tab; check for: pagead/conversion, googleadservices (conversions and remarketing), ccm/collect (Conversion Linker support calls), g/collect (indirect path),. For Bing, search for bat.bing.com (tag fired), action/0 (conversion endpoint), and UET. | M | Y | Tracking | Y | N | N | ||||||||||||||||||
76 | 7.20 | GTM | ||||||||||||||||||||||||||
77 | 7.21 | Check for correct implementation, including multiple implementations and GTM on every page. | Not started | M | Y | Tracking | Y | Y | N | |||||||||||||||||||
78 | 7.22 | Has Google Tag been configured according to best practice to fire before any other GA4 event tag, including page_views? This will ensure the parameters in the Configuration variable are present on all tags and a separate page view event is fired immediately afterwards. | Not started | The Google Tag should fire on all page views and following a navigation evet/history change on SPAs. If user_id is required for analysis in Explore reports, ensure it is sent using a different name as a user property. | H | Y | Tracking | Y | N | N | https://www.simoahava.com/analytics/google-tag-template-in-google-tag-manager/ | |||||||||||||||||
79 | 7.23 | Are custom dimensions and metrics, such as event scoped, user scoped and session scoped parameters configured correctly? | Not started | E.g. Time stamp, GTM container and version ID, login status, path clean, affiliate ID, userId and plan type. | M | Y | Tracking | Y | Y | N | ||||||||||||||||||
80 | 7.24 | For marketing Pixels (e.g. Google Ads, Facebook, TikTok) have base tags (page_view events) been configured? | Not started | Check pageview events have not been hard-coded onto site. | M | Y | Tracking | Y | N | Y | ||||||||||||||||||
81 | 7.25 | For Google Ads, has cross-domain tracking been enabled if required (e.g. where there is a booking engine which takes orders)? | Not started | The Conversion Linker tag has a checkbox for cross-domain tracking. This should be enabled if users are completing a purchcase event on another domain. | M | Y | Tracking | Y | N | N | ||||||||||||||||||
82 | 7.25 | Have marketing pixels been created for specific events, such as lead generation or purchase and do they include dynamic variables (e.g. value and quantity)? | Not started | Check the standard events used by the vendor | M | Y | Tracking | Y | N | Y | ||||||||||||||||||
83 | 7.26 | Are single page applications configured for history changes or data layer pushes to accurately track content changes | Not started | Data layer page_view events are reliable than history changes and best avoid using a combination of both | M | Y | Tracking | Y | Y | N | ||||||||||||||||||
84 | 7.27 | Are Lookup and RegEx tables set up to minimise the number of tags in GTM, especially for Google Ads ID and label? | Not started | L | N | Tracking | Y | N | N | |||||||||||||||||||
85 | 7.28 | Create a variable for the Measurement ID so that data from different environments can be sent to separate GA4 properties to prevent data pollution and it can easily be added to other tags | Not started | Data from production and testing environments should be sent to different GA4 properties. | L | Y | Tracking | Y | N | Y | ||||||||||||||||||
86 | 7.29 | Is the data layer populated with required data (.e.g. user_id, Salesforce_id, author name, content category)? | Not started | The user_id needs to be pushed to the data layer every time the page refreshes. | M | Y | Tracking | Y | Y | Y | ||||||||||||||||||
87 | 7.30 | Are data layer pushes used for events which are unable to track using GTM (e.g. iFrame form submissions)? | Not started | M | Y | Tracking | Y | Y | Y | |||||||||||||||||||
88 | 7.31 | Login status - Is this needed? | Not started | Because session scoped dimensions don't exist in GA4, this needs pushed to the data layer on every page refresh, set up as an event scoped dimension and then added to every event tag in GTM. | L | Y | Tracking | Y | Y | Y | ||||||||||||||||||
89 | 7.31 | Are there any obvious concerns about the GTM container? | Not started | Number of tags/size of container, too many auto-event listners or obsolete events? | M | N | Tracking | Y | N | Y | ||||||||||||||||||
90 | 7.32 | Configure custom hour dimension for Looker Studio dashboards | Not started | Looker Studio does not have access to hour dimension and so it is necessary to create a custom dimension in GTM | L | Y | Tracking | Y | N | N | https://twooctobers.com/blog/time-of-day-reporting-in-ga4-looker-studio/ | |||||||||||||||||
91 | 7.33 | Are they capturing click IDs for paid advertising campaigns, incliuding GCLID and MSCLKID. GBRAID and WBRAID for Google Ads, ttclid for TikTok and FBCLID for Meta? | Not started | Persisting click IDs and utms, and sending with all GA4 events can help prevent attribution from breaking | M | Y | Tracking | Y | N | N | ||||||||||||||||||
92 | 7.34 | Capture UTM parameters to enable dynamic content or targeting based upon source, medium or campaign etc | Not started | L | N | Tracking | Y | N | N | |||||||||||||||||||
93 | 7.35 | Create site search zero results event | Not started | If using JavaScript variable to capture search results, remember to disable search in Enhanced Measurement | M | Y | Tracking | Y | N | N | ||||||||||||||||||
94 | 7.36 | For page_view event, add path_clean and value {{page path}} | Not started | Remember to register parameter in GA4 | M | Y | Tracking | Y | N | N | ||||||||||||||||||
95 | 7.37 | Are you tracking clicks from AI Overviews (AIO), Featured Snippets, or People Also Ask (PAA) features in GA4? | Not started | Create custom JavaScript variables and parmeters for capturing. Remember to register new parameters in GA4 console. Because ChatGPT and Bing also include #text in their results, filter this by eg "session source/medium = google/organic", in order to be sure you're just getting Google traffic | M | Y | Tracking | Y | N | N | https://kpplaybook.com/resources/how-to-track-traffic-from-aio-featured-snippets-paa-results-ga4/?utm_medium=social&utm_source=linkedin&utm_campaign=dana+post&utm_content=20250321 | |||||||||||||||||
96 | 7.40 | Fred Pikes's GTM Practices | ||||||||||||||||||||||||||
97 | 7.41 | Add tag name in settings for all tags | Not started | Now can be captured automatically in Advanced settings > Additional metadata | L | N | Tracking | Y | N | N | ||||||||||||||||||
98 | 7.42 | Add tag name in GA4 UI events | Not started | If you use the UI to create events, always include a parameter to indicate the source of the event | L | N | Tracking | Y | N | N | ||||||||||||||||||
99 | 7.43 | Track GTM container and version in every event tag | Not started | Enables easier tracking of when events stop working | L | N | Tracking | Y | N | N | ||||||||||||||||||
100 | 7.44 | Track client and session ID as user activities. Client ID and Session ID are now built in variables you just need to enable if using GTM | Not started | Useful if you ever need to send data via the Measurement Protocol. Enable in GTM | M | Y | Tracking | Y | N | N |