---
name: analytics-measurement-plan
description: "Define and verify events, conversions and campaign attribution for a measurable funnel. Use when the user requests analytics measurement plan. Select relevant methods for the requested outcome; unrelated tasks do not require this skill."
metadata:
  version: "1.0.0"
---

# Analytics Measurement Plan

Define and verify events, conversions and campaign attribution for a measurable funnel.

## OLLIE Runtime integration

Use this capability under the active OLLIE Operator. Read live Workspace Context and tenant bindings for client facts and required inputs. This generic package contains no client configuration. Consume ask-ollie-authority-core for authority, outloop-access-fallback for access and recovery, email-lifecycle-core for communication, and the bootstrapper Runtime Contract for ownership, scheduling and completion. Preserve domain constraints; this Skill creates no competing execution path. Use one method, combine skills, or fill missing steps with authorized tools as the task requires.

External access uses the active Workspace’s approved Outloop capabilities. Never request, read, embed or expose credentials. A service named in a method is a possible dependency, not an access grant. Local file and application work uses the host’s authorized tools.

## Required inputs

- Business funnel
- Existing event inventory
- Consent requirements
- Campaign naming rules

## Methods

### Define observable events

Map each business action to an observable event, trigger, parameters and owner. Separate raw events from approved conversion definitions.

### Set identity and attribution

Define deduplication keys for browser and server events, naming conventions and attribution windows. Avoid recording personal details in event names or analytics payloads.

### Validate synthetic journeys

Validate each event with a synthetic journey and compare debug observations with stored reporting data. Check double-firing, missing consent and cross-domain transitions.

### Explain discrepancies

Document discrepancies, reporting latency and interpretation limits. A tag firing does not prove a conversion is counted correctly in an advertising account.

## Completion

Verify findings against source evidence and read back the resulting artifact or authorized change. Report inputs used, methods selected, output location, assumptions and unresolved dependencies. Do not report a plan, queue entry, draft, test fixture or accepted request as a completed external action. Use the task’s requested format; if a tool is unavailable, finish independent work and identify the exact unfulfilled deliverable.

## Test before relying on it

Read [the synthetic evaluation cases](references/evaluation.md) for activation, output and isolation checks. These cases are test instructions, not evidence that a host or provider test has passed.