Jump to a popular page, or start typing.

    CONNECTIONS / Magento / Magento to Google Customer Match

    Your Magento orders, wired to Google Customer Match.

    Connect Magento and point Signals at your Magento orders; it projects your segments into Google Ads as Customer Match lists as orders complete, hashed and consent-checked for Google Ads.

    magento -> google-customer-match :: live

    1. ● magento → google.match :: live
    2. > read segments rows=40,643
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 36,579 matched

    WHAT THIS ENABLES

    Magento to Google Customer Match

    Magento to Google Customer Match: Signals reads your Magento orders and projects your segments into Google Ads as Customer Match lists, hashed and consent-checked as orders complete.

    • Customer segments from your Magento orders activated for Google Ads, as Signals projects your segments into Google Ads as Customer Match lists.
    • Customer Match lists that add joiners and drop lapsed members each sync, drawn from your Magento orders by merchants on Adobe Commerce (Magento).

    WHAT FLOWS WHERE

    Magento to Customer Match, mapped.

    Signals reads the customer segments from your Magento orders; Signals hashes and consent-screens each record before Google Ads' Customer Match API accepts the match-ready audiences for the serving-size threshold.

    Signals reads the customer segments from your Magento orders; Signals hashes and consent-screens each record before Google Ads' Customer Match API accepts the match-ready audiences for the serving-size threshold.

    WHO THIS IS FOR

    Built for the teams that own the number.

    Growth teams feeding Google audiences from governed first-party data, with the records already in Magento orders, customers, and quotes.

    Merchants on Adobe Commerce (Magento) activating Google Customer Match straight from Magento orders.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Scoped API access to Magento, reading only your Magento orders to feed Google Ads' Customer Match API, sized for the serving-size threshold.

    2. Map

      Signals reads your Magento orders, and its columns map to Google Ads' Customer Match API in the visual mapper, hashed and checked for the serving-size threshold.

    3. Deliver

      On each run, Signals pulls your Magento orders, projects your segments into Google Ads as Customer Match lists, and sends only the orders that changed, with the serving-size threshold in the debugger.

    WHAT YOU GET

    What ships with this use case.

    Customer Match lists that add joiners and drop lapsed members each sync on every run, as Signals reads your Magento orders and sends only the orders that changed.

    Lists that self-maintain across syncs from your Magento orders, with API call volume steady because Signals sends only the orders that changed.

    A per-run match report from Google Ads' Customer Match API on the serving-size threshold, straight out of your Magento orders.

    ON THE WIRE

    What Customer Match actually receives.

    signals :: magento.google-customer-match :: wire

    1. ● signals :: audience upload
    2. > POST /user_list_operations source=magento.segments
    3. operation ADD · user_list "segment_42563"
    4. hashed_email sha256 "b02cf1…" · hashed_phone sha256 "3ad990…"
    5. members_uploaded 40,643 · members_matched 36,579
    6. ✓ accepted match=90%
    FAQ

    Asked on almost every call.

    How often does the Magento Google Customer Match sync run?

    You set the cadence, from near-real-time to a nightly Magento sync of your Magento orders into Google Ads. Since Signals sends only the orders that changed, Customer Match lists that add joiners and drop lapsed members each sync keeps pace and merchants on Adobe Commerce (Magento) watch the serving-size threshold. One scoped connection sets it up, cadence adjustable later.

    What match rate should a Magento-sourced Google Customer Match batch expect?

    In Magento, match rate tracks the email and phone quality your Magento orders carry. Clean identifiers land for Google Ads; blank ones never will. The first Customer Match API report shows merchants on Adobe Commerce (Magento) where the serving-size threshold needs work, a data-quality task handled in Magento.

    NEXT STEP

    Magento to Google Customer Match, in production this week.