Jump to a popular page, or start typing.
    Talk to our team

    CONNECTIONS / Insightly / Insightly to Meta Offline CAPI

    From Insightly opportunities and pipeline stages to Meta's offline optimization.

    Connect Insightly and point Signals at your Insightly opportunities and pipeline stages; it credits dealer, branch, and phone sales to the Meta campaigns behind them as records change, hashed and consent-checked for Meta.

    Talk to our team Explore the setup

    insightly -> meta-offline-capi :: live

    1. ● insightly → meta.capi :: live
    2. > read closed_deals rows=22,174
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 19,513 matched

    WHAT THIS ENABLES

    Insightly to Meta Offline CAPI

    Meta Offline CAPI for Insightly: Signals credits dealer, branch, and phone sales to the Meta campaigns behind them straight from your Insightly opportunities and pipeline stages, hashed and consent-screened as records change.

    • Offline and in-store sales from your Insightly opportunities and pipeline stages activated for Meta, as Signals credits dealer, branch, and phone sales to the Meta campaigns behind them.
    • In-store and phone revenue joining Meta's optimization loop, drawn from your Insightly opportunities and pipeline stages by RevOps teams running Insightly.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

    The conversion happens off Meta, away from any pixel. Here is how Insightly closes the loop.

    Meta credits the campaign that sourced the conversion conversion happens off-platform Ad click on Meta CRM record sync recorded in Insightly S Signals hash · dedupe Offline Conversions API delivered · credited
    WHO THIS IS FOR

    Built for the teams that own the number.

    Considered-purchase brands closing revenue far from the browser, with the records already in Insightly opportunities, projects, and pipeline stages.

    RevOps teams running Insightly activating Meta's offline optimization straight from Insightly opportunities and pipeline stages.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Scoped OAuth access to Insightly, reading only your Insightly opportunities and pipeline stages to feed Meta's Offline Conversions API, sized for Meta's 62-day event window.

    2. Map

      Signals reads your Insightly opportunities and pipeline stages, and its columns map to Meta's Offline Conversions API in the visual mapper, hashed and checked for Meta's 62-day event window.

    3. Deliver

      On each run, Signals pulls your Insightly opportunities and pipeline stages, credits dealer, branch, and phone sales to the Meta campaigns behind them, and sends only the records that changed, with Meta's 62-day event window in the debugger.

    WHAT YOU GET

    What changes when the CSV goes away.

    Capability Manual CSV upload Datahash
    Reporting Offline sales sit in a separate export, reconciled by hand. Revenue counted in the same Offline CAPI reporting as web conversions.
    Deduplication A re-uploaded file risks counting the same conversion twice. Deduped delivery, so a resent record never counts as a second conversion.
    Match visibility Match quality is a guess until the numbers look off. Match rate reported per upload, tied to the source event set that produced it.
    Effort and latency An analyst exports and uploads on a manual cadence. Server-side and automatic the moment Insightly records the event.
    ON THE WIRE

    What Offline CAPI actually receives.

    signals :: insightly.meta-offline-capi :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversions source=insightly.closed_deals
    3. event_name "Purchase" · event_time 2026-07-16T14:25:26
    4. value 23990.00 · currency GBP
    5. em sha256 "1fa603…" · ph sha256 "eb2201…" · external_id "txn-70926"
    6. ✓ accepted match=88%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Insightly

    Insightly to Google OCI

    Google Offline Conversions for Insightly: Signals reconciles closed-won revenue to the…

    Learn more

    from Insightly

    Insightly to Google Store Sales

    Google Store Sales for Insightly: Signals matches in-person transactions to Google accounts…

    Learn more

    same use case

    ActiveCampaign to Meta Offline CAPI

    ActiveCampaign to Meta Offline CAPI: Signals reads your ActiveCampaign contacts and deal…

    Learn more

    generic

    Meta Offline CAPI

    Datahash ingests offline transactions from your POS, CRM, or warehouse and routes them to…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Insightly Meta Offline CAPI sync run?

    Delivery tracks Insightly, run by RevOps teams running Insightly: a near-real-time or scheduled sync of your Insightly opportunities and pipeline stages feeds Meta on that cadence. Each run sends only the records that changed, so campaign learning fed by real-world purchases holds up on Meta's 62-day event window. The live debugger confirms every delivery inline.

    What match rate should a Insightly-sourced Meta Offline CAPI batch expect?

    Match rate follows identifier coverage in your Insightly opportunities and pipeline stages, which RevOps teams running Insightly control, not Insightly itself. A record with a current hashed email or phone matches for Meta; one missing both cannot. First-run feedback from Offline Conversions API pinpoints Meta's 62-day event window, the number RevOps teams running Insightly tune against.

    NEXT STEP

    Insightly to Meta Offline CAPI, in production this week.

    Talk to our team All Insightly use cases