CONNECTIONS / Insightly
Insightly + Datahash: pipeline wins become ad signals.
Insightly tracks a deal from first contact through the Project that delivers it, but ad platforms only ever see the form fill. Signals reads Opportunity stages and Project handoffs and turns them into conversion events and audiences on every platform you buy on.
- ● insightly :: signals live
- > read opportunities pipeline=sales stage=won rows=1,204
- > read projects linked_opportunity=won
- hash sha256(email,phone) scope=opportunities.read
- route meta · google · tiktok · snap
- ✓ 4 destinations synced · match 79%
The signal Insightly yields, and receives.
Every kind of signal that moves between Insightly and the platforms, through one hashed, deduplicated route.
- Offline conversions
- A Pipeline stage move, custom stages included, posts as a conversion event instead of waiting on a nightly export.
- Lead conversions
- When an Opportunity closes and Insightly opens the linked Project, that revenue routes back hashed to the campaign that sourced the deal.
- Custom audiences
- Organization and Contact lists become scheduled, hashed audiences without anyone exporting a CSV.
- Lead generation inbound
- A renamed or added custom field keeps flowing once it is mapped, so schema changes do not break the connection.
Pick your platform. Every use case for it, in one place.
Every way Insightly data moves, grouped by platform and ranked by how many use cases Insightly supports.
Google 5 
Meta 4 
Snap 4 
TikTok 4 
LinkedIn 3 
OpenAI 1 - Offline conversions Google Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Offline conversions Google Store Sales Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Google Enhanced Conversions for Leads Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Google Customer Match Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Google Forms Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions Meta Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Meta Conversions API for CRM Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Meta Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Meta Lead Ads Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions Snapchat Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Snapchat Leads Conversions API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Snapchat Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Snapchat Lead Generation Ads Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions TikTok Offline Events API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions TikTok CRM Events API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences TikTok Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation TikTok Lead Generation Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions LinkedIn Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions LinkedIn Leads Conversions API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Lead generation LinkedIn Lead Generation Forms Campaign lead submissions created as records in real time, deduped before creation.
From authorization to delivered signal.
-
Connect
Connect Insightly through a scoped API key limited to the objects you choose, revocable from Insightly at any time.
-
Map pipelines
Match each Pipeline stage, custom ones included, to the platform event it should fire in the visual mapper.
-
Hash and consent
SHA-256 hashing and consent checks run before any record leaves Insightly.
-
Deliver
Mapped destinations receive events on delivery, with per-stage match reporting in the debugger.
Insightly questions, answered.
Does Insightly's project-tracking side complicate the sync?
No. Signals reads the Opportunity and Pipeline objects that hold your sales data and treats the linked Project as a marker that a deal genuinely closed, not something to sync in its own right. You choose which stage transitions matter, and the project management side of Insightly stays untouched by the connection.
Can we map more than one Insightly Pipeline?
Yes. Insightly accounts commonly run separate Pipelines for different lead sources or business units, and the visual mapper treats each Pipeline's stages independently. A stage named Qualified in one Pipeline can map to a different platform event than a stage with the same name in another, so nothing gets flattened into one generic funnel.
Is our Insightly data copied into Datahash's systems?
No. Reads are scoped to the objects you select, hashing happens before anything leaves Insightly, and nothing is warehoused on our side afterward. A self-hosted Core deployment exists for teams that need data to stay inside their own perimeter entirely.
NEXT STEP
See your Insightly data working in every ad platform.
Ready to enable a use case, or still mapping what Insightly data could do? Our team helps you find the right place to start.
