Donorfy vs Beacon for Charities Running Paid Social Ads On Facebook

For UK fundraising teams running Meta ad campaigns, tracking conversions through browser-based pixels alone is no longer enough to scale profitably. With Safari’s ITP, ad blockers, and cookie consent banners routinely cutting out 20% to 40% of client-side tracking data, charities relying solely on standard pixel tracking are leaving Meta's ad delivery algorithms partially blind.

‍

The solution is the Meta Conversions API (CAPI) and Offline Event tracking. By transmitting donation data directly from your CRM’s server to Meta, your ad campaigns receive verified conversion records, accurate gift amounts, and crucial recurring payment milestones. When Meta can see which clicks on your ads have successfuly resulted in donations (conversions), its ad delivery algorithm is then better able to optimise your campaigns by serving ads to people with similar characteristics and behaviours to those who have already given, making your ad spend more efficient.

‍

Donorfy and Beacon CRM are both widely used by charities, and it's possible to export donor data to Meta CAPI from both, but neither offers an off-the-shelf, 'one-click' Meta CAPI toggle. Here's how they stack up when powering server-side fundraising campaigns.

‍

First, A Quick Look At How Meta Ads Tracking Works

‍

Attributing leads and sales to advertising campaigns has been a mainstay of direct response marketing for decades, and is critical to understanding what works and what doesn't.

‍

'Back in the day' adverts in newspapers might carry a phrase like "Quote '20 Off' when calling to claim your 20% discount", enabling call handlers to distinguish between people ringing to place orders organically and those who had been motivated to do so in response to the ad.

‍

Different telephone numbers were often used too, and 'cut out and send' discount vouchers would have unique identifiers printed on them to help understand where they'd come from (Radio Times vs Take A Break magazine etc).

‍

As advertising channels have changed over the years, so have the attribution mechanisms we use.

‍

When advertising online or on social media, we refer to the various techniques as 'tracking'. It sounds more sinister than it is; it's simply the use of modern technoogy to follow the journey people take from seeing an ad to taking action (or not).

‍

In digital fundraising using ads on Meta's platforms, Facebook and Instagram, campaigns rarely fail because of the creative alone - they fail because the algorithm is starved of clean, reliable conversion data, in the same way that a business advertising in the early '90s would be unable to tell which customers had been acquired after seeing an ad if the ad failed to carry the instruction to quote a specific word or phrase.

‍

Nowadays, thanks to constantly evolving privacy laws, successful tracking and attribution with Meta ad campaigns is best done with a three-layer approach:

‍

Layer 1: The Browser Pixel (The Front-Line Observer)

‍

The traditional Meta Pixel is a snippet of JavaScript running directly inside the supporter’s web browser (Chrome, Safari, Edge etc).

• How it works: When someone lands on your appeal page or clicks "Donate", the pixel immediately reports the action back to Meta'

• The strength: It tracks front-end user intent in real time - scroll depth, page views, and button clicks;

• The pitfall: It is fragile. Ad blockers, cookie consent rejections, and mobile privacy protections (such as Apple’s Safari ITP) routinely intercept and block these scripts. If a charity relies solely on the browser pixel, it typically loses visibility on 20% to 40% of donation actions.

Layer 2: Server-Side Tracking via Conversions API (The Secure Relay)

‍

Server-side tracking removes the browser as the middleman between your website and Meta. Platforms like Stape provide dedicated, affordable hosting to create this bridge.

• How it works: When a supporter donates, their browser sends that transaction data to your charity's own cloud server (running on a first-party subdomain, such as data.yourcharity.org). Your server then packages that event and sends it directly to Meta via an encrypted, server-to-server connection known as the Conversions API (CAPI);

• The strength: Because the data flows through your own server first, it bypasses ad blockers, respects browser privacy restrictions, and ensures that immediate web checkouts are captured with near 100% reliability;

• How it plays with Layer 1 (Deduplication): You don't turn off the browser pixel when you turn on server-side tracking; you run both simultaneously. By attaching a shared, unique identifier called an event_id to both the browser ping and the server ping, Meta automatically deduplicates them. If both fire, Meta merges them into a single, high-fidelity conversion without double-counting your donations.

Layer 3: Offline & CRM Feeds (The True Value Engine)

‍

While server-side tracking (Layer 2) captures immediate card transactions that take place on your website, it cannot track what happens after the browser tab is closed. This is where your CRM - like Donorfy or Beacon - becomes an attribution powerhouse.

