---
name: stage-1-plumbing-fb-ads-google-ads-analytics
description: "Make sure your business can see what its marketing does."
category: Strategy & Measurement
stage: —
definitive_article: /social-amplification
status: complete
---

# Stage 1: Plumbing (FB Ads, Google Ads, Analytics)

Make sure your business can see what its marketing does. This guide checks the accounts and tracking before work goes live. Start with the right business, its allowed scope and the access list.

**The path:** Accepted scope → Asset ownership → Tracking tests → Readiness handoff

**Start when:** An accepted business scope is ready for the first Social Amplification Engine phase, or its tracking needs repair.

## Inputs

- [Social Amplification Engine, the six-phase marketing plan](https://blitzmetrics.com/social-amplification/) accepted scope and the authoritative client-status record.
- The current access register and asset IDs; business owners for Meta, Google Ads, website, Tag Manager, Analytics and Search Console as applicable to the agreed engine gate.
- [Digital Plumbing](https://blitzmetrics.com/digital-plumbing/) and the intended conversion definitions, test limits and change authority.

## Steps

1. Confirm the right business and relationship status first. Active Client or a separately scoped Special Project can supply the work path; Not Active or HOLD stops dependent operations. Read the current engine gate rather than treating a self-report as onboarding approval.
2. Inventory existing assets and ownership. Record the actual domain, account/property/container IDs and granted roles without copying secrets. Reuse working business-owned assets instead of creating duplicates.
3. Check Meta business and ad-account ownership and the required partner access through the account’s supported controls. Verify a permitted read; a displayed account name does not prove administrative access or correct ownership.
4. If Google Ads manager linking is in scope, use [Google’s current manager-link instructions](https://support.google.com/google-ads/answer/7456530?hl=en). A link preserves the client account and does not automatically transfer administrative ownership or billing.
5. Validate the site’s actual analytics and tag setup against the agreed key events. Inspect existing tags before installing anything. Use [Google’s DebugView procedure](https://support.google.com/analytics/answer/7201382?hl=en) for a controlled test device, with its consent state and event parameters; do not generate a real purchase or contact a customer to simulate proof.
6. Check each required destination for missing or duplicate test events and the correct account. Debug visibility demonstrates receipt, not full revenue attribution. Keep test traffic identifiable and remove temporary debug configuration as the official guide requires.
7. Save ownership, access and test receipts. The current engine requires Search Console, CMS, Analytics and Tag Manager green before shipping or amplification. Drafting can continue where allowed, but any missing required row keeps the release phase blocked; hand a precise repair to its owner.

## Definition of done (QA checklist)

Quality assurance (QA) means checking the result against its agreed requirements; see the [Article Guidelines](https://localservicespotlight.com/article-guidelines/).

- [ ] The accepted scope and authoritative business identity are confirmed.
- [ ] Required asset roles and controlled tracking tests have evidence; missing rows remain blocked.
- [ ] No duplicate account/tag, implicit billing transfer or unsupported release occurred.

## Example(s)

**Fictional teaching example. This is not a client result or proof of a completed run.**

A fictional shop has a working Analytics tag but two form events per submission. The test identifies a duplicate tag. The owner approves its narrow removal, and a new controlled submission reaches the right property once. Search Console access is still unknown, so the shipping gate remains blocked despite that repair.

## Handoff and Content Factory context

[Set the engine goals](https://local-service-spotlight.github.io/task-library/?task=stage-2-goals-mission-90-day-goals-cpa-roas-budget#task-stage-2-goals-mission-90-day-goals-cpa-roas-budget) receives verified measurements and constraints; missing access goes to the named asset owner.

This work supports the [Content Factory: Produce, Process, Post and Promote](https://blitzmetrics.com/content-factory/) across its relevant stages. It uses the actual inputs and next owner above; a strategy or measurement guide does not manufacture transcripts, clips or other unrelated stage outputs.

## Start with an agent

Give the AI worker this recipe, the real Inputs, the desired result and the actions already authorized. Ask for the saved output, source evidence, passed and failed checks, and the next owner. A skill is a set of instructions. Loading it does not prove access, install a scheduled job or complete the work. Use the [current installation guide](https://localservicespotlight.com/install/) only if reusable setup is needed; a ZIP contains instructions and is not an access grant.

Use the actual supported app and verified source access. A model name is not a promise of browser control, memory or unattended work. For recurring work, inspect the real job’s trigger, owner, timezone and observed firing; this recipe creates no schedule. Before any media playback, mute the player and set volume to zero. A silent review does not prove sound was heard.

## Record the real execution

Open the run record when work begins. Keep one execution ID, the exact starting recipe revision, input sources and actual state. Write a [meta article, the record of one real execution](https://blitzmetrics.com/meta-article-prompt/) with results, checks, failures and next owner. Link it to this task in the [Task Library](https://local-service-spotlight.github.io/task-library/). Writing is required; public release follows existing authority.

Reuse the same execution ID for internal reviews, meta writing, revisions and retries. A blocked run stays open with its dependency and owner, without an invented finish time. Keep historical public examples as dated evidence; article counts alone are not verified execution frequency. Use supported findings to propose and verify a recipe improvement.


<!-- factory-layer:start -->

## Factory chain (do not treat this as isolated)

- **Phase:** —
- **Importance:** 5/5 `●●●●●` — frequency 4, revenue 5, gating 5 (runs every factory cycle or weekly; ads/revenue path; unblocks a chain (access/plumbing))
- **Suggested previous station:** —
- **Suggested next station:** —
These stations are generated neighbors, not verified prerequisites or handoffs. Follow the task’s actual Inputs and Handoff sections.
- **Handoff:** Save this task’s actual output, source, date and checks where the receiving owner can read them. Follow the Inputs and Handoff sections for its next step.

## Model routing (same factory, any engine)

- **This task's lane:** `any` — Any capable chat model (Claude, ChatGPT, Grok, Gemini). SOP following, drafts, checklists.
- **Single-engine path:** Use the capable AI app you already have. Check its required tools and access before starting. Pass the actual result and proof to the next task.
- **Optional multi-engine:** A tested local model may draft; a stronger model may review facts and voice. Use supported tools for approved actions. Pick models from observed quality and cost; a model name does not prove it can run this task.
- **Never** store the working state in one vendor's memory. Files in the Content Library are the bridge.

<!-- factory-layer:end -->
## Definitive article & links

- [Maintained source guide](https://blitzmetrics.com/social-amplification/)
- [This task in the Task Library](https://local-service-spotlight.github.io/task-library/?task=stage-1-plumbing-fb-ads-google-ads-analytics#task-stage-1-plumbing-fb-ads-google-ads-analytics)
- [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [Definitive article and task recipe standard](https://blitzmetrics.com/definitive-article-guide/)
- [How recipes and run records work together](https://localservicespotlight.com/meta-articles/)

## Review and evidence still needed

The inherited contributor status is `complete`. It is preserved, not promoted by this rewrite. That label alone does not verify document readiness, account access, an actual execution or a client outcome.

A relevant real execution, source evidence, independent reviewer and accepted handoff remain to be recorded. The fictional example teaches the method and does not fill a real-run evidence gap. The opening and full method need a named semantic reviewer; the task-specific path is source guidance, with visible desktop/mobile presentation still to check.