> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wegive.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Setup Requirements

> Access, configuration, sharing choices, and validation steps for checkout tracking.

Checkout tracking supports both donor portals, in single-page and stepper layouts. Your organization's checkout configuration determines which controls and milestones are available.

## Required access

* Access to **Integrations** in your WeGive dashboard.
* Permission to configure and publish your organization's GTM container or Tealium profile.
* A checkout URL for testing, along with access to your destination's debugging or reporting tools.

## Integration details

| Platform | Information to enter in WeGive | Configuration in your tracking platform |
| - | - | - |
| Google Tag Manager | Web container ID, such as `GTM-ABC1234` | Custom Event triggers, Data Layer Variables, destination tags, and consent settings |
| Tealium | Account, profile, and environment | UDO variables, load rules, extensions, destination tags, and consent settings |

Follow the [GTM setup instructions](/external/onboarding/tracking/google-tag-manager) or [Tealium setup instructions](/external/onboarding/tracking/tealium). You do not need both services to track checkout.

## Choose your events and sharing settings

Use the [standard event catalog](/external/onboarding/tracking/standard-events) to choose the milestones your organization needs. A completed checkout, a successful payment, and a created recurring plan are distinct outcomes. Avoid counting multiple signals as separate donations.

Tealium's **Send standard checkout events** setting defaults off. If your profile already forwards WeGive events through custom code, remove that forwarding before enabling automatic delivery to avoid duplicates.

Review [donor-sharing settings](/external/onboarding/tracking/donor-sharing) before mapping contact fields. Common checkout context is available without donor sharing. Each integration's settings govern its own published fields and automatic payloads; browser scripts running on the same page are not isolated from each other.

## Custom event requirements

Custom listeners must run inside the checkout window. For embedded checkouts, code on a cross-origin parent page cannot directly inspect checkout controls. GTM Custom HTML tags and Tealium JavaScript Code extensions can install listeners in the checkout itself.

Read the [hook contract](/external/onboarding/tracking/checkout-hooks) and [control catalog](/external/onboarding/tracking/checkout-hook-catalog) before selecting interactions. Hosted payment fields and wallet controls have specific observability limits.

## Validate before publishing

1. Use GTM Preview or a Tealium test environment with your checkout URL.
2. Confirm that the event and current context reach the tracking platform.
3. Check which rules match and which tags execute.
4. Confirm that the intended destination receives the expected payload.
5. Test your donor-sharing settings across the donor flows your checkout supports, such as an already signed-in donor or a donor who signs in during checkout.
6. For any payment or recurring-plan events you use in reporting, check that the destination counts the intended outcome without duplicates. If you use `donationSuccess` for successful-payment reporting, confirm that pending and failed payments do not count as successful gifts.

An event arriving in GTM or Tealium does not prove delivery to the final destination. Your organization owns its tag configuration, destination mappings, and custom receiver setup.

## Support

For help configuring WeGive, contact [support@wegive.com](mailto:support@wegive.com).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.