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

    CONNECTIONS / Insightly / Insightly to TikTok Offline eAPI

    From Insightly opportunities and pipeline stages to TikTok's Offline Events API.

    Connect Insightly and point Signals at your Insightly opportunities and pipeline stages; it sends register and phone sales so offline joins TikTok's web optimization as records change, hashed and consent-checked for TikTok.

    Talk to our team Explore the setup

    insightly -> tiktok-offline-eapi :: live

    1. ● insightly → tiktok.eapi :: live
    2. > read closed_deals rows=26,803
    3. hash sha256(email,phone) consent=filtered
    4. route tiktok deliver
    5. ✓ delivered · 21,174 matched

    WHAT THIS ENABLES

    Insightly to TikTok Offline Events API

    TikTok Offline Events API for Insightly: Signals sends register and phone sales so offline joins TikTok's web optimization 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 TikTok, as Signals sends register and phone sales so offline joins TikTok's web optimization.
    • Counter sales deduped against any TikTok web event for the same buyer, 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 TikTok, away from any pixel. Here is how Insightly closes the loop.

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

    Built for the teams that own the number.

    Brands whose TikTok conversions finish at a till, not a checkout, with the records already in Insightly opportunities, projects, and pipeline stages.

    RevOps teams running Insightly activating TikTok's Offline Events API 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 TikTok's Offline Events API, sized for web-to-offline deduplication.

    2. Map

      Signals reads your Insightly opportunities and pipeline stages, and its columns map to TikTok's Offline Events API in the visual mapper, hashed and checked for web-to-offline deduplication.

    3. Deliver

      On each run, Signals pulls your Insightly opportunities and pipeline stages, sends register and phone sales so offline joins TikTok's web optimization, and sends only the records that changed, with web-to-offline deduplication 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 eAPI 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 eAPI actually receives.

    signals :: insightly.tiktok-offline-eapi :: wire

    1. ● signals :: event payload
    2. > POST /event/track source=insightly.closed_deals
    3. event "CompletePayment" · event_time 1784771825
    4. user.email sha256 "c02fa8…" · user.phone sha256 "6b91dd…"
    5. properties.value 37978 · properties.currency USD
    6. ✓ accepted · dedupe=event_id
    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 TikTok Offline eAPI

    ActiveCampaign to TikTok Offline Events API: Signals reads your ActiveCampaign contacts and…

    Learn more

    generic

    TikTok Offline eAPI

    Move your in-store and call-centre conversions to TikTok server-side, so TikTok can…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Insightly TikTok Offline eAPI 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 TikTok on that cadence. Each run sends only the records that changed, so a unified web-and-offline conversion view holds up on web-to-offline deduplication. The live debugger confirms every delivery inline.

    What match rate should a Insightly-sourced TikTok Offline eAPI 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 TikTok; one missing both cannot. First-run feedback from Offline Events API pinpoints web-to-offline deduplication, the number RevOps teams running Insightly tune against.

    NEXT STEP

    Insightly to TikTok Offline eAPI, in production this week.

    Talk to our team All Insightly use cases