Google Analytics 4 Setup Checklist

Google Analytics 4 Setup Checklist

Google Analytics 4 (GA4) helps businesses understand how users discover their websites, interact with content, and complete important actions. A correct setup is essential for collecting reliable data and making informed marketing decisions.

This Google Analytics 4 Setup Checklist helps digital marketers, website owners, analysts, and marketing teams configure GA4, verify data collection, define events and conversions, and prepare reports for ongoing analysis.

Use this checklist when setting up GA4 for a new website, auditing an existing property, implementing analytics after a redesign, or troubleshooting data collection issues.

1. Prepare for GA4 Implementation

Before creating or modifying analytics settings, define what needs to be measured.

• Identify the website, app, or digital property to track.

• Document the main business objectives.

• Identify the important user actions to measure.

• List the required events and conversions.

• Confirm who owns the analytics implementation.

• Check whether a GA4 property already exists.

• Review any existing Google Analytics or Google Tag Manager implementation.

• Identify the people who need access to analytics reports.

• Document relevant privacy, consent, and data retention requirements.

Verification: Ensure the measurement plan identifies the important user actions and reporting requirements before implementation begins.

2. Create or Verify the GA4 Property

The GA4 property is the primary location where analytics data is collected and organized.

• Sign in to Google Analytics using the appropriate Google account.

• Confirm that you have the necessary permissions.

• Check whether an appropriate GA4 property already exists.

• Create a new property if required.

• Enter a clear property name.

• Select the appropriate reporting time zone.

• Select the correct currency for relevant business reporting.

• Review the business details and reporting objectives requested during setup.

• Confirm that the property belongs to the correct business or organization.

• Document the property details for future reference.

Verification: Confirm that the property name, time zone, currency, and ownership details are correct before collecting production data.

3. Configure the Web Data Stream

A web data stream connects your website to GA4 data collection.

• Open the appropriate GA4 property.

• Navigate to the data collection or data stream settings.

• Create a web data stream if one does not already exist.

• Enter the correct website URL.

• Provide a descriptive stream name.

• Review the enhanced measurement settings.

• Record the measurement ID for implementation.

• Confirm that the stream corresponds to the intended website.

• Review settings for collecting page views and other supported interactions.

Verification: Confirm that the web data stream points to the correct domain and that its measurement ID is recorded accurately.

4. Install the GA4 Tracking Code

GA4 can be implemented directly using the Google tag or through Google Tag Manager, depending on the website setup.

• Decide whether to use the Google tag directly or Google Tag Manager.

• Confirm whether an existing implementation is already active.

• Add the appropriate tracking code or configure the tag in GTM.

• Use the correct GA4 measurement ID.

• Follow the installation requirements of your website platform.

• Confirm that the tag loads on the intended pages.

• Check whether the website already contains another GA4 implementation.

• Avoid installing duplicate tracking code.

• Review consent management requirements before activating analytics storage.

• Publish implementation changes only after completing the appropriate checks.

Verification: Use available browser debugging tools or tag diagnostics to confirm that the Google tag is loading correctly.

5. Test Data Collection

A tag appearing in the page source does not automatically mean that analytics data is being collected correctly.

• Open the website using a test browser session.

• Visit the homepage.

• Navigate to several important pages.

• Check whether page views are collected.

• Open GA4 Realtime reporting.

• Use DebugView when debugging events.

• Confirm that events are associated with the correct property.

• Check for missing or duplicate page views.

• Test desktop and mobile experiences.

• Review browser console errors if data collection fails.

• Verify that consent settings do not unintentionally block expected collection.

Verification: Confirm that test activity appears in the appropriate debugging or reporting tools. Standard reports may take longer to populate than real-time or debug views.

6. Configure Enhanced Measurement

Enhanced measurement can automatically collect certain interactions without requiring separate manual event configuration, depending on the settings and implementation.

• Review the enhanced measurement options available for the web stream.

• Confirm whether automatic page views are enabled.

• Review scroll measurement.

• Review outbound click tracking.

• Check site search tracking if applicable.

• Review file download tracking.

• Check supported video engagement measurement where relevant.

• Confirm that the selected settings match the measurement plan.

• Test important automatically collected events.

