Connect the systems involved in the sale.
Sissel separates data sources from destinations. Bringing in an outcome never means it is automatically sent to an advertising platform.
Bring in customer outcomes
Use a supported CRM connection, the public events API, server-side conversion endpoints, or Zapier. Sissel records the source of each result.
Add advertising context
Connect Meta and Google to read campaign structure and spend. Existing browser tags can keep running alongside Sissel.
Send selected results back
Map the outcomes you want, test the destination, and enable live sending only after you have reviewed the comparison.
| System | Availability | Direction | Operating mode | Requirements | Documentation |
|---|---|---|---|---|---|
| Vigdis CRM | Beta | Into Sissel | Cursor-based polling | Read-only API key; contact/deal entities; field and stage mapping | Open |
| Events API | Beta | Into Sissel | Server push | Workspace token with events:write; stable deduplication key | Open |
| Zapier | Beta | Into Sissel | Zap trigger and actions | Workspace token; Zapier connection | Open |
| Meta Ads | Beta | Spend/hierarchy in; selected outcomes out | OAuth; Test or Live per outcome | Owner/admin; ad account and dataset; reconciliation before Live | Open |
| Google Ads | Beta | Spend/hierarchy in; selected outcomes out | OAuth; validateOnly/Test or Live per outcome | Owner/admin; operating account and conversion action IDs; reconciliation before Live | Open |
Have a system that is not listed?
Start with the public API or Zapier while a dedicated connector is evaluated.