fact
What the supplied snapshot shows
The September 6 Meta response records an active ad set with Instagram and Threads placements, a mixed-interest audience and a form-start optimization event.
Results and measurement · 1
First resolve what a lead meant
TLDR. Reconcile lead definitions before ranking channels or judging a change.
The September 6 snapshot establishes an optimization setting. It does not identify the origin or quality of every lead reported for August.
fact
Specific source conflict
The monthly deck describes a pixel Lead event. The persona deck describes native Meta forms and unavailable website Lead events. The strategy deck describes a measurement rollout. The index labels the material as sample content. These source claims conflict, and the September 6 optimization snapshot does not reconcile them.
interpretation
What that can support
A form-start optimization setting describes what the ad set was seeking. It does not prove that every separately reported Lead event was a form start, a native form or a qualified enquiry.
unknown
What this demonstration does not establish
Current account state, qualified enquiries, sales and the effect of any subsequent changes have not been retrieved.
What we still have to check
Match reporting windows and event definitions to dated platform and CRM records. Then verify whether a reported signal represents a successful submission, a reachable person or a qualified enquiry.
Sources and limits
Supplied Meta targetingsearch and ad set response · 2026-09-06 · dated provider snapshot. The snapshot establishes returned settings and search results on that date, not present reach, eligibility or performance.
Fusion reference pack · 2026-09-02 · historical reference. The index dated September 2 mixes sample and live labels. Linked decks dated September 3 conflict on lead mechanisms. Used for information coverage and explicit source comparison, not reconciled performance.
Results and measurement · 2
Keep every result at its actual level
TLDR. Compare equivalent windows and event definitions, then follow each enquiry to its business outcome.
A monthly report should show where the process improved and where evidence ends, with work delivered separated from measured effect.
unknown
Required monthly evidence
A production run supplies PPC and Meta costs and traffic, SEO where present, top paid landing-page funnel, CRM enquiries, work and prior-test outcomes.
hypothesis
Creative and audience interpretation
Creative and copy rankings, placement, age, gender, region and device comparisons need matched windows and usable samples. The demonstration preserves these information types, with no verified current rankings or claim that a demographic group cannot buy.
hypothesis
Sales path to retain
Proposed weekly path: campaign and creative → submission → reachable person → suitable space, budget and timing → demonstration → offer → purchase or loss reason. Preserve UTM attribution. A production report should explain where progression changed, with completed work separated from demonstrated effect.
What we still have to check
Confirm exact source windows, comparable baselines, lead mechanism and sales feedback.
Sources and limits
Fusion reference pack · 2026-09-02 · historical reference. The index dated September 2 mixes sample and live labels. Linked decks dated September 3 conflict on lead mechanisms. Used for information coverage and explicit source comparison, not reconciled performance.
Supplied campaign-settings.md · 2026-09-06 · dated proposal. Campaign options were proposed, not activated. Current eligibility, demand and budget need readback.