Use cases for Creators

A Creator publishes trackable distribution for a funded program and receives recognition and reporting for the accepted contributions attributed to it. If the program defines Creator compensation, the Sponsor funds it separately in Credits under the program terms. It is never taken from the Member reward pool. The Creator role remains separate from the community operator who holds venue authority inside a Space, even when one person holds both roles.

Decide whether a program is worth publishing

Scenario. A Creator is offered a place in a Sponsor-funded Campaign that a community is hosting.

Problem. A brief that names compensation but not the disclosure duty, the qualifying action, or the review rule leaves the Creator carrying a risk they never agreed to.

How ZYNC works. The program states its disclosure and content terms, the Missions it funds, what counts as an accepted contribution, and the window in which a result can be reversed — before the Creator opts in. Opting in is per program, so accepting one Campaign never enrolls a Creator in the next. See accept a program.

Expected outcome. The Creator can decline, negotiate, or accept against terms that are written down rather than implied.

Relevant capabilities. Per-program opt-in, disclosure and content terms, published verification rules, and versioned Campaign terms.

Next step. Work through the checklist in Accept a program.

Publish distribution that can be attributed

Scenario. The Creator publishes to its own audience and wants the resulting contributions counted as theirs.

Problem. When distribution cannot be traced, credit turns into an argument at the end of the Campaign.

How ZYNC works. The program issues trackable distribution the Creator publishes under the agreed disclosure. Accepted contributions that arrive through it are attributed to the Campaign, the Community, the Creator, and the referral path together, so every party reads the same record. Attribution reports what the network observed; it does not assert that the Creator caused the Sponsor’s wider growth. See publish and track.

Expected outcome. The Creator sees which accepted contributions its distribution is credited with, on the same evidence the Sponsor and Community see.

Relevant capabilities. Trackable distribution, reproducible attribution, and shared program reporting.

Next step. Read what a Creator can and cannot see in Publish and track.

Reconcile attribution, compensation, and corrections

Scenario. The Campaign produces results, some of which are held, rejected, or reversed.

Problem. Attribution or compensation that changes without explanation leaves a Creator unable to reconcile the program.

How ZYNC works. A held or rejected contribution is visible with its state and reason category. Any Creator compensation is a Sponsor-funded Credits term frozen with the program version before distribution begins, never a percentage of the Member reward pool. When a Creator believes a decision or attribution is wrong, the dispute path is stated in the program rather than improvised. See compensation, holds, and disputes.

Expected outcome. The Creator can reconcile what was published, accepted, held, corrected, and reported, plus any compensation settled under the program terms, and can challenge an error through a defined route.

Relevant capabilities. Frozen program terms, separate reward and fee treatment, contribution states, hold and reversal reasons, and Creator dispute handling.

Next step. Review Compensation, holds, and disputes.

Explore the details

• Creator overview
• One shared program lifecycle
• Campaigns and sponsorships