---
name: collect-verified-weekly-measurements
description: "See which work brings leads and sales to your business."
category: Strategy & Measurement
stage: —
definitive_article: https://localservicespotlight.com/skills-measurement-analytics/
status: needs-work
---

# Collect verified weekly measurements

See which work brings leads and sales to your business. This guide helps your team check the numbers before it chooses what to change. Start with the source and date range for each number.

**The path:** Source contract → Matching exports → Checked numbers → Weekly report

**Start when:** The agreed measurement window has closed for an authorized business or funnel.

## Inputs

- The accepted measurement source contract, business scope, period, timezone and comparison period.
- Read access or named exports from the sources that own the requested metrics: Search Console, site analytics, calls, forms, customer records, bookings and revenue.
- [Goals, Content, Targeting: the result, proof and people for this work](https://blitzmetrics.com/gct-business-strategy/) targets and the preceding report; the current [Measurement & Analytics procedure](https://localservicespotlight.com/skills-measurement-analytics/).

## Steps

1. Identify the authoritative source and definition for each metric. Search visibility, site visits, inquiries, qualified leads, bookings and collected revenue are different stages; do not substitute one for another.
2. Confirm the in-scope relationship and approved source access. Record which sources were actually read. Use not connected or unknown for inaccessible data, never zero.
3. Pull the current and preceding comparable windows. Retain export date, period, timezone, units, filters and attribution settings. Deduplicate leads by the client’s accepted identity rules while preserving source totals.
4. Compute ratios with named numerators and denominators. For the source’s low-ticket funnel, opt-in rate is opt-ins divided by landing visits, take-rate is buyers divided by its specified eligible audience, cost per lead is spend divided by ad-page opt-ins, and cost per buyer is spend divided by front-end buyers. Confirm the actual source denominator before computing take-rate; do not infer it from an unlabeled percentage.
5. Use the source’s 25% opt-in and 3% take-rate targets only for the applicable agreed funnel. Do not judge its page-rate thresholds below 100 visits. Preserve the source’s comparison notes for changes above 30%; neither a threshold nor a week-over-week move proves a cause.
6. If using front-end revenue divided by ad spend, label that ratio precisely. A ratio of at least one covers ad spend on that revenue basis; fees, fulfillment, refunds, margin and timing still matter. It is not proof of free leads, profit or permission to scale.
7. Reconcile totals and note missing sources, incomplete attribution and sample limits. Save the report, weakest supported stage and proposed next check. Hand findings to analysis and the relevant action owner; this measurement task changes no campaigns or funnels.

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

- [ ] Each value traces to its source, definition, unit and period; missing values remain unknown.
- [ ] Funnel thresholds apply only to the declared source contract and sufficient sample; zero denominators have no invented rate.
- [ ] Qualified leads, bookings and revenue stay separate; report and handoff are saved.

## Example(s)

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

In a fictional week, ad spend is $100 and recorded front-end revenue is $120. The ratio is 1.2 on that basis. Fulfillment costs and refunds have not been checked, so profit stays unknown. A page has 80 visits, so its opt-in result is reported without a pass/fail verdict against the 100-visit rule.

## Handoff and Content Factory context

[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) and [Diagnose weak results](https://local-service-spotlight.github.io/task-library/?task=analyze-why-underperformers-fail#task-analyze-why-underperformers-fail) receive the report. The authorized sales or ads owner receives the relevant stage finding, not an automatic scale instruction.

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:** 3/5 `●●●○○` — frequency 3, revenue 3, gating 2 (supporting)
- **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://localservicespotlight.com/skills-measurement-analytics/)
- [This task in the Task Library](https://local-service-spotlight.github.io/task-library/?task=collect-verified-weekly-measurements#task-collect-verified-weekly-measurements)
- [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 `needs-work`. 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.