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

    CONNECTIONS / OVHcloud / OVHcloud to Meta Custom Audience

    From OVHcloud Object Storage files to Meta lookalike and suppression seeds.

    Signals reads your OVHcloud Object Storage files through a read-only S3 key scoped to the OVHcloud container you name, then keeps Meta audiences synced as adds and removals so lists never drift so Meta sees match-ready audiences without an export.

    Talk to our team Explore the setup

    ovhcloud -> meta-custom-audience :: live

    1. ● ovhcloud → meta.audience :: live
    2. > read segments rows=41,099
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 30,824 matched

    WHAT THIS ENABLES

    OVHcloud to Meta Custom Audience

    OVHcloud to Meta Custom Audience: your OVHcloud Object Storage files, hashed and consent-checked, feed Meta as Signals keeps Meta audiences synced as adds and removals so lists never drift each time a new file lands.

    • Signals keeps Meta audiences synced as adds and removals so lists never drift, reading your OVHcloud Object Storage files each time a new file lands.
    • Always-current lookalike seeds and exclusions, with no export step out of your OVHcloud Object Storage files.

    WHAT FLOWS WHERE

    OVHcloud to Custom Audience, mapped.

    Signals picks up the customer segments from your OVHcloud Object Storage files; 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 OVHcloud Object Storage files; 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, working out of OVHcloud Object Storage containers and objects.

    Teams on OVHcloud Object Storage who need lookalike seeds and suppression lists that track your live customer base out of OVHcloud Object Storage files.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only S3 key scoped to the OVHcloud container you name, mapped to Meta's Custom Audiences API and tuned for audience refresh cadence.

    2. Map

      Columns from your OVHcloud Object Storage files align to Meta's Custom Audiences API in the visual mapper, hashed as the file lands and checked for audience refresh cadence.

    3. Deliver

      Each time a new file lands, Signals reads your OVHcloud Object Storage files and keeps Meta audiences synced as adds and removals so lists never drift, processes only the newly dropped file, with audience refresh cadence watched in the debugger.

    WHAT YOU GET

    What ships with this use case.

    Lookalike seeds and suppression lists that track your live customer base from your OVHcloud Object Storage files, delivered each time a new file lands.

    Always-current lookalike seeds and exclusions out of your OVHcloud Object Storage files, delivered each time a new file lands without transfer overhead climbing.

    Match feedback on audience refresh cadence from Meta's Custom Audiences API each run, tied back to your OVHcloud Object Storage files.

    ON THE WIRE

    What Custom Audience actually receives.

    signals :: ovhcloud.meta-custom-audience :: wire

    1. ● signals :: audience upload
    2. > POST /customaudiences source=ovhcloud.segments
    3. schema ["EMAIL_SHA256","PHONE_SHA256"]
    4. num_received 41,099 · num_invalid_entries -97
    5. audience_id "1684254" · session "upsert"
    6. ✓ accepted match=75%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from OVHcloud

    OVHcloud to Google Customer Match

    OVHcloud to Google Customer Match: your OVHcloud Object Storage files, hashed and…

    Learn more

    from OVHcloud

    OVHcloud to TikTok Custom Audience

    OVHcloud to TikTok Custom Audience: your OVHcloud Object Storage files, hashed and…

    Learn more

    same use case

    ActiveCampaign to Meta Custom Audience

    ActiveCampaign to Meta Custom Audience: Signals reads your ActiveCampaign contacts and deal…

    Learn more

    generic

    Meta Custom Audience

    Build and refresh Meta Custom Audiences from your CRM, warehouse, or SingleView, with…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the OVHcloud Meta Custom Audience sync run?

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

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

    Match rate follows identifier coverage in your OVHcloud Object Storage files, which teams on OVHcloud Object Storage control, not OVHcloud itself. A record with a current hashed email or phone matches for Meta; one missing both cannot. First-run feedback from Custom Audiences API pinpoints audience refresh cadence, the number teams on OVHcloud Object Storage tune against.

    NEXT STEP

    OVHcloud to Meta Custom Audience, in production this week.

    Talk to our team All OVHcloud use cases