Our Current Setup:
- Source: We run two separate WordPress sites using the Charitable plugin.
- Site 1: General day-to-day donations.
- Site 2: Dedicated to our flagship event.
- Middleware: We use a single Zapier Zap that "listens" to both sites and creates an Opportunity in Salesforce whenever a donation is processed.
- CRM: Salesforce Nonprofit Success Pack (NPSP).
Currently, all donations land in Salesforce looking the same. I want to specifically identify the events donations so that they are named consistently, with the event title in each Opportunities name. Then I can associate them all with a Campaign.
We don't have a direct integration from our wordpress to Salesforce. We use Zapier to upload donations from Stripe to SF. At the moment, it's one Zap that feeds opportunities into SF and SF names the opportunity based on the NPSP settings (standard). As I say, we use a whole other wordpress site for processing the events donations, so it should be easy enough... Is there something I can do with the website API, or is it something for Zapier, or a flow, or is there actually something much easier... Any suggestions will be helpful! Thanks you
Great question Jake, and both Vishal and Steven have covered the core of it well. To add a bit more structure:
Agreeing with Vishal - adding a Zapier formatter or filter step to detect the source site and set a custom Opportunity Name is the cleanest lightweight fix. His suggested naming convention ("Flagship Event - Donor Name - Donation Date") is exactly the kind of pattern that makes reporting and data hygiene much easier down the line.
Agreeing with Steven
- if your end goal is Campaign association, skip the naming workaround entirely and have Zapier directly populate the CampaignId field on the Opportunity at the point of creation. Since you already know the source (the separate WordPress site), you don't need conditional logic — you can hardcode the Campaign ID for event donations in that Zap branch.
Since you're on NPSP, make sure you are populating the Primary Campaign Source field on the Opportunity, not just a custom campaign field - It should keep your donation attribution clean.
Also consider adding a custom picklist field like Donation Source (General / Flagship Event) on the Opportunity which will give you a reliable filter for reports and list views independent of the Opportunity Name, which can drift over time.
If you would ever want to scale beyond two sites, splitting into two separate Zaps (one per WordPress site) makes the logic far easier to maintain than a single Zap with branching.
Hope this helps!
Vish (KVP Business Solutions)
