Skip to main content
Blackbaud → BranchIntegration guide

Connecting Blackbaud to Branch

Blackbaud runs large nonprofits where major gifts, grants and legacies dominate the income, and none of those come from a click. Branch's real job is the web-to-app seam — a person clicks a link in a browser, installs the app, and something has to carry the context across an install that destroys every cookie involved. The join between them succeeds or fails on one thing: whether the Branch link click identifier and the deferred deep link payload reaches the Blackbaud gift before the conversion happens, because Branch can only match a conversion it can tie back to a click it recognizes.

Free30 minutesNo obligation

Specific to this pair

Blackbaud and Branch: the leak is app to web form, not web to app

Use a Branch link to open the right appeal page on the Blackbaud-hosted donation form with campaign and user reference in the URL, if the form accepts them. Post the purchase to Branch's server-to-server API from the form confirmation with the transaction ID as event identifier, not from Raiser's Edge NXT, where batching breaks the user reference.

Branch carries click context across an install. For a nonprofit on Blackbaud, the seam that actually loses gifts usually runs the other way: a supporter in your app taps Donate and is sent to a Blackbaud-hosted donation form in a browser, and the app's context is gone by the time the gift is made. A Branch link can open the right appeal page with the campaign and a user reference in the URL, but only if the form accepts that value as a parameter or hidden field. Check yours before building.

When the gift completes, post a purchase event to Branch's server-to-server API from the form confirmation, keyed on the same user identity, with the form's transaction ID as the event identifier. Do not post from Raiser's Edge NXT: online gifts land there through a batch, often days later and after gift-entry staff have merged or corrected the constituent, so the original user reference may not survive.

The deferred deep link earns its keep in a peer-to-peer or event app where a fundraiser shares a personal page link: a friend installs the app to donate, and without Branch that donation looks organic and the fundraiser's share of credit disappears from your app reporting. If your app takes neither gifts nor registrations, Branch has nothing to attribute here.

Blackbaud → Branch · what breaks

Why this join usually fails — Blackbaud → Branch

  1. 01

    The Branch link click identifier and the deferred deep link payload never reaches Blackbaud

    Major gifts are relationship-led over years, and grants come through applications. Neither touches a website.

  2. 02

    One major gift distorting a whole year

    A single six-figure gift arriving in a month with a campaign running will make that campaign look extraordinary. Excluding major gifts from campaign reporting is not hiding good news — it is the only way the campaign figures mean anything.

  3. 03

    The install that erases the campaign

    Someone clicks a paid ad on the mobile web, hits the app store, installs, and opens the app as a brand new anonymous user. Without deferred deep linking that campaign produced an organic install, and the ad account shows nothing for a conversion it genuinely caused.

  4. 04

    Nothing reconciles afterwards

    Branch shows the attributed link and campaign on the event in its dashboard. Check that the install carries a link click rather than showing as organic, which is the failure this product exists to prevent.

Blackbaud → Branch · the fix

What working looks like — Blackbaud → Branch

  • The Branch link click identifier and the deferred deep link payload on every gift

  • Conversions arriving in Branch

    The event is attributed to the originating link and campaign, and forwarded to any configured downstream partners.

  • Reconciled against the source

Blackbaud → Branch · architecture

How Blackbaud and Branch actually connect

  1. 1

    Blackbaud holds the truth

    At large charities a handful of major gifts can exceed all online giving combined. Pooling them makes online campaign performance unreadable and swings wildly with events nobody advertised for.

  2. 2

    Branch needs a click to match

    Branch needs the link click context matched to the app open, plus the event and its revenue. Without the deferred deep link payload there is nothing to join the install to.

  3. 3

    The identifier is the bridge

    The Branch link click identifier and the deferred deep link payload, captured at the visit and carried into the Blackbaud gift.

  4. 4

    The event source decides reliability

    Send online gifts at amounts received, with recurring valued on stated retention. Major gifts and grants excluded.

  5. 5

    Deduplication at the destination

    Branch deduplicates on the event identifier you supply. Firing a purchase from both the SDK and your server without a shared identifier double-counts, and Branch forwards to downstream partners, so the duplicate propagates.

Blackbaud → Branch · normal or broken

