Build: defining a segment precisely
An audience is only as good as its definition. "Cart abandoners" sounds simple until you specify: abandoned how long ago, did they view a product page first, does a completed purchase in the same session exclude them, and does the definition run off your event stream or a CRM export that is already stale by the time it syncs. We define every segment against your actual event and customer data model, not a generic template, and document the definition so it can be audited later.
Sync: getting the segment into each platform's own audience mechanism
Each ad platform has its own audience API and its own matching mechanics. The three mechanisms this practice implements most:
- Customer Match (Google). Upload hashed customer identifiers - email, phone, mailing address - matched to signed-in Google users, usable for targeting or exclusion across Search, Display, YouTube, and Gmail.
- Custom Audiences (Meta, TikTok, LinkedIn, Snapchat, Pinterest). Each platform's version of uploading your own customer or event data (a customer list, a website-visitor pixel audience, an app-user list) matched directly to real accounts on that platform.
- Lookalike / similar audiences. Built by the platform's own algorithm from a seed Custom Audience - typically your best customers - to reach new people who resemble that seed without being existing customers themselves. Meta calls these Lookalike Audiences, Google calls its version Similar Segments, LinkedIn calls its version Lookalike Audiences.
The sync itself can run as a one-time upload, a scheduled batch (hourly, daily), or a real-time API push tied to your event stream - the right cadence depends on how time-sensitive the segment is, covered per use case below.
Suppress: the audience that says "don't show this ad"
Suppression is targeting's inverse - explicitly excluding a segment from a campaign, most commonly existing customers from an acquisition campaign that is paying to reacquire people who already converted. A suppression audience needs the same precise definition and sync freshness as a targeting audience; a stale suppression list still wastes spend on people it should already be excluding.
Verify: confirming the platform actually applied it
An audience upload that returns success from the platform's API does not guarantee the audience is usable - match rate, minimum size thresholds, and processing delays all affect whether a campaign can actually target (or exclude) it. Verification means checking the platform's own audience size and match-rate reporting, not just the upload confirmation.
The use cases this builds toward
Mechanics alone are not the point - the segments worth building are. The flagship pattern across every use case below is the same: define the segment technically, sync it, then change the creative and offer to match what that specific audience actually needs, which is rarely the same message you would send a cold prospect.