Before you begin
The Google Ads account must already be under the agency MCC
The daily CONFIG Sync script discovers new MCC child accounts and adds them to CONFIG_Clients as PAUSED. If the account is missing below, connect it to the MCC and run CONFIG Sync manually or wait for its next scheduled run.
Existing clients
Continue an onboarding
Resume a client created by this app without re-entering its setup. The workbook is verified before lifecycle controls are restored.
Provisioned safely
The client, workbook, and runtime files are ready
Controlled go-live
Finish the Google Ads Scripts handoff
- Install the generated
WEEKLY_REPORT_CONFIG_JSONandAUDIT_SNAPSHOT_CONFIG_JSONScript Properties. - Run the weekly Google Ads script in Preview. Confirm the account, campaign IDs, destination, budget, and row count.
- Generate the live config, reinstall the weekly property, and run one final Preview.
- Only then activate the account in
CONFIG_Clients.
Activation starts audit collection. Budget alerts remain a separate approval and are not enabled here.
Final verification
Confirm the first live data arrived
The app will read the run ledgers and verify the first post-activation core extraction, staged handoff, and weekly workbook delivery. It does not change ads or trigger scripts.
Guided planning workspace
Prepare a reviewed campaign brief
Save source-backed facts, questions, access checks, measurement references, and a proposed budget. This workspace does not create Editor files, change ads, post, launch, or prove that anything is serving. An approved setup continues into the separate reviewed engineering-preview package workspace below.
1. Review source facts
Enter a short exact excerpt or upload a UTF-8 .txt/.md file up to 64 KiB. Source text is transient; only snippets you add as facts are saved.
Saved source references, hashes, and spans support traceability. They do not verify ownership of an external document or prove that a statement is true; an authorized person must review each fact.
2. Track open questions
3. Record tested access and ownership
4. Link measurement evidence
Link the exact authorized S01 measurement revision for this same client account. The saved record remains the authority for each trust dimension.
Verifier/operator step: choose the exact saved measurement revision after checking its client, account, outcome, dates, and role.
5. Build the proposal
6. Review the next gate
Readiness describes eligibility for one stage. It is never proof that an export exists or that ads were posted, launched, or served.
Detailed Editor build
Compose and review the exact files
Enter every keyword, ad line, negative, location, and asset explicitly. The planning intents above are context only; this screen never invents ad copy or keywords from them.
Independent review
Review rows, budget math, sources, and generated files
Guided planning workspace
Prepare a reviewed Meta (Facebook/Instagram) setup
Save source-backed facts, questions, and a proposed Meta campaign/ad set/ad/creative build. This workspace does not call Meta, create anything in Ads Manager, or push or publish anything — the build must be created manually in Ads Manager after review.
1. Link the Google setup workspace (optional)
Link the reviewed Google campaign-setup revision for this same client, then import individual approved facts from it rather than re-entering them.
2. Review source facts
Facts show as approved, candidate, or rejected. An authorized reviewer must approve a fact before it can support a proposal field.
3. Track open questions
4. Build the proposal
Edit the JSON proposal directly. Every reference (sourceFactIds, destinationId, adSetKey, creativeKey…) must point to something already defined above or in this same proposal.
5. Layer evidence and Advantage+ choices
Each layer — campaign, ad sets, ads, creatives, placements, and event sources — is shown with its own evidence and state, kept visually separate.
6. Review readiness
Readiness describes facts, conflicts, unknowns, blockers, and tracking status. It is never proof that anything was built, posted, or is serving.
7. Lifecycle
Five separate lifecycle states. Each is shown independently — none is inferred from another.
8. Handoff
There is no publish or push-to-Meta button. The handoff panel documents the manual build steps for Ads Manager.
Managed AM
Owned work queue
Choose an authorized scope. Approval, implementation proof, and outcome review remain separate steps.
Local engineering evidence
Google setup rules
These campaign-scoped checks show supported findings and evidence limits. They do not establish whole-account readiness or change Google Ads.
Local engineering evidence
Follow-through
Each stage is recorded separately: the finding, the decision, the implementation, a recorded check and the mature result. Implemented does not mean it worked.
Propose guided work
Choose a current supported gap. The task still requires recorded review before implementation.
Priorities
Watch items
Completed work
Readiness
What the current evidence supports
Choose a client, account, and allowed campaign in Managed AM to load readiness.
Outcome signals
Count, value, attribution, and maturity are shown separately. One verified signal does not prove another.
Owned next checks
Reports
Report drafts
Review the saved client or Account Management report before sending it for approval.
Weekly report schedule
Automatic drafting needs a saved active weekly schedule and your permission. Approval and delivery remain manual and recorded.