Core concepts

Campaigns run the program. Projects connect your product.

Both belong to a workspace, but they solve different problems. They connect only when an identified supporter completes verified activity.

The resource model

A workspace can publish several campaigns and create several developer projects without pairing them one to one.

Campaign

A public community program. It controls the published widget, voting rounds, contribution budget, and the recipients supporters can choose.

Developer project

An integration boundary. It owns API keys, browser origins, external user identities, entitlement rules, and webhook endpoints.

Supporter

Your customer inside one developer project, identified by the stable external user ID supplied by your server.

Entitlement

A stable product-facing key and its current state. Rules decide when a supporter earns it; your application decides what it unlocks.

How an identified campaign donation flows

The developer project is attached at runtime through the supporter identity token—not through a permanent campaign setting.

1

Your app identifies the supporter

Your server issues a short-lived identity token from one developer project.
2

The campaign widget accepts that identity

The campaign and project must share a workspace, and the embedding origin must be allowed by the project.
3

The supporter contributes to a campaign recipient

The donation remains associated with the campaign and selected recipient for payment and reporting.
4

Our Impact records a project event

After PayPal capture succeeds, the identified donation becomes a donation.completed event in the project that issued the token.
5

That project evaluates its rules

Only matching entitlement rules in that developer project update the supporter’s access.

What is—and is not—connected

Campaign → recipient DirectThe campaign defines which connected recipients appear in its widget.
Project → supporter DirectThe project owns the external identity namespace and supporter record.
Project → entitlement DirectDefinitions and earning rules are scoped to one project.
Campaign → project RuntimeThere is no permanent one-to-one link. A valid project identity joins them for one supporter session.

Events outside a campaign

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.