Records and identifiers
An audience starts with source records, such as a customer export, CRM segment, or a list of target contacts. The source can contain emails, phone numbers, company identifiers, or other fields supported by the destination. Each platform defines its accepted identifiers and formats. Preparation resolves duplicates, removes suppressed records, and normalizes the selected fields. Some upload paths require hashed identifiers, while others accept raw fields and prepare them for the platform. The selected tool’s contract determines the expected form. Applying another hash to an already hashed identifier prevents a valid match. A Play can combine these checks with enrichment tools and retain an inspectable dataset. The retained source ID connects each uploaded row with the record and evidence that produced it. Enrichment adds candidate identifiers, not permission to use them for advertising.Account connections and platform behavior
The Ads audiences page shows the three platforms, their connection state, and example workflows. Workspace owners and admins connect the required accounts through Integrations. Provider account permissions and platform terms also apply. An audience object belongs to a specific advertising account. Deepline tools create or select that object, synchronize its members, and retrieve its reported status. Retaining the account and audience IDs lets later updates target the same object.
Account selection, consent fields, identifier normalization, and processing states differ by platform.
The audience guide contains those operational rules.
The per-action Technical reference contains the current request fields.
Uploads and matching
An accepted upload confirms that the platform accepted a request or file. It does not establish that every row matched a person or company. Processing can continue after the upload response, and invalid rows can appear separately. Deepline can retrieve the status that the platform exposes. Matched counts can remain unavailable, delayed, or reported as an approximate range. A missing count is an unknown result, not a zero or a match-rate estimate. Your team reviews the account, source population, suppression, identifiers, and proposed changes before upload. Changing an audience can affect campaigns that already use it. Audience membership and campaign performance are separate results.Enrichment comparisons and ongoing use
A baseline audience uses identifiers already present in the approved source. An enriched audience adds only the identifiers selected for that comparison. Keeping the versions separate helps measure whether enrichment adds matched people under comparable conditions. Recorded Deepline usage covers the operations that ran, including any paid enrichment. The advertising platform’s media spend is separate. Audience preparation does not automatically start a campaign or set its budget. A recurring Play trigger can refresh the reviewed population using the same destination IDs and update policy. The Database can retain source membership and synchronization records between runs. Each replacement must represent the complete population intended for that destination.Related features and guides
- Integrations: account connections and access modes.
- Waterfall enrichment: additional identifiers from a sequence of sources.
- Skills: the specialized ads-audience workflow.
- Build ad audiences: preparation, approval, upload, and status checks.