Jump to a popular page, or start typing.

    CONNECTIONS / Google Sheets / Google Sheets to Meta Custom Audience

    Your Google Sheets rows, wired to Meta lookalike and suppression seeds.

    Connect Google Sheets and point Signals at your Google Sheets rows; it keeps Meta audiences synced as adds and removals so lists never drift each time a new file lands, hashed and consent-checked for Meta.

    google-sheet -> meta-custom-audience :: live

    1. ● google sheets → meta.audience :: live
    2. > read segments rows=37,390
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 27,669 matched

    WHAT THIS ENABLES

    Google Sheets to Meta Custom Audience

    Google Sheets to Meta Custom Audience: Signals reads your Google Sheets rows and keeps Meta audiences synced as adds and removals so lists never drift, hashed and consent-checked each time a new file lands.

    • Customer segments from your Google Sheets rows activated for Meta, as Signals keeps Meta audiences synced as adds and removals so lists never drift.
    • Lookalike seeds and suppression lists that track your live customer base, drawn from your Google Sheets rows by ops teams maintaining Google Sheets.

    WHAT FLOWS WHERE

    Google Sheets to Custom Audience, mapped.

    Signals picks up the customer segments from your Google Sheets rows; Signals hashes and consent-screens each record before Meta's Custom Audiences API accepts the match-ready audiences for audience refresh cadence.

    Signals picks up the customer segments from your Google Sheets rows; Signals hashes and consent-screens each record before Meta's Custom Audiences API accepts the match-ready audiences for audience refresh cadence.

    WHO THIS IS FOR

    Built for the teams that own the number.

    Performance teams running first-party suppression and lookalike seeds, with the records already in Google Sheets tabs and ranges.

    Ops teams maintaining Google Sheets activating Meta lookalike and suppression seeds straight from Google Sheets rows.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Read-only OAuth access to the Google Sheet you name to feed Meta's Custom Audiences API, sized for audience refresh cadence.

    2. Map

      Signals picks up your Google Sheets rows, and its columns map to Meta's Custom Audiences API in the visual mapper, hashed and checked for audience refresh cadence.

    3. Deliver

      On each run, Signals pulls your Google Sheets rows, keeps Meta audiences synced as adds and removals so lists never drift, and processes only the newly dropped file, with audience refresh cadence in the debugger.

    WHAT YOU GET

    What ships with this use case.

    Lookalike seeds and suppression lists that track your live customer base on every run, as Signals reads your Google Sheets rows and processes only the newly dropped file.

    Always-current lookalike seeds and exclusions from your Google Sheets rows, with transfer overhead steady because Signals processes only the newly dropped file.

    A per-run match report from Meta's Custom Audiences API on audience refresh cadence, straight out of your Google Sheets rows.

    ON THE WIRE

    What Custom Audience actually receives.

    signals :: google-sheet.meta-custom-audience :: wire

    1. ● signals :: audience upload
    2. > POST /customaudiences source=google-sheet.segments
    3. schema ["EMAIL_SHA256","PHONE_SHA256"]
    4. num_received 37,390 · num_invalid_entries -225
    5. audience_id "1678533" · session "upsert"
    6. ✓ accepted match=74%
    FAQ

    Asked on almost every call.

    How often does the Google Sheets Meta Custom Audience sync run?

    You set the cadence, from near-real-time to a nightly Google Sheets sync of your Google Sheets rows into Meta. Since Signals processes only the newly dropped file, lookalike seeds and suppression lists that track your live customer base keeps pace and ops teams maintaining Google Sheets watch audience refresh cadence. One scoped connection sets it up, cadence adjustable later.

    What match rate should a Google Sheets-sourced Meta Custom Audience batch expect?

    In Google Sheets, match rate tracks the email and phone quality your Google Sheets rows carry. Clean identifiers land for Meta; blank ones never will. The first Custom Audiences API report shows ops teams maintaining Google Sheets where audience refresh cadence needs work, a data-quality task handled in Google Sheets.

    NEXT STEP

    Google Sheets to Meta Custom Audience, in production this week.