Checkout Tracking - WeGive Documentation

Use this reference to configure Google Tag Manager, Tealium, Facebook Pixel, or Meta Conversions API with WeGive checkout. It covers Portal V1 and V2 in single-page and stepper layouts: 21 standard events, eight stable HTML attributes, 134 control identities, and their payload fields. WeGive supplies standard events and field names. Your organization configures tag routing, consent rules, reporting labels, and downstream mappings. Optional controls exist only when their checkout feature is enabled and rendered.

Set up tracking

Required access, connection details, sharing controls, and a validation checklist.

Events and payloads

Milestones, successful payments, recurring plans, and exact event-specific data.

Stable checkout attributes

Native input listeners, custom selections, hosted fields, and all supported controls.

Webhook reference

Server notifications and their payloads, including checkout-session joins.

Quick lookup

Need	Read or listen to
Successful payment	`donationSuccess`; Tealium `value_transactionStatus` is `2`
New recurring plan	`recurringPlanCreated`; amount describes one installment
Session join	GTM `wegive.checkout_session_uuid`; Tealium `wegive_checkout_session_uuid`
Transaction reference	GTM `value.correlation_id`; Tealium `value_correlation_id` on outcome events
Current gift amount	GTM `wegive.amount`; Tealium `wegive_amount`; major units before covered fees
Revenue	Outcome `value.amount_dollars` / `value_amount_dollars`; major units including covered fees
Donor email, if sharing enabled	GTM `wegive_donor.email`; Tealium `donor_email`
Individual input	`[data-checkout-control="donor-email"]`, with scope/context/instance as needed
Custom selector or hosted card blur	`document` event `wegive:checkout-interaction`

Platform guides

Google Tag Manager: triggers, variables, custom listeners, and Google identity.
Tealium: native events, UDO variables, and custom extensions.
Facebook Pixel & CAPI: browser context, server payloads, matching fields, and deduplication.

Data references

Event payloads: every event-specific field, unit, and label.
Common checkout data: session, checkout, gift, page, and attribution fields.
Donor details & sharing: contact fields, settings, and lifecycle.
Control catalog: every supported stable control identity.
Page views & embedded checkout: route events and parent-window notifications.

For help with availability or configuration, contact [email protected].