AmbassadorHub

Description

AmbassadorHub is a peer-to-peer fundraising platform plugin for WordPress. It provides everything you need to run ambassador-led fundraising campaigns:

• Accounts — Ambassador role, email verification, custom profile fields, frontend portal
• Campaigns — Campaign custom post type with lifecycle management
• Fundraisers — Individual and nested (team) fundraiser pages, with a shared team total
• Donations — Donation tracking, donor deduplication, and GDPR anonymization
• Payment Connectors — Built-in Stripe and PayPal PSP connectors
• Consent — Privacy-policy and marketing-consent checkboxes, WP Privacy API export/erasure support
• REST API — Full REST API under ambassadorhub/v1

Need more payment providers (Mollie, Buckaroo), the automation rule builder, custom fields, or marketing integrations? Those ship in the optional AmbassadorHub Premium add-on. Want to run petitions and signature-collection campaigns alongside your fundraisers? See the optional AmbassadorHub Petitions add-on.

External Services

This plugin connects to third-party payment services when you configure a payment provider. No external connections are made until you explicitly enable and configure a provider under Settings → Integrations.

Gravatar
Used to display a profile picture for ambassadors and donors who haven’t uploaded their own image, via WordPress core’s own get_avatar()/get_avatar_url() functions (the same fallback WordPress itself uses for comment authors and user profiles).
Data sent: the user’s email address (hashed before sending, per Gravatar’s own API).
Triggered when: an ambassador, donor, or fundraiser owner’s avatar is displayed and no custom profile picture has been uploaded.
– Privacy policy: https://automattic.com/privacy/
– Terms of service: https://wordpress.com/tos/

PayPal
Processes payments via PayPal checkout.
Data sent: donation amount, currency, customer details, return and cancel URLs. The site’s own configured PayPal API credentials are also used to obtain an OAuth access token, and to verify orders/process webhook events.
Triggered when: a donor initiates a payment and PayPal is the active provider; also when a PayPal webhook event arrives, and when a site administrator clicks “Test connection” in Settings → Payments.
– Privacy policy: https://www.paypal.com/us/legalhub/privacy-full
– Terms of service: https://www.paypal.com/us/legalhub/useragreement-full

Stripe
Processes payments via credit card and other Stripe-supported methods.
Data sent: donation amount, currency, customer details, payment method tokens.
Triggered when: a donor initiates a payment and Stripe is the active provider; also when a site administrator clicks “Test connection” in Settings → Payments (a read-only request to confirm the configured API key is valid).
– Privacy policy: https://stripe.com/privacy
– Terms of service: https://stripe.com/legal

Google Analytics / Google Tag Manager (opt-in, off by default)
Under Settings → Advanced → Analytics, the site owner can enable pushing fundraiser, campaign, and ambassador-registration events to the browser dataLayer. This setting is disabled by default and nothing is pushed until it is turned on. When enabled, events are consumed by whatever GTM container or gtag.js snippet the site owner has already installed — the plugin does not load Google’s scripts itself.
Data pushed: event name, and the fundraiser or campaign’s title (for fundraiser/campaign events only — the ambassador-registration event carries no additional data).
Triggered when: this setting is enabled, and a fundraiser is published, a campaign starts or ends, or an ambassador registers.
Cookie: only while this setting is enabled, and only when a payment provider is also configured, the plugin sets a first-party cookie named ambh_tk (a random UUID, no personal data) to correlate browser sessions across page loads. The cookie has a one-year expiry and is not set otherwise.
– Privacy policy: https://policies.google.com/privacy
– Terms of service: https://policies.google.com/terms

Technical details