Campaign
A public community program. It controls the published widget, voting rounds, contribution budget, and the recipients supporters can choose.
Core concepts
Both belong to a workspace, but they solve different problems. They connect only when an identified supporter completes verified activity.
A workspace can publish several campaigns and create several developer projects without pairing them one to one.
A public community program. It controls the published widget, voting rounds, contribution budget, and the recipients supporters can choose.
An integration boundary. It owns API keys, browser origins, external user identities, entitlement rules, and webhook endpoints.
Your customer inside one developer project, identified by the stable external user ID supplied by your server.
A stable product-facing key and its current state. Rules decide when a supporter earns it; your application decides what it unlocks.
The developer project is attached at runtime through the supporter identity token—not through a permanent campaign setting.
donation.completed event in the project that issued the token.Campaign widgets automatically record verified, identified PayPal donations. For trusted activity that happens elsewhere, your server can send POST /api/v1/events directly to a developer project. Those events can evaluate the same project-scoped entitlement rules without involving a campaign.