Campaigns
Last updated: June 1, 2026
Campaigns are how you organize, track, and report on your fundraising in WeGive. A campaign groups together the donations, supporters, messages, and giving activity tied to a specific initiative — whether that's an annual fund, a single appeal, or a major project — so you can see how it's performing in one place.
This guide walks through creating a campaign, the best practices that keep your reporting clean, how to attach a campaign to a checkout so donations are attributed to it, and what campaign members are.
Creating a Campaign
From Campaigns, click Create Campaign. You'll see the following fields:
Name (required)
The display name for your campaign. This is the only required field — everything else is optional and can be added later.
Parent campaign (optional)
Search for and select an existing campaign to nest this one underneath it. This builds a campaign hierarchy (see Parent and Child Campaigns below). Leave blank for a standalone or top-level campaign.
Goal (optional)
A dollar target for the campaign. This drives the progress bar you see on the campaign overview (for example, "$500 out of $100k — 1%"). It does not restrict giving; it's purely for tracking and display.
Start date / End date (optional)
The campaign's active window. These are informational dates for your own organization and reporting — they don't automatically open or close giving.
Siebel ID / CRM ID (optional)
A 6-character campaign code used to map this campaign to the matching record in your Siebel CRM. Fill this in if you sync campaigns with an external system so attribution flows through correctly.
Once you save, the campaign gets a slug (a URL-friendly version of the name, e.g. trauma-healing). The slug is generated for you and can be edited later from the campaign's settings.
Note: Name is the only field WeGive requires to create a campaign. Goal, dates, parent, and Siebel ID are all optional, so don't feel blocked if you don't have every detail yet — you can edit the campaign at any time.
Best Practices
Naming
Use clear, human-readable names that will still make sense months later in a report. "2026 Spring Appeal" is better than "Appeal 2." Consistency matters more than cleverness — pick a convention (year + initiative, or program + audience) and stick to it across campaigns.
Set a goal even if it's an estimate
The goal powers the progress indicator and gives your team a shared target. An approximate goal is more useful than no goal.
Use parent and child campaigns intentionally
Structure your hierarchy to match how you want to report, not just how you organize internally. A parent campaign automatically rolls up the giving from its children, so put broad initiatives at the top and specific appeals underneath (more below).
Fill in the Siebel/CRM ID if you sync
If your organization pushes data to the Siebel integration, set the CRM code at creation time. Backfilling attribution after donations have come in is far more painful than setting it up front.
One campaign per distinct initiative
Resist the urge to reuse a single campaign for everything. Separate campaigns keep your conversion, revenue, and member numbers meaningful. If two efforts share a theme but have different goals or audiences, make them separate child campaigns under a common parent.
Plan your tracking before you launch
Decide up front how donations will reach the campaign — which checkout, which UTM tags, which links — so your reporting is clean from day one. See the checkout and UTM sections below.
Parent and Child Campaigns
You can nest campaigns by setting a parent campaign. This creates a family tree: a parent campaign and all of its descendants.
When you view a parent campaign, WeGive can roll up the giving, members, and message activity from its child campaigns into the parent's numbers. On the campaign overview, you'll see a Child campaigns table listing each child along with its gross revenue, the rolled-up revenue, payments, members, and messages. Many of the analytics views (giving over time, checkout conversion, message performance, conversion funnel) have an "Include descendant campaigns" toggle that switches between showing just that campaign's data and the whole family's aggregated data.
A couple of rules to know:
A child campaign must belong to the same organization as its parent.
A campaign can't be its own parent (no circular references).
When to use this: Use a parent campaign for a broad initiative (e.g. "Year-End Giving") and child campaigns for the specific appeals, channels, or audiences within it (e.g. "Year-End — Email," "Year-End — Direct Mail"). You get granular numbers per child and a combined view at the parent.
Adding a Campaign to a Checkout (the Implement button)
To attribute donations from a checkout to a specific campaign, you use the Implement button. This generates a link, embed, or pop-up that ties that checkout to the campaign — so every gift made through it is aggregated into the campaign's totals.
How it works
Open the campaign (or the checkout element) and click Implement.
In the dialog, search for and select the campaign you want to attribute donations to.
Choose how you want to deliver the checkout:
Link to — a direct URL you can share anywhere.
Embed — an
<iframe>you drop into your website; the campaign URL is the iframe's source.Pop-up — a script snippet that opens the checkout in a modal.
Optionally expand UTM parameters to add source/medium/campaign/term/content tags for analytics.
Click Copy to grab the URL (or Download PNG to use the generated QR code).
What actually changes in the URL
Selecting a campaign appends the campaign as a query parameter to the checkout URL. The base path stays the same — the campaign is added on the end:
https://{org}.wegive.com/{org-slug}/checkout/{checkout-slug}?campaign={campaign-id}If you add UTM tags, those are appended as additional query parameters:
...?campaign={campaign-id}&utm_source=newsletter&utm_medium=email&utm_campaign=springWhen a donor opens that link, the checkout reads the campaign value from the URL and attaches it to their checkout session. Every donation made through that session is then attributed to the campaign and rolls into its reporting. The QR code encodes the same campaign-tagged URL, so scanned gifts are attributed too.
Key takeaway: It's the same checkout either way — adding a campaign doesn't create a new checkout. It just tags the URL so the giving lands in the right campaign. You can point multiple campaign-tagged links at one checkout and each will report separately.
Tip
Combine the campaign tag with UTM parameters when you're running the same checkout across multiple channels. The campaign tag gives you the rollup in WeGive; the UTMs let you see which channel (email vs. social vs. QR poster) drove each gift.
What Are Campaign Members?
A campaign member is the link between a supporter (donor) and a campaign — it records that a given person is affiliated with that campaign. You'll find them on the Members tab of any campaign, which shows a map of where members are located and a list of each member, the supporter's name, revenue, when they joined, and their last source.
How members are created
Automatically — when a supporter interacts with the campaign. This includes making a donation through a campaign-tagged checkout, but also setting up a recurring plan, making a pledge, submitting a form, engaging with a message, or going through a journey tied to the campaign. The first qualifying activity creates the membership; later activity updates it.
Manually — from Campaign Members → Create Campaign Member, where you choose the Campaign, the Supporter, and the Last source. This is useful for recording an affiliation that didn't come through an automated channel (for example, an offline gift or a contact you want associated with the campaign).
The "Last source" field
Each campaign member has a last source that records the most recent activity that tied that person to the campaign. Possible sources include:
Transaction — a donation/payment
Recurring plan / scheduled donation — a recurring gift setup
Pledge — a pledge
Form submission — a submitted form
Message — an interaction with a campaign message
Journey — participation in a donor journey
Fundraiser — peer-to-peer fundraiser activity
This tells you not just that someone is a member, but how they most recently engaged — useful for understanding which channels are bringing people into a campaign.
In short: Campaign members are the roster of people connected to a campaign. Most appear automatically as donations and activity flow in through your campaign-tagged checkouts and links; you can also add them by hand when you need to.
Quick Reference
Task | Where | Notes |
|---|---|---|
Create a campaign | Campaigns → Create Campaign | Only Name is required |
Nest under a parent | Parent campaign field | Same org; no self-parenting |
Set a target | Goal field | Drives the progress bar |
Map to CRM | Siebel ID / CRM ID | 6-character code |
Attribute a checkout | Implement button | Adds |
See the family rollup | "Include descendant campaigns" toggle | Aggregates child data |
View affiliated supporters | Members tab | Auto-created from activity, or add manually |