Docs / Integration Tutorials /  

Donorbox

Donorbox Conversion Tracking And Attribution – How To Set Up

Track Donorbox thank you pages and attribute all plans and repeat donations to the original source.

Contents

Track Donorbox donations

Track Donorbox thank you pages, attributing each donation details to the website visitor source. Able CDP integrates Donorbox with ad platforms' conversion APIs using complete customer details, eliminating tracking problems. The unique capability of Able tracking combines in-browser tracking data with server-side Donorbox webhooks, allowing to report repeat revenue and subscriptions in ad platforms such as Facebook Ads and Google Ads, as well as report lifetime donations value in Google Analytics.

Once the initial donation is tracked, all visitor and ad click details are stored and associated with personal information, allowing Able CDP to attribute any future donations and plan lifecycle events to the original ad click and visitor source. Both front-end and server-side events can then be sent to ad platforms such as Google Ads, Facebook Ads Conversions API and TikTok Events API, as well as Google Analytics 4.

Able tracks the following Donorbox lifecycle events, collecting all into a single journey:

  1. Donations, combining data from thank you page tracking for the initial donation with webhook data
  2. Recurring donations using webhooks (RecurringSubscriptionPayment event)
  3. Plan creation (Subscribe event)
  4. Plan cancellation or pause (CancelSubscription event)
  5. Failed plan payment (FailedSubscription event)

Enable Donorbox thank you page tracking

In Able Dashboard, press "Add Service Integration" and select "Donorbox".

Enable tracking of Donorbox parameters in Able CDP tracking code to record customer details. For Able CDP tracking to work correctly, donation details, including personal details, should be enabled in the Donorbox campaign settings.

Send Donorbox webhooks to Able

Able attributes all follow-on revenue to the original donor source, allowing to measure and report lifetime value for each campaign.

  1. Login to your Donorbox account, click Add-ons in the left sidebar > click API & Zapier Integration
  2. Add Custom Webhooks for the following endpoints (where %%FUNNEL_MARK%% is unique funnel identifier, available in the Get Code section of the Able Dashboard):
  3. New/Update Donation - https://isr7zwf0y2.execute-api.eu-west-2.amazonaws.com/webhook/%%FUNNEL_MARK%%
  4. New/Update Plan - https://isr7zwf0y2.execute-api.eu-west-2.amazonaws.com/plan_webhook/%%FUNNEL_MARK%%

Frequently Asked Questions and Troubleshooting

Which Donorbox conversions are tracked?

Able tracks Donorbox through two routes that complement each other:

  • Browser tracking on the website: the embedded donation form and the Donorbox thank you page. This is what associates the website visitor (and their ad click identifiers) with the donor's details.
  • Server-side webhooks from Donorbox (New/Update Donation and New/Update Plan). These deliver every donation and plan lifecycle event reliably, even when browser tracking is blocked or the donor never returns to a thank you page.

When the same donation is reported by both routes, the browser event takes precedence and the webhook acts as a backup, so each donation is counted once.

The following events are supported:

  • InitiateCheckout. Tracked in browser when a donor enters their email in the embedded Donorbox form. Associates the browser visitor with the donor's email and name for attributing future donation events.
  • Purchase. Tracked for a one-time donation or the first payment of a new recurring plan. Generated in browser from the Donorbox thank you page, and server-side from a donation webhook with nothing refunded.
    • Data includes: donation ID, donation amount and currency, campaign (as a line item, with the Donorbox form ID as SKU), donor email, name and address
  • Donate. An identical copy of every Purchase, generated at the same time. Donate is the donation-specific name for the same event.
  • RecurringSubscriptionPayment. Generated by a donation webhook for a repeat payment on an existing recurring plan (the second payment onward). Such payments do not produce a Purchase or a Donate event.
  • Refund. Generated by a donation webhook that reports a refunded amount, whether the refund is full or partial.
  • Subscribe. Generated by a plan webhook when a recurring plan becomes active.
  • CancelSubscription. Generated by a plan webhook when a recurring plan is cancelled or paused. A pause is treated the same as a cancellation.
  • FailedSubscription. Generated by a plan webhook when a recurring payment can't be collected and the plan status becomes failed.

Each server-side event carries the donation amount, the campaign it went to, and the donor's name, address and email. If Donorbox has converted the amount to another currency, the converted amount is used. Plan webhooks with any other status are ignored and no event is recorded.

Why does a donation appear twice in Able?

Every Purchase is accompanied by an identical Donate event, so a single donation shows up as two events in the customer journey. When totalling donations, count only one of them. Purchase is the event most integrations, such as Google Analytics and ad platforms, use by default; Donate is available for cases where donations need to be distinguished from other kinds of revenue.

How are paused and resumed plans tracked?

A paused plan is recorded as a CancelSubscription event. When a paused plan resumes, Donorbox reports it as active again, which produces a new Subscribe event. Note that Donorbox sends a plan update webhook on other plan changes as well, so Subscribe events may also be recorded when an active plan is updated; use the first Subscribe event for a donor to determine when the plan was started.

Donations are tracked, but the donor source is missing. What should I check?

Able associates donor details with the website visitor via the InitiateCheckout event from the embedded form and the Purchase event from the thank you page. If a donor's history in Able contains only webhook events, verify that:

  • The Able tracking code generated in the Get Code section of the Able Dashboard is installed on the pages with the Donorbox form and on the thank you page, as well as throughout the rest of the website.
  • Passing donation details to the thank you page is enabled in the Donorbox campaign settings, so that the thank you page URL includes the donor's email and donation details.

Donorbox conversion tracking is commonly used with


This page has been written by the Able CDP Customer Success Team, formed of digital marketing practitioners and seasoned marketing data experts.
If you have any questions or suggestions, please contact us using the contact form.