AmbassadorHub

By Trybes

0+ active installationsVersion 1.2.1

Peer-to-peer fundraising platform — accounts, campaigns, fundraisers, and donations, running entirely on your own WordPress site.

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

Installation

  1. Upload the ambassadorhub folder to /wp-content/plugins/.
  2. Activate the plugin through the Plugins menu in WordPress.
  3. Navigate to AmbassadorHub → Settings to configure the plugin.
  4. Enable and configure a payment connector under Settings → Payments.

FAQ

Does this plugin require WooCommerce?

No. The plugin uses Action Scheduler (bundled) for background jobs, but does not depend on WooCommerce itself.

Can I use both Stripe and PayPal at the same time?

Only one PSP can be active at a time. You can configure both but select the active one under Settings → Payments.

Where do ambassadors log in?

Ambassadors use a frontend portal block (not wp-admin). Add the Account block to any page to create the ambassador dashboard.

Screenshots

Changelog

1.2.1

  • Fixed: team leaders could still invite members to a team that had ended, or whose fundraiser had ended or passed its end date. The “Invite member” option is now hidden for these teams, and the site refuses the invitation.
  • Fixed: opening an invitation to a team that has ended now says straight away that the team no longer accepts new members, instead of first asking the visitor to sign up or log in. The invitation is no longer used up when joining is refused.
  • Fixed: when you created a group right after creating a fundraiser, the group got the fundraiser’s picture. The group form now starts with an empty image field.
  • Fixed: the “Create a group” form shown after creating a fundraiser could not be submitted, because its button stayed disabled.

1.2.0

  • Ambassadors can log out from their account page.
  • Added “Forgot password?” to the login form. It uses WordPress’s own password reset and then returns the ambassador to the login page.
  • Ambassadors can change their password in the Profile tab. Changing it logs out their other devices.
  • The ambassador password rules now also apply when resetting a password.
  • The WordPress toolbar is no longer shown to ambassadors on the site.
  • Only ambassadors can create fundraiser pages. Other logged-in users see an explanation instead of the form.
  • Fixed: team leaders could not remove members from their team.
  • Fixed: opening a team invite while logged in as an administrator or editor changed that account into an ambassador account, which locked it out of the dashboard. Subscribers and customers still become ambassadors when they accept an invite. Invites to teams that have ended are now refused.
  • A page created from a team invite is published once the ambassador confirms their email address, like any other new page.
  • Fixed duplicate emails: “Your fundraiser is live” arrived twice after joining a team, each edit sent two “edited” emails, publishing a page also sent an “edited” email, and new invitees got two verification emails.
  • Fixed a server error when an email verification link arrived without its user ID.
  • Fixed: after activating the plugin, fundraiser page addresses could show “Page not found” until the permalinks were saved again.
  • Fixed: when the plugin was activated with WP-CLI, fundraiser pages logged database errors until someone opened wp-admin.
  • Fixed: add-on fields did not appear in the form when an ambassador started a new fundraiser.
  • Fixed: the “Minimum Target Amount” setting was ignored, so ambassadors could set any target. It now applies when an ambassador sets or changes a target. Set it to 0 for no minimum.
  • Deleting the plugin now also removes its spam protection, fundraiser and setup wizard settings.
  • The account page now works on sites installed in a subfolder and with plain permalinks.
  • The login form fields are now labelled for screen readers and password managers.
  • Smaller download: the plugin zip no longer includes the Plugin Directory banners and screenshots, or AI assistant instruction files bundled by a third-party library.
  • Categories for fundraisers, and for petitions when the AmbassadorHub Petitions add-on is active. Add them under AmbassadorHub → Categories, and choose them for a fundraiser or petition in the editor. When there is at least one category and ambassadors are allowed to start new fundraisers, they choose categories when they start one, and can change them later. Team pages, personal pages and sub-petitions get the categories of the fundraiser or petition they belong to. Category pages and category counts show each fundraiser or petition once, without its team and personal pages.
  • Developers: new ambh_account_password_changed action. The namespace key was removed from the ambhConstants script data; use restUrl instead. Categories use the new ambh_category taxonomy; add your own post types with the ambh_category_post_types filter. Category pages list only top-level actions; return false from the new ambh_category_archive_top_level_only filter to also list sub-pages. The fundraiser REST endpoints accept and return categories.

1.1.1

  • Security: removed the public REST endpoints for creating donations (POST /ambassadorhub/v1/donations and POST /ambassadorhub/v1/fundraisers/{id}/donations) and the public donation list (GET /ambassadorhub/v1/fundraisers/{id}/donations). They skipped the spam protection of the donation form, and nothing in the plugin used them. Visitors donate through the Donation Form block, as before.
  • Privacy: the marketing-consent checkbox on the signup and donation forms is now optional. Visitors can sign up or donate without agreeing to marketing email, and consent is only recorded when they tick the box. The privacy-policy checkbox is still required.
  • Fixed: the marketing-consent checkbox on the signup form was stretched to full width, with its label pushed below it.
  • Developers: the ambh_donation_rest_saved action and the ambh_donation_create_params filter no longer fire, because the endpoints that triggered them are gone.

1.1.0

  • Redesigned the frontend ambassador account dashboard: fundraisers and petitions now share one unified “My Actions” grid, filterable by type (Fundraisers, Petitions, Groups, Personal pages), instead of separate per-module sections.
  • Added a single “+ New action” menu for starting a new fundraiser, team, or petition, replacing the separate “+ Start a…” buttons each module previously rendered on its own.
  • KPI/stat tiles now stay visible on both the Dashboard and Profile tabs instead of disappearing when switching away from Dashboard.
  • Added ambh_account_dashboard_stats, ambh_account_dashboard_actions, and ambh_account_dashboard_create_actions hooks so add-ons (Petitions, Premium) can plug into the new stats row, actions grid, and create-action menu. The generic ambh_account_dashboard hook remains for backwards compatibility with existing integrations.

1.0.0

  • First stable release — AmbassadorHub is now available directly from the WordPress.org Plugin Directory.
  • Added built-in spam protection for the public signup, donation, and team-invite forms: an invisible honeypot field, a submission-timing check, per-visitor rate limiting, a disposable/blocked-email-domain filter, and a link-count filter on the donation message field. Every check runs entirely on this site — no CAPTCHA provider, no external service, nothing sent off-site — and is configurable (including fully disabled) from the new Settings → Spam Protection tab, which also shows a log of recently blocked attempts.
  • Added a per-account daily cap on team-member invitations, closing a gap where the existing per-team hourly limit could be bypassed by repeatedly creating new teams.