Conversion tracking setup in GA4 for Canadian businesses involves the same technical steps as US setup, but with several PIPEDA and CASL compliance considerations that materially affect implementation. **Step 1: Define what counts as a conversion.** The 1–3 outcomes that genuinely connect marketing activity to business revenue. For service businesses: form submissions for consultations, phone calls (tracked via call-tracking software), live chat conversations that reach handoff, calendar booking completions. For ecommerce: completed purchases, plus secondary conversions like add-to-cart and checkout-started. For B2B SaaS: demo requests, free trial signups, qualified lead form fills. Avoid vanity 'conversions' like newsletter signups, content downloads, or page views — these dilute conversion data and make it harder to evaluate program performance. Track them as Events but not as Key Events. **Step 2: Implement Events through Google Tag Manager.** GTM is the recommended approach for most Canadian businesses — easier to maintain than direct GA4 implementation, easier to add additional analytics tools as needs evolve, and easier to manage consent state. Configure each conversion as a separate GTM Tag firing on a clearly-defined Trigger. **Step 3: Mark Events as Key Events in GA4.** In GA4, navigate to Admin → Events and toggle 'Mark as key event' for each conversion Event. This makes them appear in conversion reports and Goal-related calculations. GA4 allows up to 30 Key Events; use the slots for genuine business outcomes. **Step 4: Configure Enhanced Measurement.** GA4's Enhanced Measurement automatically tracks scrolls, outbound clicks, site search, video engagement, and file downloads. Enable selectively based on what's actually useful for your reporting; over-enabling produces noise without signal. **Step 5: PIPEDA-compliant consent management.** Canadian privacy law (PIPEDA federally, plus provincial equivalents like Quebec's Law 25) requires meaningful consent before processing personal information. The practical implementation: - Implement a Consent Mode v2 setup in GTM that respects user consent choices - Configure GA4 to receive only consented tracking when consent is denied (Google's Consent Mode handles modeled conversions for non-consenting users while respecting the consent decision) - Use a Canadian-aware consent management platform (Cookiebot, OneTrust, or Iubenda all support PIPEDA workflows) - Document your consent flows for auditability **Step 6: CASL compliance for any tracking that triggers commercial electronic messages.** If your conversion tracking ties into email automation that sends commercial messages, ensure the consent capture explicitly authorizes CEMs separately from analytics consent. **Step 7: Validate end-to-end.** Use GA4's DebugView to confirm Events fire correctly during real user journeys. Use GTM's Preview Mode to validate Tag firing. Test with consent both granted and denied to confirm Consent Mode handles both cases correctly. **Step 8: Document and monitor.** Document each conversion Event with: business definition, technical Trigger, expected volume range, and ownership. Set up custom alerts for unusual deviations (sudden conversion drops often indicate broken tracking rather than sudden business changes).