Jump to a popular page, or start typing.

    Custom Audiences

    Ship the right audience to every ad platform, automatically.

    Datahash builds and refreshes custom audiences across Meta, Google, Snap, TikTok, LinkedIn, and X from your CRM, warehouse, or SingleView.

    offerings.custom-audiences :: live

    1. ● offerings.custom-audiences :: live
    2. > segment high_ltv_repeat size=48,200
    3. hash sha256(em,ph) · add 1,240 · remove 380
    4. sync meta · google · snap · tiktok · linkedin · x
    5. ✓ 6/6 audiences updated
    WHO THIS IS FOR

    Built for the teams that own the number.

    Teams suppressing existing customers from acquisition campaigns.

    Brands seeding lookalikes from high-LTV cohorts.

    Lifecycle marketers reactivating dormant users and running cross-sell.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Source connection to CRM, warehouse, or SingleView.

    2. Segment

      Audience segmentation and hash prep.

    3. Sync

      Scheduled or event-driven sync to each destination.

    4. Operate

      Suppression lists, lookalike seeds, and retention audiences maintained automatically.

    THE PIPELINE

    What flows where.

    Your sources on the left, verified destinations on the right. Signals hashes, dedupes, and routes in the middle.

    crm.list warehouse singleview Signals hash · dedupe· route meta.audience google.cust_match snap.audience tiktok.audience [ one pipeline, every destination ]
    WHAT YOU GET

    What ships with this offering.

    One segment definition syncing to six ad platforms.

    Suppression, lookalike, reactivation, and cross-sell audiences kept current.

    Hashed identifier handling per each platform's spec.

    ON THE WIRE

    What the platform actually receives.

    Identifiers are hashed with SHA-256 at source. The payload the destination sees never contains raw PII.

    signals :: custom-audiences :: wire

    1. ● signals :: audience payload
    2. > sync audience "high_ltv_repeat" · members 48,200
    3. em sha256 "c81f04…" · ph sha256 "2d6b77…"
    4. meta.custom_audience +1,240 / -380 · 200 OK
    5. google.customer_match +1,240 / -380 · 200 OK
    6. ✓ synced 6/6 destinations · pii=hashed-at-source
    FAQ

    Questions your team will ask.

    How large can an audience be?

    Platform limits are generous, typically in the millions of members, and Datahash chunks uploads to stay within each platform's API constraints. Minimum sizes matter more in practice; we flag segments too small to serve reliably, since a platform may suppress a custom audience entirely rather than run a campaign against too few matched users.

    How often do audiences refresh?

    On the cadence you choose, from event-driven near real time to daily or weekly batches, set per audience rather than fixed platform-wide. Refreshes send incremental adds and removes, so audiences track your source of truth without full re-uploads, and a customer who churns or opts out drops from the audience on the next cycle.

    Do you support Segments?

    Yes. Segments built in Datahash, including predictive and rule-based cohorts, are first-class audience sources and sync to every connected destination the same way a CRM list or warehouse export does. A propensity-to-churn segment or a high-LTV cohort updates on its normal refresh schedule and reaches Meta, Google, Snap, TikTok, LinkedIn, and X together.

    NEXT STEP

    Live in fifteen minutes. Measurable in a week.

    Talk to our team of solutions engineers. We map your source data, propose an integration plan, and give you a live setup in the same call where possible.