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

    CONNECTIONS / Kommo / Kommo to Google Store Sales

    Your Kommo messenger pipelines, wired to Google Store Sales matching.

    Connect Kommo and point Signals at your Kommo messenger pipelines; it matches in-person transactions to Google accounts as store-sales conversions as records change, hashed and consent-checked for Google Ads.

    Talk to our team Explore the setup

    kommo -> google-store-sales :: live

    1. ● kommo → google.sales :: live
    2. > read closed_deals rows=36,539
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 30,327 matched

    WHAT THIS ENABLES

    Kommo to Google Store Sales

    Kommo to Google Store Sales: your Kommo messenger pipelines, hashed and consent-checked, feed Google Ads as Signals matches in-person transactions to Google accounts as store-sales conversions as records change.

    • Offline and in-store sales from your Kommo messenger pipelines activated for Google Ads, as Signals matches in-person transactions to Google accounts as store-sales conversions.
    • Counter and showroom revenue inside the same ROAS view as online orders, drawn from your Kommo messenger pipelines by conversational-sales teams on Kommo.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    Google credits the campaign that sourced the conversion conversion happens off-platform Ad click on Google CRM record sync recorded in Kommo S Signals hash · dedupe Store Sales Direct API delivered · credited
    WHO THIS IS FOR

    Built for the teams that own the number.

    Omnichannel retailers reconciling point-of-sale against Google spend, with the records already in Kommo leads and messenger-driven pipelines.

    Conversational-sales teams on Kommo activating Google Store Sales matching straight from Kommo messenger pipelines.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Scoped OAuth access to Kommo, reading only your Kommo messenger pipelines to feed Google Ads' Store Sales Direct API, sized for the store-sales match rate.

    2. Map

      Signals reads your Kommo messenger pipelines, and its columns map to Google Ads' Store Sales Direct API in the visual mapper, hashed and checked for the store-sales match rate.

    3. Deliver

      On each run, Signals pulls your Kommo messenger pipelines, matches in-person transactions to Google accounts as store-sales conversions, and sends only the records that changed, with the store-sales match rate 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 Store Sales 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 Kommo records the event.
    ON THE WIRE

    What Store Sales actually receives.

    signals :: kommo.google-store-sales :: wire

    1. ● signals :: store sales upload
    2. > POST /offline_user_data_jobs source=kommo.closed_deals
    3. transaction_time 2026-07-16T00:29:33 · transaction_amount_micros 12721000000
    4. currency_code USD
    5. hashed_email sha256 "6d2e91…" · hashed_last_name sha256 "cc410a…"
    6. ✓ accepted match=83%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Kommo

    Kommo to Google OCI

    Kommo to Google Offline Conversions: your Kommo messenger pipelines, hashed and…

    Learn more

    from Kommo

    Kommo to Meta Offline CAPI

    Kommo to Meta Offline CAPI: your Kommo messenger pipelines, hashed and consent-checked,…

    Learn more

    same use case

    ActiveCampaign to Google Store Sales

    ActiveCampaign to Google Store Sales: Signals reads your ActiveCampaign contacts and deal…

    Learn more

    generic

    Google Store Sales

    Datahash automates Store Sales Direct and Store Sales Customer Match uploads from your POS…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Kommo Google Store Sales sync run?

    Delivery tracks Kommo, run by conversational-sales teams on Kommo: a near-real-time or scheduled sync of your Kommo messenger pipelines feeds Google Ads on that cadence. Each run sends only the records that changed, so store visits reconciled to campaign spend holds up on the store-sales match rate. The live debugger confirms every delivery inline.

    What match rate should a Kommo-sourced Google Store Sales batch expect?

    Match rate follows identifier coverage in your Kommo messenger pipelines, which conversational-sales teams on Kommo control, not Kommo itself. A record with a current hashed email or phone matches for Google Ads; one missing both cannot. First-run feedback from Store Sales Direct API pinpoints the store-sales match rate, the number conversational-sales teams on Kommo tune against.

    NEXT STEP

    Kommo to Google Store Sales, in production this week.

    Talk to our team All Kommo use cases