Turn CRM activity into useful marketing outcomes
Map leads, qualified leads, opportunities and sales without confusing routine CRM activity with business results.
An outcome is not every CRM change
CRMs produce a large stream of record creation, field updates, tasks and stage changes. Only a small part of that stream represents results you should compare by campaign or send back to an ad platform. An outcome should have a stable business meaning that survives changes to the CRM interface.
Map the funnel your team actually uses
| Outcome | Typical meaning | Useful for |
|---|---|---|
| Lead | A new identifiable enquiry entered the customer system | Checking acquisition volume and tracking coverage |
| Qualified lead | Sales accepted the person against a written qualification rule | Comparing lead quality and paid acquisition |
| Opportunity | A real commercial process or deal was opened | Longer funnels where qualification alone is too early |
| Won deal | The opportunity reached an agreed closed-won state | Pipeline performance and customer acquisition cost |
| Sale | A completed transaction or order with a stable value | Revenue, return on ad spend and conversion feedback |
You may use fewer stages. A simple business can start with qualified lead and sale. The names in Sissel should describe the shared meaning, while the connector mapping translates your CRM’s own fields and stages into that meaning.
Information each outcome needs
- Stable record identity
A source-scoped ID that lets repeated delivery update the same logical result instead of creating copies.
- Outcome time
The time the business result actually happened, not merely when a sync later delivered it.
- Person identity
A tracking token, external ID, email or phone that can link the result to known journey evidence.
- Outcome type
The canonical meaning—lead, qualified lead, opportunity, won deal or sale.
- Value and currency
For revenue outcomes, keep both together and do not combine unlike currencies without an explicit conversion policy.
- Revision behavior
Define what happens when value, status or cancellation changes after the first event.
Example mapping
| CRM condition | Sissel outcome | Send to ads? |
|---|---|---|
| Contact created from a real enquiry | Lead | Usually keep off at first |
| Sales accepted at a documented qualification step | Qualified lead | Good first candidate after testing |
| Deal opened with expected value | Opportunity | Useful when the definition is consistent |
| Deal marked won | Won deal | Useful for long-cycle optimization and reporting |
| Order completed with amount and currency | Sale | Good candidate when revisions and refunds are understood |
Do not send every stage simply because the integration makes it possible. More events are not automatically better signals. Start with the outcome that best balances business value, enough volume and a dependable definition.
Test the complete change path
- 1Create one test person
Use a controlled website journey so the expected visitor and campaign are known.
- 2Trigger the CRM condition
Move the record through the exact field or stage transition used by the mapping.
- 3Inspect the received outcome
Confirm type, time, identity, source record and value before checking attribution.
- 4Repeat the source event
Verify that an ordinary retry does not create a second logical outcome.
- 5Change the record
If values or status can change, confirm the revision appears as expected and remains explainable.