CONNECTIONS / Sellsy

Sellsy + Datahash: paid invoices become ad signal.

Opportunity stages and invoice status sit inside Sellsy while ad platforms still optimize on the first form fill. Signals reads both and syncs qualified stages and paid revenue back to Meta, Google, TikTok, and Snap.

Talk to our team Explore use cases

sellsy :: live

● sellsy :: signals live
> read opportunities step=won rows=2,847
> read invoices status=paid
hash sha256(email,phone) scope=opportunities.read
route meta · google · tiktok · snap
✓ 4 destinations synced · match 79%

WHAT FLOWS THROUGH SELLSY

The signal Sellsy yields, and receives.

Every kind of signal that moves between Sellsy and the platforms, through one hashed, deduplicated route.

Offline conversions: A lead or opportunity moving to a qualifying stage in Sellsy posts as a conversion event, so campaigns optimize on pipeline movement instead of the first form fill.
Lead conversions: An opportunity marked won ties to its Sellsy invoice, and the paid amount leaves as an offline conversion with real revenue attached, not an estimated deal value.
Custom audiences: Contacts and companies leave Sellsy hashed before they reach any destination, so audience sync never puts a plaintext email or phone number on the wire.
Lead generation inbound: Custom fields defined on a Sellsy opportunity or contact map in the visual mapper, so a business-specific field reaches a destination without new integration code.

USE-CASE LISTING

Pick your platform. Every use case for it, in one place.

Every way Sellsy data moves, grouped by platform and ranked by how many use cases Sellsy supports.

Google 5

Meta 4

Snap 4

TikTok 4

LinkedIn 3

OpenAI 1

Offline conversions OpenAI Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.

HOW IT CONNECTS

From authorization to delivered signal.

Connect

Connect Sellsy with a scoped, reversible integration user.
Map

Select the records and stage changes to sync, and map fields in the visual mapper.
Verify

Choose destinations and verify sample events in the live debugger.
Go live

Go live with per-destination delivery status and match rate reporting.

FAQ

Sellsy questions, answered.

Which Sellsy events can trigger a conversion?

Any opportunity stage change or invoice status you pick can trigger a conversion, from a qualified opportunity through a paid invoice. Sellsy's pipeline steps map to platform events in the visual mapper, so a business selects the moments that count as leads, sales-qualified, and closed-won without touching the CRM's own setup. The mapping updates independently of the pipeline, so a renamed step does not break the feed.

Does invoice status matter, not the opportunity stage alone?

Yes, because an opportunity marked won is not always paid. Sellsy tracks invoices and payments separately from opportunities, and Signals can wait for invoice status to change before sending a purchase event with the actual paid value. That keeps ad platforms optimizing toward revenue that landed in the bank, not toward a deal that later cancels or gets partially refunded.

Is Sellsy contact data stored by Datahash?

No, contact identifiers are SHA-256 hashed at ingestion and Datahash Cloud does not store PII on host servers. Sellsy contacts and companies are read through a scoped, reversible integration user, hashed before they leave the pipeline, and matched against ad platform user bases without a plaintext copy existing anywhere in between. A self-hosted Core deployment keeps everything inside your own perimeter if required.

NEXT STEP