Diagnose missing conversions and "flying blind" measurement fast
Use this when the numbers don't match: ad platforms over/under-report, GA4 looks off, CRM revenue doesn't reconcile, or privacy changes (ATT/cookie loss/consent) have degraded tracking. It produces a root-cause shortlist, a "what to trust" guidance note, and a prioritized fix plan.
You are an OpenClaw agent helping a digital marketer triage an attribution/measurement incident. Ask only for the minimum inputs needed, then: - Define the primary source-of-truth outcome. - List the top likely causes (distinguish privacy/mechanics vs implementation). - Provide a prioritized fix plan (today/this week/this month). - End with a short "what we can and cannot conclude" note. Inputs (fill in): - Business model + primary conversion: - Channels involved: - Tools (GA4, CRM, ecommerce, tag manager): - What changed recently: - What looks wrong (numbers, date range, screenshots if available):
This recipe runs a structured attribution incident response: verify whether you have a measurement mechanics
issue (privacy limits, modeling, consent, dedupe rules) vs an implementation issue (UTMs/events/pixels/server-side).
Rebuild measurement around first-party data, consent, and signal loss
Create a privacy-first measurement architecture that accepts signal loss as permanent: define a durable KPI stack, implement consent-aware tracking priorities, and choose when to use modeled vs deterministic data. Outputs a blueprint plus an implementation backlog for a quarter.
Make GA4 usable by fixing event naming, parameters, and conversions
GA4 is event-based and flexible—but teams often ship messy event names, missing parameters, and inconsistent conversions. This recipe audits your event taxonomy and produces a clean naming standard, a conversion map, and a QA checklist.
A playbook for "stops at the same frame" and "freeze mid-render" failures
Renders freeze at a consistent percentage or frame — often caused by a bad clip, a heavy effect, a Fusion comp issue, or "stop render on error" settings. This recipe classifies the failure pattern and gives you a structured triage plan instead of blind re-exports.
Fix a common Premiere playback-lag issue caused by audio input device settings
Severe playback lag and stutter in Premiere Pro that looks like a codec performance problem but is actually caused by audio hardware input settings. This recipe provides a quick decision tree to test and fix the issue — often resolved in under a minute by switching the default input to "No Input."