• How it works: When offline or delayed revenue occurs, your CRM pushes the transaction details directly to Meta’s Offline Conversions / CAPI endpoint using hashed identifiers (SHA-256 encrypted email, phone, name, and postcode) along with the original ad click data (fbclid);

• Why it matters for charities:
  • Direct Debits & Recurring Gifts: When a supporter signs up for a £10/month regular gift, the website checkout only captures the initial mandate setup (often recorded as £0). The actual donations clear days or weeks later inside the CRM;‍
  • Gift Aid Claims: Offline feeds can update Meta with the additional 25% Gift Aid reclaim once eligibility is confirmed;‍
  • Failed Payments & Cancellations: If a Direct Debit bounces or is cancelled within 14 days, the CRM knows, preventing you from spending ad budget optimising for phantom donors.

The Power of the Triple Layer

‍

Meta requires hashed customer parameters (SHA-256 encrypted email, phone, name, and postcode) alongside technical identifiers (ffbclid and _fbp) to match an offline gift to the user who clicked your ad.

‍

When all three layers operate together, they create a complete feedback loop:

1. The Pixel captures immediate engagement and intent on the page;
2. The Server (Stape/sGTM) guarantees that immediate online donations are recorded without loss from ad blockers or cookie restrictions;
3. The CRM (Beacon/Donorfy) feeds recurring payments and actual lifetime value back to Meta weeks down the line.

With this full picture, you are no longer forcing Meta to optimise for cheap £3 one-off clicks. Instead, you can train Meta’s bidding algorithms to seek out supporters who reliably generate long-term recurring revenue for your cause.

‍

‍

So, Which Is The Best Charity CRM If You're Running Ads On Facebook, Donorfy or Beacon?

‍

They both do it very differently, so let's take a look at the core similarities and differences when it comes to the fundamentals of successfully attributing conversions with signals sent to Meta CAPI from your CRM.

‍

Capturing Ad Parameters at the Point of Donation

‍

Before a CRM can pass data to Meta CAPI, it must first capture the user's ad context (UTMs, fbclid, and _fbp cookie values) when they land on your donation page.

‍

Beacon CRM

‍

Beacon offers a streamlined native form builder that can be embedded directly onto your website via standard code snippets or hosted on a standalone subdomain.  

• Hidden Field Ingestion: Beacon forms natively parse URL parameters. You can add custom text fields to your database (e.g., Meta Click ID, UTM Source, UTM Campaign) and map them directly to incoming URL queries without writing custom JavaScript;

• Front-End Data Layer: When a supporter donates via an embedded Beacon form, it pushes a standard purchase event directly to the browser window’s Google Tag Manager (GTM) data layer. This allows you to generate a unique event_id client-side, store it against the payment record, and use it for server-side deduplication.  

Donorfy

‍

Donorfy approaches data capture primarily through Donorfy Web Widgets or custom forms communicating via its REST API.  

• Widget Tracking: Donorfy’s out-of-the-box donation widgets are primarily built to assign gifts to internal Campaign Codes and Funds. Passing dynamic, granular click identifiers like a 50-character fbclid string typically requires storing it in custom Constituent or Transaction attributes;

• Custom Form Requirement: Charities running high-volume paid acquisition with Donorfy often bypass the standard web widgets in favor of custom forms (e.g., WordPress/Gravity Forms or custom web apps) wired into the Donorfy API. This gives developers total control over capturing cookie data and browser headers before passing the payload into Donorfy.

‍

‍

Triggering Server-Side Events to Meta CAPI

‍

Once a donation or recurring gift record is created in the database, the CRM needs to send an event payload to Meta’s Graph API endpoint.

‍

Beacon CRM: Native Workflows & Verified Zapier App

‍

Beacon features a visual Workflows engine and an official, verified Zapier integration.  

• Ease of Deployment: Within Beacon, you can set an automated action to "Trigger a Zap" whenever a new payment record is created;

• Payload Richness: Beacon automatically bundles the payment amount, constituent contact details, and custom fields (including any captured fbclid) into the Zapier trigger payload;

• CAPI Routing: In Zapier, you can pipe this directly to Meta’s native Conversions API integration with minimal transformation, automatically hashing supporter emails and names into SHA-256 before transmission.

Donorfy: Automation Triggers & REST API

