Jump to a popular page, or start typing.

    CONNECTIONS / Bitrix24 / Bitrix24 to TikTok Offline eAPI

    Bitrix24 deals and smart processes into TikTok, built for TikTok's Offline Events API.

    Signals reads your Bitrix24 deals and smart processes through scoped OAuth access to Bitrix24, reading only your Bitrix24 deals and smart processes, then sends register and phone sales so offline joins TikTok's web optimization so TikTok sees offline conversions without an export.

    bitrix24 -> tiktok-offline-eapi :: live

    1. ● bitrix24 → tiktok.eapi :: live
    2. > read closed_deals rows=64,075
    3. hash sha256(email,phone) consent=filtered
    4. route tiktok deliver
    5. ✓ delivered · 52,542 matched

    WHAT THIS ENABLES

    Bitrix24 to TikTok Offline Events API

    Bitrix24 to TikTok Offline Events API: your Bitrix24 deals and smart processes, hashed and consent-checked, feed TikTok as Signals sends register and phone sales so offline joins TikTok's web optimization as records change.

    • Signals sends register and phone sales so offline joins TikTok's web optimization, reading your Bitrix24 deals and smart processes as records change.
    • A unified web-and-offline conversion view, with no export step out of your Bitrix24 deals and smart processes.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    TikTok credits the campaign that sourced the conversion conversion happens off-platform Ad click on TikTok CRM record sync recorded in Bitrix24 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, working out of Bitrix24 deals, leads, and smart processes.

    Sales operations teams on Bitrix24 who need counter sales deduped against any TikTok web event for the same buyer out of Bitrix24 deals and smart processes.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Scoped OAuth access to Bitrix24, reading only your Bitrix24 deals and smart processes, mapped to TikTok's Offline Events API and tuned for web-to-offline deduplication.

    2. Map

      Columns from your Bitrix24 deals and smart processes align to TikTok's Offline Events API in the visual mapper, hashed as the sync runs and checked for web-to-offline deduplication.

    3. Deliver

      As records change, Signals reads your Bitrix24 deals and smart processes and sends register and phone sales so offline joins TikTok's web optimization, sends only the records that changed, with web-to-offline deduplication watched 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 Bitrix24 records the event.
    ON THE WIRE

    What Offline eAPI actually receives.

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

    1. ● signals :: event payload
    2. > POST /event/track source=bitrix24.closed_deals
    3. event "CompletePayment" · event_time 1783902284
    4. user.email sha256 "c02fa8…" · user.phone sha256 "6b91dd…"
    5. properties.value 25273 · properties.currency AED
    6. ✓ accepted · dedupe=event_id
    FAQ

    Asked on almost every call.

    How often does the Bitrix24 TikTok Offline eAPI sync run?

    You set the cadence, from near-real-time to a nightly Bitrix24 sync of your Bitrix24 deals and smart processes into TikTok. Since Signals sends only the records that changed, counter sales deduped against any TikTok web event for the same buyer keeps pace and sales operations teams on Bitrix24 watch web-to-offline deduplication. One scoped connection sets it up, cadence adjustable later.

    What match rate should a Bitrix24-sourced TikTok Offline eAPI batch expect?

    Match rate follows identifier coverage in your Bitrix24 deals and smart processes, which sales operations teams on Bitrix24 control, not Bitrix24 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 sales operations teams on Bitrix24 tune against.

    NEXT STEP

    Bitrix24 to TikTok Offline eAPI, in production this week.