---
name: funnel-levels-audience-engagement-conversion
description: "Judge each piece of marketing by the job it should do."
category: Strategy & Measurement
stage: —
definitive_article: /9-triangles-framework-scalable-home-service-businesses/
status: complete
---

# Funnel levels (Audience, Engagement, Conversion)

Judge each piece of marketing by the job it should do. This guide helps your team see where people move from first notice to a sale. Start with your live pages and ads, then name the main job of each.

**The path:** Active work → Main job → Right metric → Next step

**Start when:** The team needs to map marketing activity and metrics to the customer’s stage.

## Inputs

- Current assets and campaigns, their goals, audiences and destinations.
- [Goals, Content, Targeting: the result, proof and people for this work](https://blitzmetrics.com/gct-business-strategy/) brief and source-backed metrics for the same period.
- The current customer path, including how inquiries are handled.

## Steps

1. Use three practical levels: audience/awareness means reaching relevant people; engagement/consideration means they watch, read or interact; conversion means the agreed action such as a qualified inquiry, booking or sale. The [funnel discussion](https://blitzmetrics.com/9-triangles-framework-scalable-home-service-businesses/) uses these equivalent teaching labels.
2. Inventory each in-scope active item and assign its primary job from its purpose and destination. Record a secondary role where real; do not pretend every asset or person has only one role.
3. Choose a primary metric and balancing metric for each job. Examples are relevant reach with cost per thousand impressions; useful views with watch time; or qualified leads with cost per lead. Define the denominator and source.
4. Map the next action a person can actually take. Check a working destination or follow-up, not just a drawn arrow. People can enter at different stages; the diagram is a planning aid, not proof of a fixed individual journey.
5. Compare performance within the same stage and period. Flag missing evidence and weak handoffs. An empty stage is a question about the strategy, not automatic proof that the business is broken.
6. Save the map, baseline and gaps. Propose the most useful next content or handoff fix with owner and review date, and carry stage results into the weekly report.

## 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/).

- [ ] Every in-scope asset has a supported primary job and relevant metric.
- [ ] The map shows real destinations or explicit gaps; audience-level assumptions are not individual tracking claims.
- [ ] Stage baselines and proposed repairs have sources and owners.

## Example(s)

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

A fictional roofer has a short safety video, a repair guide and a booking page. The video is judged on useful reach and watch time; the guide on visits and its next-step clicks; the booking page on valid inquiries. No one claims the same person followed all three without matching evidence.

## Handoff and Content Factory context

[Show what works and what needs review](https://local-service-spotlight.github.io/task-library/?task=show-whats-working-and-what-isnt#task-show-whats-working-and-what-isnt) uses the stage-specific goals; [Plan the next recording session](https://local-service-spotlight.github.io/task-library/?task=use-for-content-planning-and-video-topics#task-use-for-content-planning-and-video-topics) receives content gaps and [Write the agreed weekly report](https://local-service-spotlight.github.io/task-library/?task=submit-weekly-maa-report-every-friday#task-submit-weekly-maa-report-every-friday) receives the results.

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 5, revenue 5, gating 3 (runs every factory cycle or weekly; ads/revenue path)
- **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/9-triangles-framework-scalable-home-service-businesses/)
- [This task in the Task Library](https://local-service-spotlight.github.io/task-library/?task=funnel-levels-audience-engagement-conversion#task-funnel-levels-audience-engagement-conversion)
- [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.