Turn Meta performance into a creative test by recording what happened, identifying what remains uncertain, and choosing the smallest useful question to investigate next. Give Spark the relevant account context and ask for a brief before generating assets. A high CTR or low CPA can inform a hypothesis; neither explains by itself why an ad performed as it did.
This guide covers the handoff from review to the next production decision. For the full weekly process, use the Meta creative workflow. For selecting between multiple candidate tests, use the testing backlog.
Start with comparable account evidence
Before interpreting a result, confirm the date range, campaign objective, conversion definition, attribution context, offer, product, and delivery. Identify the creative and concept so the team is discussing the same thing.
An ad that received little spend is not a clean comparison with one that received substantial delivery. A promotion running in one period can also make two creatives appear different for reasons outside the design.
| Review input | Why it belongs in the decision |
|---|---|
| Ad and concept identifiers | Connects the result to the correct creative |
| Dates and offer | Makes relevant campaign conditions visible |
| Spend and delivery | Shows how much evidence exists |
| Conversion definition | Clarifies what the performance metric means |
| Purchase or lead data | Keeps the business outcome separate from attention |
| Known changes | Flags site, pricing, or campaign differences |
Missing information should remain missing. Do not enter zero purchases when purchase data is unavailable, or turn an untracked outcome into evidence of failure.
Separate the observation from the explanation
Consider a hypothetical travel-bag campaign. A product-compartment ad receives more clicks than a lifestyle ad, but the available purchase evidence is weak. This is an illustrative situation, not an Adrio customer result.
The observation is the difference in measured response under the stated conditions. “People want organization” is an explanation to investigate. “The lifestyle concept is dead” is a stronger conclusion the evidence may not support.
Ask Spark to retain those distinctions:
Review these ads for this date range and conversion definition. Separate observations, possible explanations, and missing evidence. Do not change campaigns or make creative yet. State which comparisons are weak because delivery or conditions differ.
Read the response against the actual account records. An explanation is useful when it leads to a sensible next question, not when it sounds certain.
Decide whether creative is the right next variable
Weak purchase results can reflect the offer, product-market fit, destination page, measurement, or delivery as well as creative. A new image will not resolve every account issue.
For the travel-bag example, the compartment ad may have introduced a feature the page explains poorly. The next action might be checking the destination message before making more variations. Alternatively, the ad may attract a customer whose expected use the product does not meet.
Ask what evidence would distinguish those explanations. Check the landing page and approved offer. If the creative creates an expectation the product cannot support, fix the message before testing it again.
Do not ask Spark to compensate for missing purchase data with confident creative recommendations. Narrow the decision or collect the missing information.
Turn the uncertainty into one testable question
Once a creative question is worth investigating, define it clearly. For the bag, the next question could be whether a practical demonstration communicates the organization benefit better than an annotated still image.
Keep the product and offer fixed where feasible. Name the proposed concepts and executions so the reviewer understands what changes. If several elements change together, describe the test as a comparison of bundles, not proof about one element.
The iteration-versus-diversification guide helps classify the next action. A clearer execution of organization is an iteration. Introducing travel durability as a new buying reason is a concept change.
Write the brief before generating the next batch
Give Spark the approved product inputs and evidence. Ask it to propose the direction and missing assets:
Our next question is whether demonstrating the bag compartments explains organization better than an annotated product photo. Keep the SKU, offer, and destination fixed. Propose one static execution and one video sequence. Use only the approved dimensions and product images. Flag any scene we cannot support with the available assets.
Review the plan. Does it actually investigate the question? Has it introduced another claim or offer? Is the proposed proof visible to the customer?
Approve the generation cost only after the brief is clear. More outputs can be useful during exploration, but the live account needs a contained set of ads it can fund and assess.
Review the new creative against the hypothesis
Check the asset in its intended placement. The viewer should be able to understand the organization benefit without reading the team's analysis.
For the static, inspect the annotations and product. For the video, check the scene sequence, captions, and any spoken claims. Revise the relevant part while retaining the approved offer and product identity.
Spark can create static and video ads. Both image and video ads can be published directly to Meta with approval by default. Assign a launch owner so the approved creative reaches the intended campaign.
Use the approval-controls guide for the publishing and budget review. A good brief and accurate creative still need the correct account, destination, and campaign proposal.
Choose the review rule before launch
Agree when to review and what evidence the decision needs. The timing depends on delivery, conversion frequency, and the question. There is no fixed number of days or universal spend threshold that makes every test informative.
Define how to handle weak delivery or conflicting signals. If one execution receives too little delivery, record an inconclusive comparison. If attention improves without the business outcome, examine whether the message attracts the intended customer.
Keep the review in the same decision record as the brief. Otherwise the team can forget why an ad was made and reinterpret the result around whichever metric looks favorable.
Close the loop with a specific decision
Record the observation, remaining uncertainty, and next action. Useful outcomes include retaining the concept, revising the execution, investigating the destination, collecting more evidence, or trying a different buying reason.
Do not erase inconclusive tests from the history. They show what the account has not yet established and prevent the same unsupported conclusion from returning next month.
In Adrio, carry the selected direction into the next Spark run with the relevant context. If you use a specialist reporting tool, bring the evidence it produces into the brief. The Adrio vs Motion guide discusses that reporting-to-production handoff.
Frequently asked questions
Does the highest-CTR ad tell me what concept to make next?
It provides a response signal, not a complete explanation or business outcome. Review conversion data, delivery, offer, and destination before deciding.
Can Spark read results and make the next creative?
Spark can read connected Meta performance and help plan new static and video creative. Supply or verify the relevant dates and context, then approve the direction and generation cost.
Should I pause every ad with a worse CPA?
Not automatically. Check delivery, conversion evidence, comparable conditions, and the agreed review rule. A proposed account change needs its own review.
What makes a useful next brief?
A specific question, approved product and offer, evidence behind the choice, intended execution, fixed elements, and a review rule. Use the brief template to record it.
