M03: native input mapping
Plan a capped Meta creative experiment

Purpose and compatibility
A blank file is an input scaffold, not a native export or completed mapping. Preserve the exact column names/order and input names. Populate only from the documented native acquisition or explicit manual evidence. Stop if a required input, permission, privacy condition or coverage requirement is missing. Do not replace an old prompt until the named inputs and field-level mapping are reviewed. These files do not authorize login, setup, imports, account changes, message sending, publication, test submissions or spending.
Contract status: Requires distinct native-input templates or an explicit reviewed mapping; existing kit is not drop-in compatible
Compatible without mapping: false

Required inputs
ApprovedCreatives -> native-approvedcreatives-template.txt
Required content: Two actually approved creative IDs and the single approved variable; no invented assets or sensitive audience.
Complete each required field from approved source evidence.

Budget -> native-budget-template.txt
Required content: Currency, maximum total allowance, fees/taxes, dates, stop owner, and actual account budget-control evidence.
Complete each required field from approved source evidence.

Measurement -> native-measurement-template.txt
Required content: Primary metric, attribution window, available reporting/eligibility controls and source evidence; any unavailable exact menu remains blocked.
Complete each required field from approved source evidence.

Scope -> native-scope-template.txt
Required content: Full approved scope, source account aliases, date filters, date basis/timezone, as-of capture time, definitions, source-to-alias map provenance, matching rules, inspected/excluded records, permission/privacy limits, missing-data reasons, coverage and responsible reviewer. Include recipe-specific policies, versions and tests. Scope must be inside the AI workbook or pasted packet, not merely a separate unprovided file.
Complete each required field from approved source evidence.

Old files and reviewed mapping
INPUT-CHECKLIST.txt
Original first line: M03 OFFLINE EXPERIMENT BRIEF INPUT

INPUT-CHECKLIST.txt -> ApprovedCreatives, Budget, Measurement and Scope: transfer only actual approved assets, one approved variable, all-in budget/fees/taxes, dates, stop authority, metric and attribution definition. Acquire actual account eligibility, budget-control, A/B-test-control and report/export evidence separately.
This remains a launch-blocked planning path until current official/account evidence verifies the actual controls and report/export route. The checklist contains no actual experiment result, entitlement, tested control, creative asset or authority to spend.

How to perform the handoff
1. Keep original exports and raw evidence unchanged in restricted firm storage. Check actual source fields, dates, coverage, privacy and access before mapping.
2. Prepare the distinct native inputs above. Record every mapped field, derived interpretation, missing value and observed source reference in Scope. Identically named columns still require source/evidence validation.
3. Create a separate minimized analysis workbook or text packet. Name tables/sections exactly as listed. A CSV file does not itself create a named Excel table.
4. Include the full completed Scope in the same AI-visible workbook or pasted packet. Verify exclusions, denominator, matching rules and unknowns. Do not hide raw client data on another worksheet.
5. Obtain the responsible reviewer’s approval of the completed mapping and evidence coverage before using the native prompt. Keep all blocked items visible. Any later external action is a separately authorized human step.

Acquisition and privacy requirements
Use approved minimized administrative metadata and aliases only. Aliases alone do not guarantee anonymity. Keep untouched exports/screenshots, identifying source maps, full documents and sensitive narratives in restricted firm storage. A hidden worksheet is not a privacy boundary. Do not insert credentials, payment/tax identifiers, raw client documents or unsanitized review text. Unknown is not zero, false, completed or absent.
Existing authorized access to the correct source account and records; no new login, credentials, installation or permission grant is included.
Responsible lawyer/operations reviewer approves scope, definitions and any later action.
AI optional; use only approved minimized data and retain originals separately.
Current exact Meta experiment setup and export controls were not publicly verified. This remains a planning recipe, not an operational launch guide.
Meta help page redirected to login; no login attempted. Public Blueprint overview confirms feature family only.

Recipe acquisition / manual mapping instructions
Acquire an approved experiment brief and native eligibility evidence
Location: Existing approved creative brief; Ads Manager Experiments feature (exact live submenu/report-export route unverified)
Collect two approved creative IDs, one variable, primary metric/source, attribution window, all-in currency allowance, fees/taxes, dates, stop authority and historical aggregate volume. Staff with existing access captures available experiment options and displayed eligibility requirements. Do not create, publish or start a test.
Verification: Meta Blueprint verifies experiments and conclusive/inconclusive results. Its public lesson links and a help page did not expose full current setup/export controls without login; no exact eligible option, report export or hard all-in cap is claimed.
https://www.facebookblueprint.com/student/path/219763-ab-test-conversion-brand-lift-course


Do not proceed when
- Missing all-in budget/fees, exact account eligibility, approved creatives, measurement definition or safe audience policy.
- Current official/account evidence of the actual A/B-test controls and report/export route has not been supplied.

Scope template requirements
Full approved scope, source account aliases, date filters, date basis/timezone, as-of capture time, definitions, source-to-alias map provenance, matching rules, inspected/excluded records, permission/privacy limits, missing-data reasons, coverage and responsible reviewer. Include recipe-specific policies, versions and tests. Scope must be inside the AI workbook or pasted packet, not merely a separate unprovided file.

Old examples and validation limits
Legacy synthetic examples and negative cases belong to their old prompts. They do not automatically test the native route and must not be fed into a new prompt without an explicit reviewed mapping and separately approved test design. These new files contain no synthetic values, source exports, account results or live-test evidence.
Planning path only; current account-specific Meta setup/export UI unverified; launch blocked; not tested
Public official documentation checked 2026-10-15; no login, export, live query, import, installation, configuration, message or client workflow was executed.
Local validation covers only exact scaffold schemas, placeholder presence, blank CSV rows and required warnings. It does not establish live account coverage, native export validity, successful integration or completed workflow tests.
