Build a creator campaign KPI report around one row per creator for the same period and currency. Show accepted deliverables, attributed sales after eligible reversals, spend and new customers, then calculate ratios with the denominator visible.
What belongs in the first table?
Put the campaign period, cutoff and attribution rule above the creator rows. Use gross merchandise, discounts and eligible reversal amounts to make return-adjusted revenue traceable. Shopify’s sales report definitions can help map these fields from an export. Shopify sales reports
How do you calculate CAC and ROAS?
Creator customer acquisition cost, or CAC, is the chosen acquisition spend divided by attributed new customers. Return on ad spend, or ROAS, divides the revenue attributed to paid media by the corresponding ad spend. A program-wide revenue-to-cost ratio can include creator fees, commission and paid media when you label it separately.
Fictional example. Spend excludes gifts and product costs here. Paid-media revenue is a subset of net attributed sales, assigned separately under the report’s media rule.
| Creator | Accepted assets | Fees + commission + ads | Net sales | New customers | CAC | Net sales / spend |
|---|---|---|---|---|---|---|
| A | 2 | $400 + $60 + $140 = $600 | $1,200 | 8 | $75 | 2.0× |
| B | 1 | $300 + $0 + $0 = $300 | $0 | 0 | Undefined | 0× |
| Total | 3 | $900 | $1,200 | 8 | $112.50 | 1.33× |
If A’s $140 ad spend has $420 in net sales assigned to paid media, the corresponding ROAS is 3.0×. The $1,200 includes other sales and belongs in the broader program ratio.
What decisions can the report support?
- Have marketing verify deliverables and attribution. Use the same model and settings if you compare periods. Google Analytics attribution
- Have finance verify net sales, commission and the cutoff. Investigate blank or zero denominators before interpreting them.
- Document the action supported by the report, such as commissioning a second asset or investigating a missing signal. Use a holdout when the decision depends on causal lift.
If the next wave changes from a flat fee to commission, show the revised spend assumptions next to the old ones.
Build the first snapshot in the creator KPI worksheet.
Build the report around three different audiences
Production needs to see what shipped and what still requires a decision. Marketing needs to see credited orders, revenue and creative signals. Finance needs to know what became payable and where the number came from. Give all three teams a shared creator identifier and period. Preserve the exact deliverable and order-related evidence in detail rows. The summary can show numbers each group can tie back to those rows.
Agree on who owns the current figures. The production lead can approve the accepted count. The analyst can verify deduplication, attribution window and status of order adjustments. Finance can approve the cash-facing ledger and determine what expenses go in each cost measure. When all three see a different artifact, make the shared campaign and cutoff visible on every tab.
Track the accepted deliverable, eligible sale and payment separately
A creator can publish two videos, generate four paid orders and have one payment pending. These describe three different decision points. Record the accepted count from the approval package, eligible sales from source order records and actual cash movement from transfer evidence. The paid outcome for one account or program can lag the performance window by weeks. Keep forecast, approved obligation and paid status in separate columns.
Fictional handoff. A $400 asset fee is approved. Later, a post produces $1,200 of net attributed sales, including $420 assigned to paid media. The program accrued $60 of commission and paid $140 to run ads. Make it easy for a reviewer to reproduce both $1,200 ÷ $600 and $420 ÷ $140. If the ad report includes revenue for the same orders, check whether your attribution rule allows that figure as a subset or requires deduplication. A seller can report the same purchase in more than one surface.
Give denominators and exceptions their own rows
A campaign with 8 reported first-time customers and 15 orders has two possible denominators. CAC should use the qualifying new customer count rather than orders in this example. Include how you identify the first order when storefront or identity records are available. If the evidence doesn’t distinguish a subset of customers reliably, log it. If no qualifying new customers were counted, the ratio is undefined. That row still matters because the expense belongs in the summary.
Keep separate labels for cutoffs and revenue definitions. A snapshot showing some returns may revise later. A paid attribution report may use its own time window and conversion rules. Show the March paid figure under the March definition, with a link to the configuration if the reader needs to investigate. When a definition changes, preserve the original and use a comparison that flags the change.
Check the close from the bottom up
Select two detail rows and tie each to the native source. Verify creator, amount, currency and reporting period. Compare eligible merchandise and return treatment across the export and statement. Confirm that store shipping and tax appear only in the intended measures. If an older return changed the net number, record the adjustment in the current processing period and point back to the original sale. Retain an as-of version so reopening reports doesn’t erase the original close.
Give management one view of confirmed totals and one short list of decisions the figures support. Production can commission another approved variant. Marketing can investigate whether a missing click signal affects several creators. Finance can reopen an approval when a verified refund changes eligible commission. If they ask whether the campaigns caused incremental orders, describe the evidence from a controlled holdout test separately.
Design the next report before changing campaign terms
Changes in rates, shipping costs, offer mix, return windows and paid media affect the comparability of reports. When a campaign grows, give each version of the terms a date and owner. The revised report can still use the same metrics while showing the effect on spend and eligibility. Save sample rows that catch common errors, such as a zero denominator and a commission reversal. Run them after editing a formula or changing the data source.
Decide who the report is for before choosing metrics
A weekly report is useful when it helps a team take a decision in that week. A finance statement is useful when the team can reproduce the obligation and trace the transfer. A campaign performance review needs enough context to compare results across creators or campaigns. A good reporting model lets people start from the same records and see a different view of the work depending on their task.
Write the decision directly above the scorecard. “Decide which two creators receive a second brief” leads to a different set of measures than “approve commission for orders paid before Friday.” Put creator relevance, expected deliverables and available capacity next to a rebooking decision. Review eligible orders, adjustments and obligations for the release decision. If the report will drive both, use a shared opening summary and include links to the relevant supporting tables.
Describe the interval and the cutoff in language a reader can distinguish. Interval means the activity dates the view covers. Cutoff means the latest observed data included in it. A report for April can include reversals that arrive in May if the report describes that April cohort as of a May close. A May processing report can instead show only the reversals processed in May. Both can be useful. Label the views explicitly and let finance choose the appropriate record for its purpose.
Match decisions to evidence
| Reader’s decision | Primary evidence | Start with this question |
|---|---|---|
| Commission another packing demonstration | Approved assets and audience evidence | Which use case and format were delivered, and can the reviewer repeat the test? |
| Adjust paid amplification | Attributed paid revenue and corresponding ad spend | Is the paid revenue assigned under comparable account settings and dates? |
| Review a return | Order line, adjustments and effective rate | Which eligible merchandise changed and when did the change enter the statement? |
| Release a creator payment | Approved draw and current payment readiness | Can the reviewer match the version, obligation and payee? |
| Increase program budget | Spend, operational constraints and causal evidence where needed | Can the team separate changes in execution from the effect it wants to fund? |
Set a definition for each row
Start with a creator-by-campaign-by-period readout and keep the detail at its appropriate unit. A deliverable can have several drafts. An order can have several click or code signals. A refund can contain several merchandise or non-merchandise adjustments. A payment can settle in several transfers. Joining all of those raw rows at once can multiply the amounts or counts. Group them separately and join the totals, then let reviewers open the evidence appropriate to each figure.
A practical content record starts with a campaign ID, creator ID, deliverable ID and approved asset version. A credit determination starts with campaign, order, point of credit and applicable rule. An adjustment carries the original order or line ID, an event ID and the applicable sign. A payout instruction stays linked to the approval it executed. Keep the identifiers on every exported dataset that may need to survive a handoff. Names and date labels help humans read the file, but the join should use stable IDs.
Once the figures have been summarized, check that one creator appears once per intended view. If the same creator works on two campaigns, add the campaign key before sorting by creator. If they publish two placements in one campaign, decide whether the campaign view combines them and retain a separate list of content. Reporting by placement and reporting by creator can produce different distinct counts. The scope belongs in the column name or the note right above it.
Use a data dictionary that answers the review questions
| Field group | Minimum fields | Common decision |
|---|---|---|
| Content acceptance | Deliverable ID, version, approver, approval time and placement | Count each completed requirement once and preserve any separate publishing status |
| Order assignment | Order ID, selected creator, signal references, policy version and decision reason | Close as credited, held for review or unassigned |
| Eligible merchandise | Base value, eligible discounts, qualifying reversals and currency | Sum only rows eligible for the selected measure and reporting view |
| Spend | Cost ID, creator scope, cost type, currency and accounting date | Decide which costs each ratio can include |
| New customers | Method, customer key and qualifying first order | Deduplicate across the complete period covered by the metric |
| Settlement | Approved payout ID, transfer reference and status | Match payment separately from performance |
Walk through a second reporting cycle
Fictional workbook. A small accessories shop runs a creator campaign in April. Keep all amounts in USD. The shop excludes tax and shipping from the merchandise figures. It reports one credited creator per order and maintains separate paid and non-paid classifications. The cost measure for this example includes contracted fees, earned commission and ad spend. The team reports from a frozen April snapshot and later publishes a May as-of update.
The order and fee data
| Order | Creator | Eligible merchandise before return | Eligible return as of April close | New customer? | Paid media? |
|---|---|---|---|---|---|
| A-101 | Asa | $140 | $0 | Yes | Yes |
| A-102 | Asa | $120 | $20 | Yes | No |
| A-103 | Asa | $80 | $0 | No | Yes |
| B-201 | Blair | $200 | $0 | Yes | No |
| B-202 | Blair | $100 | $40 | Yes | No |
| C-301 | Cy | $90 | $0 | No | No |
Asa has three paid and eligible orders with $320 after the April return, including $220 assigned to paid media. Blair has two orders contributing $260. Cy has one repeat-customer order contributing $90. The program total for the six rows is $670. Four rows belong to qualifying first-time customers under the fictional shop’s rule. Here, each customer is distinct. When a real report combines multiple creator views, calculate unique customers across the combined cohort before dividing.
The creative ledger holds two accepted deliverables for Asa at $120 total, one for Blair at $125 and one for Cy at $80. Asa’s placement accounts for all $55 of paid media in this example. Everyone earns a 10% commission on eligible merchandise after returns. The April commissions are $32, $26 and $9. The example assumes the program recognizes these amounts at close and that settlement is tracked in a separate ledger.
Calculate each creator’s initial readout
| Creator | Accepted assets | Eligible revenue | Fee | Commission | Paid media | Program cost | Qualifying new customers |
|---|---|---|---|---|---|---|---|
| Asa | 2 | $320 | $120 | $32 | $55 | $207 | 2 |
| Blair | 1 | $260 | $125 | $26 | $0 | $151 | 2 |
| Cy | 1 | $90 | $80 | $9 | $0 | $89 | 0 |
| Total | 4 | $670 | $325 | $67 | $55 | $447 | 4 |
Asa’s spend per reported new customer is $103.50. Blair’s is $75.50. Cy’s ratio is undefined because Cy has no attributed new customers under the stated policy. Portfolio spend per attributed new customer is $111.75. The portfolio figure includes Cy’s costs. Averaging the two defined creator ratios would give $89.50 and would leave those costs out of the denominator comparison. The portfolio ratio should come from the total dollars and distinct qualifying customers.
Asa’s paid ROAS is $220 divided by $55, or 4×. The program-wide revenue-to-cost ratio is $670 divided by $447, about 1.50×. Those two figures use different revenue and cost scopes. There is no paid ROAS for creators with no ad spend. Show the spend and attributed revenue beside any ratio to give readers a way to catch a denominator error.
Process a return that arrives after the first close
In May, the shop posts another $30 merchandise refund on Asa’s A-101 order. The April cohort as of May falls from $670 to $640. Asa’s $320 becomes $290, and its paid assignment moves from $220 to $190. That leaves a paid ROAS of approximately 3.45× at the same $55 ad spend. The commission for that creator decreases by $3 under the fictional agreement. Program cost decreases to $444 if that report recognizes the same adjustment against commission expense.
Keep any affected customer denominator explicit. A partial refund still leaves an eligible A-101 sale under this example’s definitions. The credited customer remains included. With four customers and revised cost of $444, the revised program CAC is $111. If the same order had a full eligible refund, decide whether the customer still meets the qualifying definition, then update the denominator independently. Changing the purchase amount and qualifying-customer count together is a business decision that should be reflected in the method.
Send the update in a compact revision table
| April cohort measure | April close | May as-of view | Change |
|---|---|---|---|
| Eligible attributed merchandise | $670 | $640 | −$30 |
| Asa’s eligible commission | $32 | $29 | −$3 |
| Paid media revenue | $220 | $190 | −$30 |
| Ad spend | $55 | $55 | $0 |
| Program cost | $447 | $444 | −$3 |
| Distinct qualifying new customers | 4 | 4 | 0 |
Write a statement note that tells readers what changed. For this case, “A-101 received an additional $30 eligible merchandise refund in May. The revision lowers April cohort revenue by $30 and Asa’s commission by $3. The four-customer denominator is unchanged under the partial-return rule.” Make the processing date and evidence reference available in the detail tab. Save the April snapshot so an earlier statement can still be explained.
Know where the store can disagree with an analytics report
Store order data and analytics credit records may differ on event coverage, date, currency, eligible lines and refund treatment. Start by choosing a source for each measure, then put the whole comparison in one currency and observation window where practical. If the store source contains authoritative payment and refund details, use it to reconcile eligible order amounts. Use an analytics source for campaign credit when the method and contract make it appropriate. Describe which IDs connect the rows and what gets excluded when those IDs are missing.
Check differences in three passes. First, align periods, currency and eligible order status. Second, identify shared and unmatched order IDs. Third, inspect a small number of unmatched cases for a pattern. Running these passes in order prevents accidentally describing a time difference as a tracking issue. Record how much value is affected and which direction the gap points. A few low-value entries may simply follow the expected reporting lag. Large, systematic gaps can warrant a deeper review.
Give each mismatch its own handling
- Missing analytics event. Confirm whether the paid order appears with the appropriate status in the store. Keep the order out of a creator-specific analytics view unless you can apply an authorized fallback attribution rule.
- Multiple analytics events. Check whether your source records an initial event and a correction or actually counts two purchases. Preserve IDs and deduplicate according to the documented credit rules.
- Gross versus eligible base. Read which amounts the dashboard displays. If it includes taxes, shipping or excluded products and your program doesn’t, write the difference as a definition and show the eligible calculation.
- Reporting delay. Compare event date, capture date and export time. Keep the older report available and label what arrived later.
- Code and link conflict. Retain both signals and apply the policy once. Show a reason and review status before using the assignment in the payable view.
If a reporting tool measures credit across more than one channel, keep the label in the KPI report. A brand advertising, email and creator view can each claim influence for the same shopper. If the goal is a total unique credited order value, map each order to the selected owner under the rule. Include a separate interaction view for attribution analysis, where the follow-up question is which channels helped a customer along the way.
Read the KPI table in the right order
Start with the numerator and denominator. Ask which orders contributed, which customers qualified and which cost categories were included. Then read the distribution. A small number of high-ticket orders can make an average or ROAS appear stronger for one creator. One missed shipping deadline can leave an otherwise comparable creator with fewer opportunities to generate visits. Look at each creator’s context before deciding which score should drive spend.
Read enough of the creative evidence to understand the test. A creator who demonstrates product fit for returning shoppers may have a lower reported new-customer share than one with a fresh audience. A later post may have a shorter measurement interval in the weekly readout. Annotate the number of days measured and which contracted executions shipped. Compare the same post age where you can. A month of results can still be useful, so long as it doesn’t imply that each asset had the same window.
Use a holdout or another appropriate comparison for the causal question. High attributed sales may justify investigating whether the intervention is worth repeating. They don’t on their own estimate what would have happened without it. If a team changes offer, distribution and creative all at once, the next test should specify which comparison matters most. Record changes that could materially affect comparability and decide what you can isolate.
Lay out an operating report and a finance packet
The operating report should answer a small number of weekly questions. A top panel can show four accepted assets, six eligible orders and $670 in eligible revenue from the fictional workbook, with a last-refresh time. Next to each decision row, show the responsible person, date and evidence. Put detailed order and refund rows another level down. The reporting recipient should be able to move from a noteworthy headline number to the entries that produced it.
The finance packet should preserve the approved fee and commission calculation with the original rates, adjustments and settlement reference. Put refused, held, approved and settled lines in separate states. If a merchandise return affects a commission after the period, show the original period and the current adjustments. Each statement should have a version that can be tied back to the source records at approval time.
One handoff can keep both views in sync
- Freeze the creator and campaign identifiers before exporting, with a record of any merged or renamed rows.
- Check production’s accepted deliverable IDs and whether the delivery terms make those approvals billable.
- Reconcile the eligible order totals, using the agreed adjustment source and credit rule.
- Compute the metrics with both numerator and denominator available in the output.
- Give finance the Creator A case and one edge case to reproduce from the source rows.
- Record the outcome or next review for ambiguous orders and pending payments.
- Save the version and dates with the narrative so later changes support a comparison.
Test the report before you use it to release payments
Build known fixtures that catch predictable errors. One fixture can have two creators using the same amount and date but different identifiers. Another can contain an eligible click and a coupon code from different campaigns. Include an order with an excluded tax reversal. Give one creator costs but no acquisition-eligible customers. Include a partial settlement and an unallocated transfer of the same value. Each fixture isolates a type of error a reviewer can follow.
Before changing a spreadsheet formula, run the fixtures under both old and new logic. Record each outcome with a short explanation. If the intended change revises the attribution rule, confirm the orders whose new owner genuinely differs. If the change is an update to formatting or import, amounts should match before and after. Keep affected cases with the scope so someone can reproduce the test later.
For a real reporting cycle, sample orders near the cutoff and check any high-value exceptions before reviewing low-dollar routine matches. Check that summary rows tie to detail totals. Confirm that missing data has a visible reason and an owner. If a discrepancy is material to a release, hold the affected payout row and make the remaining approvals explicit. If the discrepancy is analytical and the payment record is sound, make the causal or marketing uncertainty visible without stopping a valid payment.
Turn the numbers into the next brief
Use the evidence to choose one change you can evaluate. If Asa’s paid-versus-organic breakdown suggests a productive demo, rebook a comparable version with the same product, offer and report settings if those are the factors you need to hold fixed. If Blair’s credited customers are stronger but the audience and format are different, identify which parts are replicable. If Cy’s creative worked for returning customers, assess it against the deliverable and its actual program role. Do not infer a channel or creator ranking from a cohort whose goals differ.
Send the next brief with clear definitions for acceptance, distribution, measurement and reporting cutoffs. Include one example of the decision it should support. Every person who has to act on the report should recognize their own input in it. Use the next data capture to improve the records that were hard to verify in this one.
Present a one-page summary at the campaign meeting
Start with the date range and one sentence about the decision. State whether the numbers are from the operating report, a fixed statement or a later cohort view. Example: “April creator activity through the May 12 adjustment cutoff. Decide whether to commission a second vertical tote demo and confirm the April statement change.” Then show the counts and financial measures, including the new customer denominator and paid-media spend. Reserve a small area for unresolved issues and their owners.
Put methods close enough to be visible without a long explanation. A metric card labeled “Net attributed merchandise, after eligible returns” is easier to interpret than a generic “Revenue” label. A card for “New-customer CAC excluding product samples” tells the reader the scope of the ratio. List the free products and shipping expense separately if they matter to a wider financial review. If the team changes these definitions after the first campaign, retain both meanings and their effective dates.
Walk one row through every handoff
Use A-101 from the fictional workbook to illustrate the evidence. Production confirms Asa supplied the accepted demonstration. Marketing verifies who received order credit and which paid classification applied. Commerce records the $140 eligible merchandise and later $30 return, reducing that line to $110. Finance sees the resulting $3 commission correction and looks for the approved period adjustment. The payment operator sees the relevant obligation, not the full media report. Show the shared identifiers linking those roles, and limit the copies of customer and payment details each recipient receives.
Close by assigning the action to the appropriate owner. A marketer can decide whether the reporting settings are comparable. A producer can adjust the next creative brief. A finance reviewer can approve a statement revision. The week after publication, each person should be able to find their own decision and its underlying source record.
Set a review rhythm for a lean team
Operating updates can be frequent and provisional if they identify their cutoff and source. Approval and close records can use a slower cadence tied to the actual program terms. Assign a narrow checklist to each meeting. Weekly, check which deliverables shipped, which attribution conflicts still need review and whether a date changed. At close, verify a complete set of order-level totals, recorded adjustments and amounts awaiting approval. At the next periodic review, compare like windows and identify a targeted experiment or process change.
When handoffs are slow, measure where time is consumed inside the process. Check whether finance frequently asks for the same missing approval attachment or whether marketing spends time explaining differing counts caused by windows. Fix the source field or handoff that keeps producing the question. Add the resulting check to your template before broadening the number of metrics.
Use a short exception register alongside the KPI report
A KPI report gets harder to read if every uncredited order has an explanation at the top. Summarize the open issues that affect a decision and give each one a separate row in the exception register. Keep the issue type, amount affected, owner, cutoff and next check visible. A missing order reference can be a reporting problem, a potential commission issue or both. The register should say which downstream views the open item currently affects.
Fictional examples. One $50 order is awaiting code ownership verification. Keep the $50 in the eligible population and place its attribution decision on hold. A different order has a $12 shipping reversal and its material amount is verified. Keep the reversal with the store record but preserve the eligible merchandise base if the agreement excludes shipping. A third creator’s approved fee is pending payment. Its approval and actual payment status are separate from attributed revenue, and both can appear on the same internal report with the state labeled.
Agree on who can clear each exception. Marketing may be able to confirm which creator promoted an authorized code. A commerce operator may need to verify a particular refund’s line breakdown. Finance can confirm whether a transfer or adjustment should change the payout. When an exception moves from open to resolved, add the outcome and source. Preserve any snapshot the team relied on before the decision.
Check the final report as a reader
Imagine the recipient only has the export and the short notes directly above it. Ask them to explain an accepted asset count, the eligible revenue of a refunded order, the cost on a zero-customer line, and the status of a payment. They should be able to repeat at least one calculation using the source lines. If they cannot tell how paid revenue and ads were scoped, improve the headings and evidence links before adding more explanation to the narrative.
Have the report owner keep a reusable list of fields, rather than copying an entire workbook every time. A new campaign may need a different currency, time window or deliverable taxonomy. Retain the core relationships and identify where this campaign diverges. That preserves the useful parts of comparability without forcing a future campaign into the old definitions.
A linked packet helps the next team avoid reconstructing the operation from screenshots. Include the agreement revision, the frozen exports, the reconciliation and the exact report version reviewed. Share only the sections each reader needs. Keep the same campaign and period labels in every view so the pieces can be matched without exposing unnecessary order details.
