Pay creators a percentage of net value

Right now, a conversion payout can pay a creator in two ways: a flat amount for each conversion, like $5 for every signup, or a percentage of the conversion's value, like 10% of every order. That works when the order total is the number you care about. Often it isn't. A $49.99 order placed with a discount code, minus card fees and the cost of the product, might leave you with $31.

Starting today, a conversion payout can also pay a percentage of net value. Your backend sends what you kept from each conversion, and trackagoat pays each creator their share of that number. This way a creator's payout follows what the sale was actually worth to you, not what the customer was charged.

How it works

1. Send the net value with each conversion. When your backend records a conversion, add one field, net_value_cents, next to the value_cents you already send.
2. Pick % of net value on the payout structure. In a conversion payout structure, each event gets a rate. Under Pays, choose % of net value and enter the percentage.
3. trackagoat adds it up. Every conversion of that event earns the creator their percentage of its net value, on the structure's cadence: as soon as each conversion arrives, or rolled up daily, weekly or monthly.

The conversion call looks like this:

{
  "conversion_event_key": "purchase",
  "platform": "tiktok",
  "handle": "creator_handle",
  "value_cents": 4999,
  "net_value_cents": 3100,
  "external_id": "order_10021"
}

Nothing else about recording conversions changes. If you never send a net value, everything works exactly as it did before.

A worked example

Say you pay creators 25% of net value on the purchase event, rolled up monthly. One creator drives three orders in October:

Order	Charged	Net value sent	Quantity	Earns
A	$49.99	$31.00	1	$7.75
B	$20.00 each	$12.00 each	2	$6.00
C	$49.99	not sent	1	$0.00

At the end of October that creator has one payout line of $13.75. Order B shows that net value works like the order value: it's per unit, so it's multiplied by the quantity. Order C shows the one thing to watch for: a conversion sent without a net value still counts as a conversion, but it pays nothing on a net value rate.

Rates are set per event, so one structure can mix them. You could pay $5 for every signup and 25% of net value on every purchase, and creators see both in one place.

What counts as net value

You decide, because only your backend knows your fees and costs. Common choices are the order total minus discounts, payment fees, the cost of goods, shipping, or an app store's cut. trackagoat stores the number exactly as you send it.

A few rules keep the numbers trustworthy:

• It's optional, with no default. Nothing is ever guessed: a conversion sent without one simply has no net value.
• It can't be negative. An order you lost money on has a net value of 0.
• It's fixed once recorded, like every other conversion field. To fix a wrong one, void the conversion and record it again with a new external_id. Voiding reverses any unpaid payout the conversion produced, so a refund or a correction never leaves a creator overpaid.
• Rates top out at 100%, so a creator is never paid more than the net value itself.

Making sure nothing pays $0 by accident

The easy mistake with net value is an integration that sends it for some conversions and forgets it on others. Those conversions pay nothing, and nobody notices until a creator asks why their payout is low. So trackagoat shows you how much of your data carries a net value, everywhere it matters:

• When you set the rate. Pick % of net value for an event and the form tells you how many of that event's conversions in the last 30 days arrived with a net value.
• On the payout structure. Conversion structures now list every rate in words, such as "Purchase: 25% of net value", and warn when recent conversions of a net value event came in without one.
• Under Manage events. A new Net value sent column shows, for every event, how many of the last 30 days' conversions carried a net value.
• On each conversion. The detail panel shows its net value, or says it wasn't sent.

The 30-day window is deliberate. If you fix your integration today, the warnings clear as new conversions arrive, instead of reminding you about old ones forever.

Net value on the Conversions page

Once your backend starts sending net values, they show up next to the order values you already see:

• a Net value tile, with how many conversions it covers;
• a new Value over time chart, with value and net value side by side;
• the top creators panel can rank by net value instead of value;
• each creator, account and video page shows net value totals on its Conversions tab.

None of this appears until at least one conversion has a net value, so if you don't use it, nothing changes.

For agents and the API

Everything here works through the API and the MCP server, so an agent can set it up and keep an eye on it for you:

• record_conversions and POST .../conversions accept net_value_cents.
• The conversion summary, leaderboard and daily series return total_net_value_cents and net_value_count, and the leaderboard takes sort=net_value.
• list_conversion_events returns how many recent conversions of each event carried a net value.
• In a payout structure, the new rate is rate_type: "net_percent".

A few things you can ask an agent connected to trackagoat:

Change the Spring payout structure to pay 25% of net value on purchases instead of 10% of value.

Is our backend sending net value on every purchase this month?

Who were our top 10 creators by net value in September?

Read more

• Paying a percentage of net value: how the rate works, with examples.
• Net value: what to send and the rules it follows.
• Conversions API reference: the field, and the usage counts on conversion events.
• Aggregate API: net value in the summary, leaderboard and daily series.