Conservation & Fieldwork·Guide
From support to evidence: designing honest attribution
Greenwashing research and nonprofit craft rarely share a page with fundraising ops. Channel attribution asks which click got credit for the gift. Impact frameworks ask whether outcomes are real. Conservation programs need a third distinction that sits between them: what you may claim after money moves, before anyone can prove a species recovered. That is honest attribution—commerce total, field allocation, allocation status, and verified outcome kept as separate words.
What this guide decides
Four terms you must not collapse
Raised
Campaign commerce total. It answers how much was contributed toward the ask. It does not prove survey spend.
Allocated
Impact Record line(s) toward conservation activity. Say “allocated toward [survey]” only when a line says so.
Completed
Allocation workflow state on the record. Progress of the attribution job—not “the habitat is fixed.”
Verified outcome
Outside this product claim. Observation counts and Evidence are activity/proof, not a substitute for impact evaluation.
Why this page exists
Fundraising ops usually means channel credit: last-touch, matchback, which landing page “caused” the gift. Impact and ESG language usually means outputs versus outcomes, additionality, and whether a result would have happened anyway. Conservation publishers get squeezed by both, plus a third risk: equating a campaign total with field spend, or equating field photos with a solved problem.
ArtInStack’s Attribute layer exists so you can show provenance from an economic action to conservation activity without inventing outcomes. This guide teaches the judgment. Click-path setup stays in Impact Records.
The chain you can actually teach
Keep the objects in job order:
A campaign may be associated with a survey for storytelling. That routing link is useful. It is not an Impact Record. Without an allocation line, the honest sentence is still “supported Campaign A, which is associated with Survey A”—not “funded Survey A.”
| Step | Object | What it answers |
|---|---|---|
| 1 | Campaign | What people are asked to support (commercial container) |
| 2 | Economic action | Paid gift, license, or attributed print sale |
| 3 | Impact Record + allocation | Authoritative provenance toward activity |
| 4 | Survey / field activity | Where conservation work and evidence live |
| 5 | Published Evidence | What visitors can check on the site |
Raised vs Allocated vs Completed vs Verified outcome
Raised is the campaign’s headline total. Donors and operators need it; it is still commerce language. Treating raised as survey spend is the first collapse.
Allocated is what Impact Records exist for: an amount pointed at one or more surveys (activity/evidence targets). In v1 that is usually one allocation line matching the attributed amount. Split lines and deeper deployment chains can come later; the honesty bar does not wait on them.
Completed (and sibling statuses such as Allocated or In progress) describe where the attribution workflow sits. Closing an allocation does not mean the conservation problem is solved. Do not publish status as if it were an outcome badge.
Verified outcome sits outside the claim this stack should make from money alone. Evidence of Impact can show dated, placed, identified fieldwork. That is proof of activity, not a causal impact evaluation, IRIS+ result, or “your gift saved N animals” counterfactual. If you need that bar, bring evaluation methods—do not ask the CMS to invent them from observation counts.
Copy you can defend
Safe when true: “Your gift supported {Campaign}.” Safe when an allocation line exists: “Allocated toward {Survey}.” Safe on Evidence pages: named dates, softened places, confirmed taxa, unfinished IDs left unfinished.
Unsafe: implying survey funding from campaign association alone; equating allocation Completed with habitat recovered; using activity totals as verified outcomes; shipping a charitable PDF or badge as if the seal were the product without the record underneath.
The product is connective tissue for provenance. It is not a replacement for third-party impact science.
Where sibling guides stop and this one starts
Evidence storytelling for skeptical donors owns proof craft before the ask. Fundraising for field sites owns the path from observation to donate without a second fundraising brand, plus map honesty while you ask. This page owns what you may claim after payment—and which words you must keep separate.
Ship only as far as the stack can substantiate today: gift → Impact Record → survey allocation → activity and Evidence visitors can check. Deeper “this dollar funded Deployment #17” chains are a later honesty problem, not a reason to overclaim now.
What to avoid
Collapsing Raised, Allocated, Completed, and Verified outcome into one triumphant sentence on a program page.
Writing a “What are Impact Records?” explainer that skips the judgment and only lists UI fields.
Marketing undeployed allocation depth (per-observation micro-splits, automatic outcome scoring) as if it were live.
Using Impact Record surfaces (email, private impact page) to imply tax status, seals, or evaluated outcomes the organization has not separately earned.
Attribute what you can prove
Wire the ask beside Evidence, allocate gifts toward surveys you can substantiate, and keep outcome language for evaluation work that sits outside the CMS total.
Also in Guides: Fundraising for field sites · Evidence storytelling for skeptical donors · Field conservation’s two stacks