• Check for duplicate collection caused by overlapping manual and automatic tracking.

Verification: Confirm that enabled measurements work as expected and that the resulting events provide useful information.

7. Define and Validate Events

Events record user interactions and other activities that occur on your website or app.

• List the events required by the measurement plan.

• Review automatically collected and recommended events before creating additional events.

• Identify interactions that require custom event tracking.

• Establish consistent event names.

• Define the parameters needed for reporting.

• Configure events using the selected implementation method.

• Test event triggers.

• Verify event names and parameters in DebugView or available diagnostics.

• Check for duplicate events.

• Document each event's purpose and implementation.

Examples of events to consider include:

Verification: Ensure that event names, parameters, and trigger conditions match the intended user actions. Use Google's recommended event naming conventions where applicable.

8. Configure Key Events and Conversions

GA4 uses key events to identify activities that are especially important to a business. Google Ads may use imported GA4 events for conversion measurement when configured appropriately.

• Identify the actions that represent meaningful business outcomes.

• Confirm that the corresponding events are implemented.

• Mark the appropriate events as key events in GA4.

• Check whether the selected event should count every occurrence or follow another applicable counting approach in downstream systems.

• Verify that purchase values and currencies are passed correctly where relevant.

• Review key event reporting.

• Confirm that lead submissions, purchases, or other important outcomes are recorded as intended.

• Check whether key events are duplicated.

• Document which key events are used for business reporting.

• If linking to Google Ads, review which conversions should be imported and used for bidding.

Verification: Complete a test conversion where possible and confirm that the correct event is recorded. Remember that GA4 key events and Google Ads conversion actions are related concepts but are not automatically identical in every configuration.

9. Configure Internal Traffic and Data Filters

Internal traffic and unwanted data can affect reporting quality.

• Identify relevant internal traffic sources.

• Review the available internal traffic definition settings.

• Configure rules for appropriate internal IP addresses where supported.

• Review developer traffic requirements.

• Understand how testing or developer traffic is identified.

• Review available data filters.

• Check the current filter status before activating changes.

• Test changes carefully before relying on filtered reports.

• Document filter definitions and their intended effects.

• Review whether the filters behave as expected.

Verification: Confirm that internal or developer traffic is handled according to the reporting requirements. Avoid activating a filter without understanding its impact on collected data.

10. Review Cross-Domain Tracking and Referral Settings

Additional configuration may be needed when a customer journey crosses multiple domains or uses external payment and form systems.

• Identify all domains involved in the customer journey.

• Check whether users move between different domains during a session.

• Configure cross-domain measurement where appropriate.

• Verify that the domains are configured correctly.

• Test navigation between the relevant domains.

• Review referral behavior from third-party services.

• Investigate payment gateways or external systems that may affect attribution.

• Confirm that session continuity behaves as expected.

• Document any known limitations.

Verification: Test the complete journey and review the resulting analytics data to confirm that unnecessary session breaks or referral attribution issues are not occurring.

11. Review Consent and Privacy Requirements

Analytics configuration should follow applicable privacy requirements and the website's consent implementation.

• Identify the privacy requirements relevant to the business and audience.

• Review the website's privacy policy.

• Confirm that cookie or tracking disclosures are appropriate.

• Check whether a consent management platform is required or used.

• Verify that consent choices are passed correctly to the relevant tags.

• Test behavior when consent is granted or denied.

• Review data collection settings against the organization's privacy requirements.

• Avoid sending personally identifiable information to Analytics.

• Review data sharing and access settings.

• Document the implementation and responsible owner.

Verification: Test consent behavior and confirm that tracking operates according to the applicable requirements. Seek qualified advice where legal interpretation is necessary.

12. Configure Reports and Analysis

Prepare GA4 so the team can answer practical business questions.

• Review the standard Reports collection.

• Confirm access to acquisition reports.

• Review engagement reports.

• Check landing page reporting where available.

• Review event and key event reports.

• Confirm ecommerce reporting if applicable.

• Create or customize reports where required.

• Configure useful comparisons and dimensions.

• Use Explorations for deeper analysis where appropriate.

• Document recurring reporting requirements.

• Confirm that relevant team members know how to access the reports.

