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

    CONNECTIONS / Close / Close to Google Store Sales

    Close smart-view opportunities into Google Ads, built for Google Store Sales matching.

    Signals reads your Close smart-view opportunities through scoped OAuth access to Close, reading only your Close smart-view opportunities, then matches in-person transactions to Google accounts as store-sales conversions so Google Ads sees offline conversions without an export.

    Talk to our team Explore the setup

    close -> google-store-sales :: live

    1. ● close → google.sales :: live
    2. > read closed_deals rows=24,422
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 19,538 matched

    WHAT THIS ENABLES

    Close to Google Store Sales

    Close to Google Store Sales: your Close smart-view opportunities, hashed and consent-checked, feed Google Ads as Signals matches in-person transactions to Google accounts as store-sales conversions as records change.

    • Signals matches in-person transactions to Google accounts as store-sales conversions, reading your Close smart-view opportunities as records change.
    • Store visits reconciled to campaign spend, 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 Google, away from any pixel. Here is how Close closes the loop.

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

    Inside-sales teams running Close who need counter and showroom revenue inside the same ROAS view as online orders 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 Google Ads' Store Sales Direct API and tuned for the store-sales match rate.

    2. Map

      Columns from your Close smart-view opportunities align to Google Ads' Store Sales Direct API in the visual mapper, hashed as the sync runs and checked for the store-sales match rate.

    3. Deliver

      As records change, Signals reads your Close smart-view opportunities and matches in-person transactions to Google accounts as store-sales conversions, sends only the records that changed, with the store-sales match rate 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 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 Close records the event.
    ON THE WIRE

    What Store Sales actually receives.

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

    1. ● signals :: store sales upload
    2. > POST /offline_user_data_jobs source=close.closed_deals
    3. transaction_time 2026-07-19T10:30:30 · transaction_amount_micros 37128000000
    4. currency_code GBP
    5. hashed_email sha256 "6d2e91…" · hashed_last_name sha256 "cc410a…"
    6. ✓ accepted match=80%
    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 Meta Offline CAPI

    Close to Meta Offline CAPI: your Close smart-view opportunities, hashed and…

    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 Close Google Store Sales sync run?

    The pace follows your Close smart-view opportunities: Signals sends changes from Close to Google Ads as records change. Because it sends only the records that changed, counter and showroom revenue inside the same ROAS view as online orders stays current while inside-sales teams running Close keep the store-sales match rate in view. Delivery needs no export and no manual upload.

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

    In Close, match rate tracks the email and phone quality your Close smart-view opportunities carry. Clean identifiers land for Google Ads; blank ones never will. The first Store Sales Direct API report shows inside-sales teams running Close where the store-sales match rate needs work, a data-quality task handled in Close.

    NEXT STEP

    Close to Google Store Sales, in production this week.

    Talk to our team All Close use cases