The problem this solves
The Conversions API rewards exactly the discipline most teams cannot sustain: a consistent, stage-aware stream of outcomes. Sending only closed-won events teaches LinkedIn about a tiny, months-delayed slice of the funnel; sending everything undifferentiated teaches it mush. The useful signal is the funnel's structure itself - this email became an MQL, this one an opportunity, this one revenue - which requires a mapping between CRM stages and conversion rules, and a process that honors it every week.
The mapping is a one-time decision that tends never to get made, because it sits between teams: RevOps owns the stages, marketing owns the ad account, and the join belongs to nobody. And even where the mapping exists on a slide, the weekly execution - pull stage changes, translate to events, respect the windows, send - is precisely the recurring diligence that dies by month two.
This mission makes the mapping real and the execution standing. Once: stages paired to rules, missing rules created with fitted windows. Weekly: stage changes pulled from the CRM, translated into event batches per rule, and staged for your approval - the funnel's structure streaming to LinkedIn as long as the schedule runs.
How the mission runs
- Read both vocabularies. The CRM's pipeline stages on one side, the ad account's conversion rules on the other - laid out together, with the gaps and mismatches visible.
- Agree the mapping. The mission proposes the join - MQL to a LEAD rule, opportunity to a qualified rule, closed-won to revenue - and asks where judgment is needed. Your answers become the standing map.
- Create what is missing. Stages without a rule get one created via the Conversions API, named to match your vocabulary and windowed to your cycle length. Configuration only - no events flow yet.
- Set the weekly sync. A schedule pulls each week's stage changes from the CRM, translates them into event batches per the map - hashed emails, real timestamps, values where stages carry amounts - and stages each batch for approval.
- Approve and stream. Each week's batches wait in the Approvals queue with per-rule counts. Your yes streams them; acceptance is reported per batch, and the funnel's shape accrues on LinkedIn's side week after week.
The prompt
This is the exact objective the agent receives. Swap the obvious placeholders for your own domain, segment or channel and run it as-is from the console, Slack, or the API.
What comes back
A funnel-aware conversion stream: the stage-to-rule map decided once and recorded, missing rules created, and a weekly approval-gated sync that translates CRM stage changes into the differentiated events LinkedIn needs to optimize each campaign toward its actual job in the funnel.
Make it yours
- Start with two rules - qualified and won - and add stages once the rhythm holds; a simple map sustained beats a rich one abandoned.
- Add stage-appropriate values (pipeline value at opportunity, real value at close) so later stages carry proportionate weight.
- Pair with the true-ROAS deck, which becomes dramatically sharper once multi-stage events exist to report on.
Frequently asked questions
Why map stages instead of just streaming wins?
Volume and speed of learning. Wins are rare and months-delayed; MQLs and opportunities are plentiful and fresh. A stage-aware stream gives the algorithm early signals it can learn from now, calibrated by the later stages that confirm or correct them.
What happens when we rename or add a CRM stage?
The map is stored, versioned prose - rerun the mapping step and it reconciles: new stages get proposed rules, renamed ones get rejoined, and the weekly sync follows the updated map from its next run.
Can a batch go out without approval?
No. Every weekly batch stages and waits; an unapproved week simply does not stream, and the next week's batch notes the gap. The cadence is yours to keep - the mission makes keeping it a ten-second decision instead of an afternoon.