Verification: Test whether the reports answer the actual questions stakeholders need to address, rather than collecting metrics without a clear purpose.

13. Link Relevant Google Marketing Platforms

Integrations can help connect website analytics with advertising and other reporting workflows.

• Identify whether a Google Ads link is required.

• Verify the correct Google Ads account before linking.

• Confirm that the necessary permissions are available.

• Review personalization and data-sharing options associated with the integration.

• Configure the link according to the organization's requirements.

• Check whether conversions should be imported into Google Ads.

• Review other relevant product links where supported.

• Confirm that linked account settings are correct.

• Test reporting and imported conversion behavior where applicable.

• Document the purpose of each integration.

Verification: Confirm that the correct accounts are linked and that any imported or shared data is being used as intended.

14. Review Data Retention and Access Permissions

Appropriate retention and access settings help manage analytics data responsibly.

• Review the data retention settings available for the property.

• Select an appropriate retention period according to business needs and applicable requirements.

• Review user and administrator access.

• Remove access that is no longer needed.

• Assign permissions according to each person's responsibilities.

• Confirm that reporting users can access the required information.

• Document the property owner and backup administrator.

• Review settings periodically.

• Record relevant configuration decisions.

Verification: Confirm that access is appropriate and that retention settings align with the organization's requirements.

15. Complete the Final GA4 Quality Assurance Review

Perform a structured review before declaring the setup complete.

• Verify the property and web stream.

• Confirm the correct measurement ID.

• Check tracking implementation across important pages.

• Validate page view collection.

• Test required events and parameters.

• Verify key events and conversion-related reporting.

• Check for duplicate tracking.

• Review internal traffic filters.

• Validate cross-domain tracking if applicable.

• Test consent behavior.

• Confirm reports and integrations are accessible.

• Document outstanding issues and limitations.

• Obtain approval from the responsible stakeholder.

Verification: Record the QA results and ensure that critical tracking issues have been resolved or explicitly assigned for follow-up.

16. Monitor GA4 After Setup

Analytics implementation should be checked after deployment, not only during installation.

• Review Realtime reporting after launch.

• Check whether important events continue to arrive.

• Review key event trends.

• Investigate unexpected changes in traffic or event volume.

• Check for missing or duplicate events.

• Review relevant acquisition and landing page reports.

• Confirm that website changes have not broken tracking.

• Check relevant diagnostics and notifications.

• Schedule periodic implementation reviews.

• Update documentation when tracking requirements change.

Verification: Compare observed data with expected user activity and investigate significant discrepancies before relying on the reports for decisions.

Common GA4 Setup Mistakes to Avoid

• Using the wrong property or measurement ID: Verify the destination before deploying the tag.

• Installing tracking twice: Check for overlapping website, plugin, and GTM implementations.

• Ignoring event quality: Validate names, parameters, and trigger conditions.

• Marking every event as a key event: Prioritize meaningful business outcomes.

• Ignoring consent settings: Test tracking behavior under different consent states.

• Filtering traffic without testing: Understand the effect of filters before activating them.

• Assuming reports populate instantly: Allow for processing delays where applicable.

• Linking the wrong advertising account: Verify account identity and permissions.

• Failing to document the setup: Maintain a record of tags, events, filters, and integrations.

Final GA4 Setup Sign-Off Checklist

Before completing the implementation, confirm:

• Property and data stream are correct.

• The Google tag or GTM implementation is working.

• Data collection has been tested.

• Enhanced measurement settings are appropriate.

• Required events and parameters are validated.

• Key events and conversion-related settings are correct.

• Internal traffic and other filters have been reviewed.

• Cross-domain tracking is configured where necessary.

• Consent and privacy settings have been tested.

• Reports and relevant integrations are available.

• Data retention and access permissions are reviewed.

• QA results and outstanding actions are documented.

• Post-implementation monitoring is scheduled.

Conclusion

A reliable GA4 implementation depends on correct property configuration, accurate event collection, validated key events, appropriate privacy controls, and regular quality checks. Use this checklist to establish a measurement foundation that supports meaningful website and marketing analysis.

Learn. Prepare. Grow. — GoBizly

Explore more practical learning resources and checklists at GoBizly to improve your analytics implementation and reporting skills.