A GA4 setup checklist template is a structured framework that ensures you configure every critical dimension, conversion, and audience setting during migration or initial deployment. This guide walks through building and using a checklist that prevents data gaps and aligns tracking with your actual business goals.
Start your GA4 setup checklist template with foundational property settings. Record your property ID, the exact data stream name, and the measurement ID you embed in Google Tag Manager or directly on-page. For Canadian sites serving Quebec, note whether you need separate streams for French and English subdomains or a single stream with language as a custom dimension. Document your data retention settings—the default is two months for user-level data, but many businesses extend this to fourteen months for year-over-year analysis. List the Google Signals activation status, which ties cross-device behavior to signed-in Google users and is crucial for remarketing audiences. Include a checkbox for Search Console linking, which surfaces organic query data inside GA4's acquisition reports and prevents the manual CSV export workflow you relied on in Universal Analytics. Finally, note timezone and currency—set CAD for Canadian ecommerce sites to avoid conversion rate distortions in revenue reports.
GA4 operates on events rather than pageviews and sessions, so your checklist must define which events to track and which to mark as conversions. Begin with automatically collected events like page_view, session_start, and first_visit, then list recommended events you need to implement manually: file_download, video_start, scroll depth milestones, outbound link clicks. For ecommerce, enumerate the required purchase funnel events—view_item, add_to_cart, begin_checkout, purchase—and confirm each carries the correct parameters like currency, value, item_id, and item_name. Lead-generation businesses should list form_submit events tied to each lead magnet or contact form, tagged with a form_name parameter to distinguish newsletter signups from demo requests. SaaS sites need trial_start, subscription_upgrade, and churn events. Mark which events qualify as conversions in your checklist: a purchase event is obvious, but you might also convert on scroll-to-pricing or video_complete for top-of-funnel content campaigns. Assign an owner or implementation method—GTM trigger, server-side tag, manual data layer push—next to each event so accountability is clear during deployment.
GA4 allows thirty custom dimensions and fifty custom metrics per property, but you must define them before data flows in—retroactive application is impossible. Your checklist template should reserve rows for each custom dimension you plan to track: user_type to separate logged-in customers from anonymous visitors, content_category for blog topics or product lines, author_name for editorial performance, landing_page_template for layout testing. Canadian businesses often add province or region as a user property to slice campaign performance by Ontario versus British Columbia, or language_preference to measure French versus English engagement in bilingual campaigns. List the scope—event, user, or item—next to each dimension, because scope determines where the value can be used in Explore reports. Custom metrics track numeric values beyond the defaults: profit_margin for ecommerce, video_watch_time for media sites, form_completion_time for UX analysis. Document the parameter name exactly as it appears in your data layer or GTM variable, and cross-reference it to the friendly display name you set in the GA4 admin interface. This mapping prevents confusion six months later when a new analyst tries to build a funnel report and cannot locate the dimension they need.
Audiences in GA4 power remarketing, exclusion lists, and cross-platform activation in Google Ads and DV360. Your checklist should enumerate every audience you intend to build: purchasers in the last ninety days, cart abandoners in the last seven days, high-engagement users who triggered three or more scroll events in a session, newsletter subscribers who have not converted. For each audience, note the membership duration—how long a user remains in the segment after meeting the criteria—and whether you need it in Google Ads for remarketing or just for internal analysis. Canadian retailers running separate campaigns in Alberta versus Quebec should define province-based audiences so ad spend aligns with regional inventory or language. Document the Google Ads account link in your checklist: GA4 will not send audiences to Ads until you explicitly link the properties and grant permissions. Include a test step for each audience—trigger the qualifying event yourself, wait twenty-four hours, then confirm the audience populates in the Ads audience manager. This catches configuration errors like incorrect event parameter matching or overly restrictive conditions that leave the audience perpetually at zero users.
A GA4 setup checklist example must address data hygiene. Create a section for internal traffic exclusion: list all office IP addresses, VPN exit nodes, and developer staging environments, then confirm you have added them as data filters in the GA4 admin panel or excluded them via a GTM blocking trigger. Document referral exclusions for payment gateways like Stripe, PayPal, or Shopify checkout subdomains—without exclusion, these appear as referring sources and break attribution. For Canadian businesses using bilingual checkout flows or third-party booking widgets, add those domains to the exclusion list as well. Include a row for bot filtering, which GA4 enables by default but should be verified in your data stream settings. If you run significant paid campaigns, note whether you have enabled Google Ads auto-tagging or manual UTM parameter rules, and specify the naming convention—Canadian teams often adopt a standard like campaign-province-language-offer to keep reporting clean across regional buys. Finally, add a recurring checklist item for quarterly data quality audits: compare GA4 session counts to server logs or a secondary analytics platform, review the Realtime report for unexpected spikes in unassigned traffic, and scan the Events report for duplicates or malformed event names that indicate tagging drift.
The final section of your GA4 setup checklist framework is validation. For every event and dimension you configured, perform a live test using GA4's DebugView: trigger the event on your own device with debug mode enabled in GTM or via the query parameter, then watch the event appear in DebugView with all expected parameters and values. Document each test result in the checklist—timestamp, device used, pass or fail status, and any parameter mismatches. Check that conversions appear in the Realtime report's conversions card within seconds of triggering the event. For ecommerce implementations, place a test order and confirm the purchase revenue matches the order total in your shopping cart, not an inflated or deflated figure caused by tax or shipping handling errors. Once all items are validated, export the checklist as a shared document—Google Sheets works well—and grant view access to stakeholders: marketing managers who will build campaign reports, developers who maintain the tag setup, and external agencies managing paid media. Include a version number and last-updated date at the top of the template. This handoff step ensures that when someone asks why a particular dimension was configured or an audience was built, the answer lives in the checklist rather than in one person's memory. For Canadian teams working across Toronto, Montreal, and Vancouver offices, a centralized checklist prevents duplicate work and keeps configuration consistent across regional properties.
A setup checklist covers initial configuration of a new GA4 property from scratch, including data streams, events, dimensions, audiences, and integrations. A migration checklist focuses on transferring Universal Analytics goals, custom dimensions, and view filters to their GA4 equivalents before the UA sunset. Setup is broader; migration is a one-time mapping exercise that references the setup checklist to ensure nothing is lost in transition.
Add rows for CAD currency configuration in the data stream settings, enhanced ecommerce parameters like tax and shipping in purchase events, province-level custom dimensions for regional campaign analysis, and bilingual event naming if you serve Quebec customers. Include a Google Merchant Center link if you run Shopping ads, and document how you handle cross-border shipping events for US customers buying from Canadian inventory.
Most Canadian businesses use a single GA4 property with a language or region custom dimension. Separate properties complicate audience sharing, cross-domain measurement, and reporting consolidation. A language dimension lets you filter French sessions in Explore reports and build French-speaking audiences for Google Ads without maintaining two measurement IDs or duplicating event definitions. Reserve separate properties only if legal or data residency requirements mandate strict isolation.
Review the checklist quarterly or whenever you launch a new product, campaign type, or content format that requires additional tracking. Google releases GA4 feature updates regularly—consent mode enhancements, new recommended events, expanded integration options—so schedule a twice-yearly audit to incorporate new capabilities. If your traffic or conversion patterns shift significantly, revisit audience definitions and conversion events to ensure they still align with business priorities.
Enable DebugView in GA4 and systematically trigger each event on your checklist while watching the real-time stream. Verify that every event fires with the correct parameters, conversions increment in the Realtime report, and custom dimensions populate in the user or event details. Cross-check that Google Ads audiences appear in your linked Ads account within twenty-four hours. If any item fails validation, mark it incomplete in the checklist and document the failure reason before moving on.
The core structure—property configuration, event taxonomy, dimensions, audiences, testing—remains the same, but the specific events and conversions differ. SaaS sites need subscription lifecycle events like trial_start, upgrade, and cancellation, while lead-gen sites focus on form_submit, PDF download, and contact_sales events. Customize the event rows and conversion definitions in your template to match the funnel stages relevant to your business model, but keep the validation and documentation sections unchanged.