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

    CONNECTIONS / Insightly / Insightly to Google Customer Match

    From Insightly opportunities and pipeline stages to Google Customer Match.

    Connect Insightly and point Signals at your Insightly opportunities and pipeline stages; it projects your segments into Google Ads as Customer Match lists as records change, hashed and consent-checked for Google Ads.

    Talk to our team Explore the setup

    insightly -> google-customer-match :: live

    1. ● insightly → google.match :: live
    2. > read segments rows=69,542
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 54,243 matched

    WHAT THIS ENABLES

    Insightly to Google Customer Match

    Google Customer Match for Insightly: Signals projects your segments into Google Ads as Customer Match lists straight from your Insightly opportunities and pipeline stages, hashed and consent-screened as records change.

    • Customer segments from your Insightly opportunities and pipeline stages 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 Insightly opportunities and pipeline stages by RevOps teams running Insightly.

    WHAT FLOWS WHERE

    Insightly to Customer Match, mapped.

    Signals reads the customer segments from your Insightly opportunities and pipeline stages as records change, hashes and screens each record, and posts the match-ready audiences to Google Ads' Customer Match API, keeping the serving-size threshold in view.

    Signals reads the customer segments from your Insightly opportunities and pipeline stages as records change, hashes and screens each record, and posts the match-ready audiences to Google Ads' Customer Match API, keeping the serving-size threshold in view.

    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 Insightly opportunities, projects, and pipeline stages.

    RevOps teams running Insightly activating Google Customer Match straight from Insightly opportunities and pipeline stages.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Scoped OAuth access to Insightly, reading only your Insightly opportunities and pipeline stages to feed Google Ads' Customer Match API, sized for the serving-size threshold.

    2. Map

      Signals reads your Insightly opportunities and pipeline stages, 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 Insightly opportunities and pipeline stages, projects your segments into Google Ads as Customer Match lists, and sends only the records 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 Insightly opportunities and pipeline stages and sends only the records that changed.

    Lists that self-maintain across syncs from your Insightly opportunities and pipeline stages, with API call volume steady because Signals sends only the records that changed.

    A per-run match report from Google Ads' Customer Match API on the serving-size threshold, straight out of your Insightly opportunities and pipeline stages.

    ON THE WIRE

    What Customer Match actually receives.

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

    1. ● signals :: audience upload
    2. > POST /user_list_operations source=insightly.segments
    3. operation ADD · user_list "segment_60093"
    4. hashed_email sha256 "b02cf1…" · hashed_phone sha256 "3ad990…"
    5. members_uploaded 69,542 · members_matched 54,243
    6. ✓ accepted match=78%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Insightly

    Insightly to Meta Custom Audience

    Meta Custom Audience for Insightly: Signals keeps Meta audiences synced as adds and…

    Learn more

    from Insightly

    Insightly to TikTok Custom Audience

    TikTok Custom Audience for Insightly: Signals delivers first-party segments to TikTok as…

    Learn more

    same use case

    ActiveCampaign to Google Customer Match

    ActiveCampaign to Google Customer Match: Signals reads your ActiveCampaign contacts and…

    Learn more

    generic

    Google Customer Match

    Datahash builds and refreshes Google Customer Match audiences from your CRM, warehouse, or…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Insightly Google Customer Match sync run?

    Delivery tracks Insightly, run by RevOps teams running Insightly: a near-real-time or scheduled sync of your Insightly opportunities and pipeline stages feeds Google Ads on that cadence. Each run sends only the records that changed, so lists that self-maintain across syncs holds up on the serving-size threshold. The live debugger confirms every delivery inline.

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

    Match rate follows identifier coverage in your Insightly opportunities and pipeline stages, which RevOps teams running Insightly control, not Insightly itself. A record with a current hashed email or phone matches for Google Ads; one missing both cannot. First-run feedback from Customer Match API pinpoints the serving-size threshold, the number RevOps teams running Insightly tune against.

    NEXT STEP

    Insightly to Google Customer Match, in production this week.

    Talk to our team All Insightly use cases