> Pushing an audience to a destination

TL;DR: Open the audience → Destinations section → pick the tool → pick the target. Once live, new members push to the destination automatically.

Connecting a destination (first-time setup)

The first time you push to a destination, you need to authenticate the integration. Destinations are configured on the audience — there is no Destinations page and no Destinations entry in Settings. From the audience:

1. Scroll to the Destinations section — a grid of destination tiles, grouped by category. CRM tiles (HubSpot, Salesforce, Attio, Pipedrive, Close, Breakcold) open the plans page, where you upgrade to the Post-PMF plan or request a trial of it; Outreach and Salesloft carry Request trial
2. Click the tool's tile — for example the signed webhook. A side sheet opens
3. Enter the connection details, then Connect
4. Pick the target inside the destination under Routing
5. Save draft while you're still setting it up; Set live when it should start pushing

The connection is workspace-level, so subsequent audiences using the same tool skip the authentication step — their tile is already connected, and all they need is their own routing and rules.

Overwrite policy

When an audience member already exists in the destination (matched by email or external ID), three options:

• Overwrite — update the pushed fields, even if the destination has a different value
• Append — push new values but don't touch fields the destination already has
• Skip-if-exists — only push net-new records; existing ones stay untouched

Append is the safest default when your team also edits those records in the destination. Overwrite is right for a sequencer (the audience IS the source of truth for sequencing).

Multiple destinations

One audience can push to multiple destinations — for example, a signed webhook for each custom internal tool it feeds.

Each destination has its own routing and overwrite policy.

Pausing a destination

Pause connection — the pause icon in the destination sheet's header — preserves the configuration but stops syncing. Useful when you're triaging a destination issue without touching the audience itself. The same button resumes it.

Removing a destination

Remove, in the destination sheet's footer, detaches the destination from this audience and leaves the workspace connection intact — other audiences keep pushing. Disconnect, the trash icon in the sheet header, drops the workspace connection itself and stops every audience.

Members already pushed remain in the destination either way (Unstuck doesn't clean up downstream). Use Remove when this one audience is done with the tool; Disconnect when you're switching tools or sunsetting the integration.

Related

• What audiences are
• Building an audience — Copilot first, then manual
• Audience composition and Reachable %
• Connecting a destination
• Field mapping