PipelineSignals

Guides / Stage mapping

Map stages, values & won/lost

This is where the magic gets configured: which pipeline moves tell your ad platforms "this one was real" — and what each deal was worth.

⏱ About 5 minutes
1

Pick the stages that mean something less is more

Open the location → Pipeline-stage → event mappings. Each stage gets a dropdown. A funnel that works well:

  • New / incoming stage → Lead — a fresh enquiry
  • Qualified → Qualified — a human said "this one's real"
  • Appointment booked → Appointment booked
  • Closed won → Closed won — sends the deal value 💰

Skip administrative stages ("Contacted", "Follow-up 2"). The platforms learn from progress, not busywork — three or four meaningful steps beat mapping everything.

2

Set the status triggers bottom of the editor

The Status triggers section fires when an opportunity is marked Won or Lost in any pipeline — even when nobody drags the card to a closed stage. That's most sales teams, most of the time.

  • Marked Won → Closed won — sends the deal value
  • Marked Lost → Opportunity lost — optional, but it teaches the platform what a bad lead looks like, which sharpens targeting
3

Deal values & currency automatic

Won events carry the opportunity's monetary value in your location's own currency — detected from the account's country (a UK account reports in GBP, not mislabelled dollars). Just keep values on your opportunities and the revenue side takes care of itself.

4

Test with one card 2 minutes

Create a throwaway opportunity, drag it into a mapped stage, then mark it Won. Watch the Recent conversion events log: each event shows delivery status, the match keys used, and the value sent. Green rows all the way down? You're live.

🛡️

No double-counting, ever. Each event name fires once per opportunity, no matter how it's triggered. If a card is dragged to "Closed won" and marked Won, the platform still receives exactly one purchase — your reported ROAS stays honest.

Pipeline Signals · dedup, retries, expiry windows and consent flags handled automatically