Imported from faionfaion/faion-network (skills/faion/knowledge/marketing/conversion-tracking/AGENTS.md). Install upstream with npx skills add faionfaion/faion-network --skill conversion-tracking. Copyright stays with the author.

Conversion Tracking

Summary

One-sentence: Generates the conversion-tracking config: event taxonomy, pixel + server-side tags, validation script, QA fixtures across browsers.

One-paragraph: Generates the conversion-tracking config: event taxonomy, pixel + server-side tags, validation script, QA fixtures across browsers. Use it when кілька джерел трафіку, потрібен unified event taxonomy. The methodology pins the artefact shape via JSON Schema in content/02-output-contract.xml, so a downstream agent can validate the output mechanically rather than by prose review.

Ефективно для:

• Кілька джерел трафіку, потрібен unified event taxonomy.
• Server-side tagging доступний (GTM Server / Cloudflare Worker).
• Privacy mode browsers + ad-blockers — потрібен CAPI / Conversions API.
• QA fixtures + validation script запускаються при кожній зміні tracking.

Applies If (ALL must hold)

• The producing agent has read access to the inputs named in Prerequisites.
• The downstream consumer expects an artefact whose shape matches produces=config.
• A named human reviewer is available for signoff before any binding action.
• The task has more than a one-shot scope — output will be re-read or extended later.

Skip If (ANY kills it)

• Pre-discovery: inputs unstable, problem not named — pick a discovery methodology instead.
• One-shot prompt task that nobody else will reuse — write a plain prompt, not a methodology call.
• Output consumer wants a different shape than produces=config — pick a methodology whose contract matches.
• Hard real-time path where the output-contract validator can't run in budget.

Prerequisites

Assumes Loaded

Content (load on demand)

Task Routing

Templates

Scripts

Related

• parent skill: pro/marketing/growth-marketer/
• [[ab-testing-setup]]
• [[north-star-metric]]
• [[activation-framework]]

Decision tree

See content/06-decision-tree.xml. The tree maps observable input signals (artefact shape, freshness, scope) to either a run-the-methodology conclusion or a skip-this-methodology conclusion, with every leaf referencing a rule id from 01-core-rules.xml. Use it when the operator is unsure whether this methodology applies to the current task.