‍

Donorfy uses an automation feature called Triggers alongside a comprehensive REST API.  

• Automation Mechanism: Under Data Management > Triggers, you can configure rules (e.g., When a new Transaction is created where Amount > 0) to execute an HTTP POST webhook;

• Middleware Overhead: Because Donorfy does not rely on a fully managed public Zapier action app in the same way, connecting it to CAPI usually involves using a custom webhook in Zapier, or other software to act as a bridge;

• Developer Flexibility: For organisations with in-house technical resources or technical agency partners, Donorfy’s REST API is thoroughly documented, making it straightforward to build robust back-end workers that queue and post batched offline transactions to Meta

‍

Recurring Giving & Long-Term Donor Value Attribution

‍

For most charities, the real payoff with paid social isn't a single £10 one-off gift; it is acquiring a regular giver with an average lifetime value of hundreds of pounds.

• Donorfy's Strength in Recurring Gifts: Donorfy was engineered specifically around the UK fundraising financial cycle, including native management of Recurring Payment Instructions (RPIs) for direct debits (via GoCardless) and automated Gift Aid reclaim schedules. When a subsequent monthly payment clears 30 or 60 days later, Donorfy records that transaction on the constituent timeline. If the constituent record holds the original ad attribution parameters, you can fire offline CAPI events for monthly renewals, enabling Value-Based Bidding in Meta Ads Manager;

• Beacon's Strength in Lifecycle Attribution: Because Beacon's relational data model allows you to easily connect People, Payments, Subscriptions, and Custom Objects, you can construct workflows that fire different CAPI events depending on donor status. For example, you can tell Meta when a supporter completes an initial donation versus when their subscription successfully executes its third continuous payment.

A word of caution at this point: if not done correctly, you can inadvertently send Meta duplicated histories of what are meant to be unique transactions. This double-counting makes its algorithm think it's twice as successful as it really is, and halves the Cost per Acquisition (CPA) you'll see reported - leading to poor decisions about budget allocation based on an overly optimistic understanding of performance.

‍

Choosing the Right Fit for Your Paid Social Strategy: Donorfy or Beacon CRM

‍

If your charity prioritises speed, ease of iteration, and an out-of-the-box user journey where marketing teams can map custom tracking fields into forms and push data to Zapier without writing code, Beacon CRM provides the lower barrier to entry. Its native data layer events and flexible form fields drastically reduce the friction of implementing client-plus-server conversion deduplication.

‍

If your organisation operates an established, finance-led fundraising model that handles high-volume direct debits, complex gift-aid accounting, and custom web frontends, Donorfy offers exceptional backend financial rigor. While connecting it to Meta CAPI requires more upfront developer or agency setup, its API-first structure makes it a resilient backend for enterprise-grade offline conversion attribution.  

‍

Our Experience of Using Both Donorfy and Beacon CRM With Clients

‍

The Beacon CRM User Interface is much more pleasing and easier to navigate, and it's clear that it's been developed with greater readiness for a role in the broader promotional marketing and fundraising activities of its users. Donorfy looks very outdated these days by comparison, and feels clunky. Not only that, but there's no way to get URL query string parameters like the all-important fbclid and _fbp into the form and therefore into the donor's Transaction and Constituent records, which suggests that it wasn't built for a world in which donors are recruited through paid ad campaigns online and on social media.

‍

Donorfy's API capabilities are excellent, and its documention is comprehensive, but when we needed support with it they tried to hand us off to a commercial partner which would have seen our client have to pay a consultancy fee. It also has an annoying habit of double-reporting individual one-off donations - in our Zapier flows, we filter for 'TransactionAdd' events only, which should only happen once per donation, but the way Donorfy's connection with payment gateways like Stripe seems to work leads to every single donation triggering two webhook POST events, which is really frustrating and it's not easy to prevent the duplicates being fired off to Meta CAPI.

‍

If we had to pick an overall winner, it would probably be Beacon CRM.

‍

Unlock Better Return on Ad Spend with Server-Side Tracking

‍

Bridging the gap between your CRM and Meta’s advertising engine is the single most effective way to lower your cost-per-donor and unlock automated value-based bidding.

‍

Whether your charity uses Donorfy, Beacon, or an external giving platform, our paid social team specialises in building end-to-end tracking infrastructure, get in touch and start a conversation about improving attribution and optimisation today.

‍