Partnership-Ad Readiness and Test Sheet
Use this before scheduling paid spend. It is a planning record, not a substitute for Meta's current account-specific setup requirements or professional agreement review. Bring the creator agreement, account operator and proposed test brief.
Worked example: a proposed app demo
Fictional case: a creator has supplied a useful app demonstration. The buyer wants to run a partnership ad but has not verified all permissions.
| Check | Evidence available in example | State | Required next action |
|---|---|---|---|
| Relevant demonstration | Current cut accurately shows the feature | Reviewed for this cut | Keep final approved version linked |
| Product claims | Product approver confirms two factual statements | Approved | Recheck if the edit changes them |
| Organic post commission | Written scope includes one post | Confirmed for organic use | Do not infer paid authorisation |
| Paid licence | Duration and editing rights not agreed | Missing | Obtain written scope before paid use |
| Account authorisation | Operator has not verified current permission state | Not checked | Verify actual accounts and record date |
| Disclosure | Launch disclosure wording not approved | Open | Have responsible reviewer confirm it |
| Test comparison | Same offer and destination; creator and creative differ | Package comparison | Do not call it an isolated identity-effect test |
| Tracking | Purchase event defined; attribution window not recorded | Incomplete | Record event, window and reporting source |
| Full cost | $1,000 media + $600 creator/editing assumed | Illustrative budget only | Confirm quote and any other costs |
| Launch decision | Rights, authorisation and tracking incomplete | Not ready | Hold spend until named owners clear gaps |
A useful video can be ready for creative review while the proposed ad remains unready for launch. Keep those states separate.
Cost example
The fictional test later records 20 attributed purchases. Media cost per attributed purchase is $1,000 ÷ 20 = $50. Including the assumed $600 creator/editing cost gives $1,600 ÷ 20 = $80. If rights or internal work add costs, include them before calling the latter fully loaded. These calculations do not establish incremental purchases or a future acquisition cost.
Fill in your preflight
| Item | Evidence / link | State | Owner | Date / expiry | Next action |
|---|---|---|---|---|---|
| Approved cut and claims | Enter your record | Enter your record | Enter your record | Enter your record | Enter your record |
| Written usage scope | Enter your record | Enter your record | Enter your record | Enter your record | Enter your record |
| Current account permissions | Enter your record | Enter your record | Enter your record | Enter your record | Enter your record |
| Disclosure review | Enter your record | Enter your record | Enter your record | Enter your record | Enter your record |
| Tracking and attribution rules | Enter your record | Enter your record | Enter your record | Enter your record | Enter your record |
| Complete cost record | Enter your record | Enter your record | Enter your record | Enter your record | Enter your record |
| Launch approval | Enter your record | Enter your record | Enter your record | Enter your record | Enter your record |
Write the test question
Question: ___ Package or isolated change: ___ Comparison: ___ Business outcome: ___ Other diagnostic signals: ___ Observation window: ___ Cost scope: ___ Decision owner: ___
Choose a comparison and observation plan appropriate to your economics, data and platform delivery. No universal budget, duration or winning percentage is supplied here. If only the whole package is compared, interpret the result at that level.
Your final output: ready / blocked on permission / blocked on rights / needs measurement plan. State who clears each gap. After the test, record what happened, what remains uncertain and the next spending decision.