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

    CONNECTIONS / Close / Close to Meta Offline CAPI

    Close smart-view opportunities into Meta, built for Meta's offline optimization.

    Signals reads your Close smart-view opportunities through scoped OAuth access to Close, reading only your Close smart-view opportunities, then credits dealer, branch, and phone sales to the Meta campaigns behind them so Meta sees offline conversions without an export.

    Talk to our team Explore the setup

    close -> meta-offline-capi :: live

    1. ● close → meta.capi :: live
    2. > read closed_deals rows=29,326
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 23,168 matched

    WHAT THIS ENABLES

    Close to Meta Offline CAPI

    Close to Meta Offline CAPI: your Close smart-view opportunities, hashed and consent-checked, feed Meta as Signals credits dealer, branch, and phone sales to the Meta campaigns behind them as records change.

    • Signals credits dealer, branch, and phone sales to the Meta campaigns behind them, reading your Close smart-view opportunities as records change.
    • Campaign learning fed by real-world purchases, with no export step out of your Close smart-view opportunities.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    Meta credits the campaign that sourced the conversion conversion happens off-platform Ad click on Meta CRM record sync recorded in Close 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, working out of Close leads, calls, and smart-view opportunities.

    Inside-sales teams running Close who need in-store and phone revenue joining Meta's optimization loop out of Close smart-view opportunities.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Scoped OAuth access to Close, reading only your Close smart-view opportunities, mapped to Meta's Offline Conversions API and tuned for Meta's 62-day event window.

    2. Map

      Columns from your Close smart-view opportunities align to Meta's Offline Conversions API in the visual mapper, hashed as the sync runs and checked for Meta's 62-day event window.

    3. Deliver

      As records change, Signals reads your Close smart-view opportunities and credits dealer, branch, and phone sales to the Meta campaigns behind them, sends only the records that changed, with Meta's 62-day event window 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 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 Close records the event.
    ON THE WIRE

    What Offline CAPI actually receives.

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

    1. ● signals :: event payload
    2. > POST /offline_conversions source=close.closed_deals
    3. event_name "Purchase" · event_time 2026-07-16T19:57:29
    4. value 29281.00 · currency USD
    5. em sha256 "1fa603…" · ph sha256 "eb2201…" · external_id "txn-94849"
    6. ✓ accepted match=79%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Close

    Close to Google OCI

    Close to Google Offline Conversions: your Close smart-view opportunities, hashed and…

    Learn more

    from Close

    Close to Google Store Sales

    Close to Google Store Sales: your Close smart-view opportunities, hashed and…

    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 Close Meta Offline CAPI sync run?

    The pace follows your Close smart-view opportunities: Signals sends changes from Close to Meta as records change. Because it sends only the records that changed, in-store and phone revenue joining Meta's optimization loop stays current while inside-sales teams running Close keep Meta's 62-day event window in view. Delivery needs no export and no manual upload.

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

    In Close, match rate tracks the email and phone quality your Close smart-view opportunities carry. Clean identifiers land for Meta; blank ones never will. The first Offline Conversions API report shows inside-sales teams running Close where Meta's 62-day event window needs work, a data-quality task handled in Close.

    NEXT STEP

    Close to Meta Offline CAPI, in production this week.

    Talk to our team All Close use cases