Planning comparisons, offers, credits and anchors

This article covers GiveCampus campaign administration. Available controls can vary between the classic and redesigned campaign interfaces.

• Percentage to goal is current amount/count divided by goal times 100, not percentage growth. A prior-year baseline of 100 and current result 120 displays 120%, representing 20% growth. Use the correct comparison year and equivalent scope. A display goal does not itself establish an automated year-over-year-growth challenge rule.
• Eligible active matches/challenges can be featured on child tiers when the current layout is enabled; the child gift filter determines eligible offers.
• Earned progress is not proof of cash collection/deposit. Online offers can trigger processor checkout, which can fail. Offline offers do not charge a card; their collection and allocation must be reconciled separately.
• Add the Alumni affiliation/class-year selector before payment and configure qualifying years for an offer. A “Young Alumni” label alone does not automatically populate graduation year.
• The shared Allow Matches and Challenges setting gates both ordinary donor offer flows. Administrative offline management is separate; donor offers are not all offline uploads. Do not recommend deleting existing donor offers as the default way to disable creation.
• The layout uses #campaign-matchallenges-section for its matching/challenge section. Append that fragment to the campaign URL and test the selected template.
• Campaign leaderboard donor participation uses campaign contributions, joint gifts, offline donor records and aggregate adjustments. A CRM connection does not provide a universal hard/soft-credit inclusion switch or equal treatment. Define the exact count and source records before promising that a leaderboard reproduces a CRM credit report.