Set Up Impact Numbers & Cards

Last updated: July 22, 2026

Impact cards turn a supporter's giving into a tangible result — "You provided 120 meals" or "Your gifts planted 45 trees." They appear on a supporter's profile so people can see the difference they've made.

This guide walks through creating an impact card, choosing between static and dynamic types, targeting the right audience, and publishing.

Before you start

  • Static vs. dynamic. A static card shows the same value to everyone. A dynamic card calculates a personalized value for each supporter by dividing their total contributed amount by the number you set. Decide which fits before you begin.

  • Audience. By default a card will apply broadly to all supporters, but you can use audience rules to show it only to supporters who match conditions you define (e.g., donors who gave over a certain amount).

  • Draft first. Cards are unpublished by default, so you can build and review before anything goes live. If you select 'Set Live' on the Impact Card builder, the card will publish.

Create an impact card

  1. Go to Impact Cards and click Create Impact Card.

  2. Fill in the fields described below.

  3. Click Review details, then save.

Type

Choose Static or Dynamic.

  • Static — the card displays the exact value you enter, the same for every supporter. Use this for a fixed organizational number ("We served 10,000 meals this year").

  • Dynamic — the card divides each supporter's total contributed amount by the number you enter and rounds the result, so every supporter sees a value personalized to their giving.

How the dynamic math works: If a supporter has contributed $600 and you set the impact number to 25 (meaning "$25 provides one meal"), the card shows 24 — that is, 600 ÷ 25, rounded. The number you enter is the cost per unit of impact, not the result.

Name

The label shown on the card (required). This is the text supporters read, such as "Meals provided" or "Trees planted."

Type the @ symbol to insert contextual data into the name. This pulls in dynamic values (like the supporter's name or other merge fields) so the card reads naturally for each person. Use this when you want the wording itself to personalize, not just the number.

Number

The impact value (required). What you enter depends on the type:

  • Static card — enter the literal number to display (e.g., 10000).

  • Dynamic card — enter the cost of one unit of impact (e.g., 25 if $25 = one meal). WeGive divides each supporter's total giving by this number.

URL

An optional link for the card — for example, a page explaining the program behind the number.

Note: The URL only applies to static cards. If you switch the card to dynamic, the URL is not saved.

Start Date / End Date

Optional. Use these to scope the card to a specific time window, such as a single campaign or fiscal year. Leave blank for an always-on card.

Include On Organization

When turned on, the card is associated at the organization level rather than only on individual supporter profiles. Leave off if the card is meant purely for individual supporter views.

Published

This toggle is labeled Set Live — enable it to publish the card immediately when you save. Leave it off to keep the card as a draft while you finish building it.

What publishing triggers: When you publish a card, WeGive checks your audience rules and tags every existing supporter who matches, so the card starts showing up for the right people. Until a card is published, it stays hidden from supporters.

Audience Rules (segmentation)

Audience rules control which supporters see the card. If you add no rules, all supporters are in the audience. When you add rules, only supporters who match will be tagged and shown the card.

Rules are organized into groups. Each group holds one or more individual rules, and you decide how groups and rules combine.

Add a group and a rule

  1. Under Audience Rule Groups, click Add Group.

  2. Click Add Rule inside the group.

  3. In the Select Rule dialog, search for and pick a field — supporter data such as Full Name, Preferred Email, Type, phone fields, and many more.

  4. Choose a comparator (for example, is, is not, contains, greater than — the available options depend on the field).

  5. Enter the value to match against. Some comparators (like is set / is empty) need no value.

Add more rules to a group with Add Rule, and add more groups with Add Group.

How rules and groups combine

There are two levels of logic:

  • Within a group — rules combine to define one segment (for example, "Type is Individual" AND "gave more than $100").

  • Across groups — a dropdown at the top sets how the groups combine:

    • Match all groups (AND) — a supporter must satisfy every group to see the card.

    • Match any groups (OR) — a supporter who satisfies at least one group sees the card.

Use multiple groups with OR when you want to reach several distinct segments with the same card (e.g., "major donors" OR "monthly donors").

Preview your audience

As you build rules, WeGive shows a live count: "Preview [N] people that are in your audience now." Click it to confirm you're reaching the group you intended before publishing. If the count is 0 or far from what you expect, revisit your comparators and values.

Rule Tinker (test your logic)

Click the gear / Rule Tinker icon next to Audience Rule Groups to open a sandbox where you can:

  • Review the current rule logic and see how the groups combine.

  • Use the Truth Table to toggle rule values and watch how different combinations change the outcome.

  • Add Test Case to check specific scenarios.

This is the safest way to confirm complex AND/OR logic does what you intend before the card goes live.

Best practices

  • Start as a draft, preview, then publish. Build the card with Set Live off, confirm the audience count looks right, then enable publishing. This avoids surfacing a half-finished card or an unintended audience.

  • For dynamic cards, enter the cost per unit — not the result. The most common mistake is entering the total impact instead of the unit cost. Remember: WeGive divides the supporter's giving by this number.

  • Keep names supporter-friendly. Write the name as the supporter should read it ("Meals provided"), and use @ contextual data only where personalization genuinely helps.

  • Use date ranges for campaign-specific cards. Scope seasonal or campaign numbers with Start/End dates so old cards retire automatically.

  • Test complex segments in Rule Tinker. Any time you mix AND and OR across multiple groups, validate with the Truth Table before publishing.

  • Watch the audience preview count. A count of 0, or a surprisingly large/small number, almost always means a comparator or value needs fixing.

  • Use OR groups to combine segments. Rather than building separate cards for similar audiences, group distinct segments under "Match any groups (OR)."

Examples

Example 1 — Static organizational number

A nonprofit wants every supporter to see the same headline figure.

  • Type: Static

  • Name: Meals served in 2026

  • Number: 10000

  • Published: On

Every supporter sees "10,000 — Meals served in 2026."

Example 2 — Dynamic, personalized impact

A food bank wants each supporter to see how many meals their giving provided, where $25 funds one meal.

  • Type: Dynamic

  • Name: Meals you provided

  • Number: 25

  • Published: On

A supporter who has given $500 sees "20 — Meals you provided" (500 ÷ 25). A supporter who has given $1,000 sees "40."