Campaigns
brands post, clippers submit, the ledger records.

01The ledger principle

That is a deliberate design: you run the programme and stay in control of how and when money moves, and of the legal and tax duties that come with paying people. Nothing in the app or in this documentation promises a clipper views or income; amounts shown before approval are labelled as estimates.

02Who does what

03Switch it on: console settings

Console, Money, Campaigns (src/server/campaigns/settings.ts):

The picture is from a demo with the switch on. A new install has it off.

Then give the right plans the "Create campaigns" limit (Plans), and add the view-counting keys below.

04For the brand: creating a campaign

In the app, Campaigns, a workspace owner creates a campaign as a draft:

Activating the campaign freezes its terms: rate, flat fee, minimum views, per-clip maximum, currency, platforms, access and rules cannot change afterwards. Title, brief, links, a later end date and the budget stay editable. A campaign can be paused (no new joins or submissions; tracking continues), ended (submitted clips are tracked to the end of their window and approved ones are still owed) and archived once nothing is open.

The budget, what is reserved and what is paid are visible to clippers on purpose: nobody should post into an empty pool.

05For the clipper: accounts, joining, submitting

1. Link an account On the Accounts page add a platform and a handle. The app shows a short code to put into the channel description or bio. YouTube and Twitch accounts are verified by reading that code through their official APIs. Other platforms are verified by a screenshot that the operator reviews (or by the optional profile-page read).
2. Join a campaign Open ones at once; application ones after the brand approves; invite ones with the link.
3. Post and submit Post the clip on the linked account, then submit the link of the post. One post can be submitted to a campaign once.
4. Follow it Each submission shows its views, the counted views, which requirements pass, the fraud score with its signals, and what it earned. "Counted views can be lower than the platform shows" comes with the reasons.
5. Earnings The Earnings page shows balances net of commission: in hold, paused, payable, in a batch, paid, each payout with its reference. The clipper enters where to be paid (a short text, for example a payment address); only whoever records payments sees it.

A rejection always names a rule of the campaign. A clipper may appeal a rejection once; the operator decides the appeal.

06How views are counted

On automatic platforms views are read hourly for the first 48 hours after submission, then daily, until the tracking window ends. The status check "Campaign views can be counted automatically" tells you which of the two are set up; without either key every count needs a screenshot and a reviewer.

Get a YouTube Data API key

1. Project In the Google Cloud console create or pick a project.
2. Enable the API APIs & Services, Library, YouTube Data API v3, Enable.
3. Create the key APIs & Services, Credentials, Create credentials, API key. Restrict it to the YouTube Data API v3.
4. Paste it Console, System, Integrations, "YouTube Data API key".

Get Twitch app keys

1. Register At dev.twitch.tv/console, Applications, Register Your Application.
2. Copy the Client ID into Console, Product, Imports, "Twitch app client ID".
3. Secret Create a client secret and paste it into Console, System, Integrations, "Twitch app client secret".

07How an amount is worked out

per-view part  = 0 while counted views < minimum views,
                 else the smaller of: per-clip maximum, counted views × rate ÷ 1000
earned (gross) = flat fee + per-view part, never more than what was reserved for the clip
commission     = gross × your commission, at the rate in force when the payout row is written
net            = gross − commission   (what the clipper is owed)

• When a clip is approved, its possible maximum is reserved against the budget. If the budget is fully reserved, the clip cannot be approved until the brand raises the budget. The rule the ledger keeps: reserved + paid never exceeds the budget (src/server/campaigns/ledger.ts).
• Payout rows are written for the flat fee at approval, then for what the clip earned once per earning period, and a last time when the window ends or the clip reaches its maximum. Unused reservation returns to the budget.
• Each row becomes payable after the hold. A row that is marked paid is final.

Any rate you see in an example is an example. What clippers actually earn depends on the campaign's terms and on real views.

08The fraud score

Every tracked clip gets a score from 0 to 100, the sum of signals that everyone involved can see with their measured values (src/server/campaigns/fraud.ts):

A score at or above the threshold (60 by default) sets a flag. A flag pauses the clip's payouts until a reviewer or the operator looks. It never rejects a clip by itself. Clearing the flag lets the payout continue; the clip is flagged again only if its score rises 10 points above the cleared score. Rejecting needs a rule of the campaign, like any rejection.

The score is a set of simple checks on public numbers. It can be wrong in both directions; a person decides.

09For the operator: the three console pages

Only the operator can reverse an already approved clip, with a rule, and only its unpaid part.

10Paying clippers: batches, CSV, marking paid

1. Create a batch Console, Payouts, "Create a batch from what is payable" (for everything or for one campaign). It collects every payable row per clipper and currency. Balances under the smallest-balance setting wait.
2. Download the CSV It has each clipper's e-mail, their pay-to text, the amounts and the currency. Nothing in the app shows a clipper's e-mail to brands or other clippers.
3. Pay with your own provider (bank transfer, a payout service), outside Vodmill.
4. Record the reference Mark the batch paid with the reference of the payment you made (a bank transfer id, a payout batch id). Clippers see it. This cannot be undone.

A batch that was not paid can be cancelled; its rows become payable again. With "Campaign owners can mark payouts paid themselves" on, a brand owner can mark its own campaign's payable rows paid with a reference, and export its own CSV.

11Your commission

The commission is 0 until a console owner sets it. It is entered in basis points and can never be above 5000 (50 %): the cap is enforced in the console and again when the value is read, so a value written past the console is still capped (COMMISSION_CAP_BPS). Clippers and brands see the rate before they join. Each payout row stores the commission at the rate in force when the row was written, so a later change never alters old rows.

The ledger shows your commission as a figure next to every payout. Collecting it is part of how you settle with the brand outside the software.

12What to tell your users

• Clippers post on their own accounts and must follow each platform's rules, including its rules on disclosing paid or sponsored content.
• Views must be real. Bought or botted views break the standard rules of every campaign.
• Posts must stay public for the whole tracking window.
• Payments are made outside the app; the app shows what is owed and what was recorded as paid.
• Nothing promises views, reach or income.