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

    CONNECTIONS / DigitalOcean / DigitalOcean to Meta Custom Audience

    Your DigitalOcean Spaces objects, wired to Meta lookalike and suppression seeds.

    Signals reads your DigitalOcean Spaces objects through a read-only Spaces key scoped to the bucket 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

    digitalocean -> meta-custom-audience :: live

    1. ● digitalocean → meta.audience :: live
    2. > read segments rows=12,937
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 10,738 matched

    WHAT THIS ENABLES

    DigitalOcean to Meta Custom Audience

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

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

    WHAT FLOWS WHERE

    DigitalOcean to Custom Audience, mapped.

    Each sync hands the customer segments from your DigitalOcean Spaces objects to Signals, which hashes and filters every record, then Meta's Custom Audiences API logs the match-ready audiences for audience refresh cadence.

    Each sync hands the customer segments from your DigitalOcean Spaces objects to Signals, which hashes and filters every record, then Meta's Custom Audiences API logs 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 DigitalOcean Spaces buckets and objects.

    Teams landing exports in DigitalOcean Spaces who need lookalike seeds and suppression lists that track your live customer base out of DigitalOcean Spaces objects.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

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

    2. Map

      Columns from your DigitalOcean Spaces objects 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 DigitalOcean Spaces objects 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 DigitalOcean Spaces objects, delivered each time a new file lands.

    Always-current lookalike seeds and exclusions out of your DigitalOcean Spaces objects, 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 DigitalOcean Spaces objects.

    ON THE WIRE

    What Custom Audience actually receives.

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

    1. ● signals :: audience upload
    2. > POST /customaudiences source=digitalocean.segments
    3. schema ["EMAIL_SHA256","PHONE_SHA256"]
    4. num_received 12,937 · num_invalid_entries 150
    5. audience_id "1648768" · session "upsert"
    6. ✓ accepted match=83%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from DigitalOcean

    DigitalOcean to Google Customer Match

    DigitalOcean to Google Customer Match: Signals reads your DigitalOcean Spaces objects and…

    Learn more

    from DigitalOcean

    DigitalOcean to TikTok Custom Audience

    DigitalOcean to TikTok Custom Audience: Signals reads your DigitalOcean Spaces objects 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 DigitalOcean Meta Custom Audience sync run?

    The pace follows your DigitalOcean Spaces objects: Signals sends changes from DigitalOcean to Meta each time a new file lands. Because it processes only the newly dropped file, lookalike seeds and suppression lists that track your live customer base stays current while teams landing exports in DigitalOcean Spaces keep audience refresh cadence in view. Delivery needs no export and no manual upload.

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

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

    NEXT STEP

    DigitalOcean to Meta Custom Audience, in production this week.

    Talk to our team All DigitalOcean use cases