Working vs. broken, side by side — Blackbaud → Branch

Normal, not a fault

  • The Branch link click identifier and the deferred deep link payload present on the gift

  • Sent from the Blackbaud gift record

  • Deduplicated correctly

    Branch deduplicates on the event identifier you supply. Firing a purchase from both the SDK and your server without a shared identifier double-counts, and Branch forwards to downstream partners, so the duplicate propagates.

  • Reconciles with the source

Actually broken

  • The Branch link click identifier and the deferred deep link payload missing on most records

    Major gifts are relationship-led over years, and grants come through applications. Neither touches a website.

  • Sent from the browser

    A single six-figure gift arriving in a month with a campaign running will make that campaign look extraordinary. Excluding major gifts from campaign reporting is not hiding good news — it is the only way the campaign figures mean anything.

  • Counted twice, or not at all

    Someone clicks a paid ad on the mobile web, hits the app store, installs, and opens the app as a brand new anonymous user. Without deferred deep linking that campaign produced an organic install, and the ad account shows nothing for a conversion it genuinely caused.

  • Nobody has reconciled it

Blackbaud → Branch · diagnose

Diagnostic order — Blackbaud → Branch

  1. 01

    Count gifts carrying the Branch link click identifier and the deferred deep link payload

  2. 02

    Follow one real conversion end to end

  3. 03

    Set a major-gift threshold and exclude above it from campaign reporting

    Report those separately and prominently. They are the most important income and the least attributable.

  4. 04

    Measure your organic install share and ask whether it is plausible

    An implausibly large organic share is usually broken attribution rather than genuine word of mouth.

  5. 05

    Read the match rate, not the success message

    Branch shows the attributed link and campaign on the event in its dashboard. Check that the install carries a link click rather than showing as organic, which is the failure this product exists to prevent.

Blackbaud → Branch · prove

How it gets proven — Blackbaud → Branch

Source of truth

Blackbaud gifts by date, with online gifts separated from major gifts, grants and legacies.

  • The Branch link click identifier and the deferred deep link payload confirmed present on a live gift.
  • Attributed installs and in-app purchases reconciled against your own user records, with the unattributed share stated.
  • Online gifts reconciled against imported conversions, with major gifts, grants and legacies excluded and reported separately.

Blackbaud → Branch · free audit

What we check in the free audit

  • Count gifts carrying the Branch link click identifier and the deferred deep link payload
  • Follow one real conversion end to end
  • Set a major-gift threshold and exclude above it from campaign reporting
  • Measure your organic install share and ask whether it is plausible
  • Read the match rate, not the success message

Checked against

Blackbaud gifts by date, with online gifts separated from major gifts, grants and legacies.

Get my free conversion tracking audit

Free30 minutesNo obligation

Blackbaud → Branch · when not to buy

When you don't need this — Blackbaud → Branch

  • Measure identifier coverage yourself first — pull your last hundred gifts and count how many carry the Branch link click identifier and the deferred deep link payload.
  • Small charities with no major-gift programme do not have this distortion.
  • If you have no app, or no web surface driving app installs, there is no seam here to bridge and the integration solves nothing.

Blackbaud → Branch · what we deliver

What gets built — Blackbaud → Branch

  • Identifier capture into Blackbaud

    Attribute online giving only, and hold major gifts, grants and legacies out of every campaign figure.

  • Event source: the Blackbaud gift record

    Send online gifts at amounts received, with recurring valued on stated retention. Major gifts and grants excluded.

  • Dispatch to Branch

    The Branch server-to-server events API, posted from your backend with the user identity and event data.

  • Reversals where they exist

    Refunds and cancelled recurring gifts reverse.

Written guarantee

95%+ tracking accuracy

Measured against Blackbaud gifts by date, with online gifts separated from major gifts, grants and legacies.. Miss it and we keep working at no cost.

Get my free conversion tracking audit

From $400 · See packages

FAQ

Blackbaud → Branch questions, answered

Yes, a Branch link can route to a web URL, including a hosted donation form. Whether attribution survives depends on the form passing the campaign or user reference through to its confirmation, so check that first.

Free · 30 min

Get Blackbaud and Branch joined properly

Free30 minutesNo obligation