Activating the audience

You built the audience — now go use it. Activating exports it in the exact shape your destination expects:

• Social platforms — Meta, Google, LinkedIn, X, Reddit, and more, each in its own custom-audience format, ready to upload.
• DSPs — shaped for direct use in your programmatic buys.
• Outbound — lead lists for email and SMS campaigns.
• Direct mail — names and addresses, ready for the mail house.

Say where it's going:

• /watt:audience export this to Meta
• /watt:audience I need a lead list for an email campaign
• /watt:audience get this ready for my DSP

Watt names the formats available when you ask — the chat is always the current answer.

And that's just Watt's side. You're in Claude, so the export composes with the rest of your tooling: push it into your CRM through an MCP connector, dedupe it against a suppression list you keep, or hand it to anything else your connected tools can do with a file.

Nothing exports unconfirmed

Activation is the one step that pulls real people, so it runs behind an explicit gate. Before anything is pulled, Watt puts the whole deal on screen and waits for your yes:

• The destination you picked.
• The scale — how many people this run pulls, as a real number. There's no size ceiling — an audience exports whole, whatever its reach.
• The identifiers that ride along — emails, phones, names, addresses, mobile IDs — and what the destination's format does to them.
• Who gets dropped — people missing the identifiers your destination matches on can't be uploaded, and that count is named before the run, never discovered after.

No surprise files, no silent shortfalls. "Just do it" without the numbers on screen isn't a confirmation — Watt will put them up and ask once.

The file

Every file matches what its destination actually accepts — for an ad platform, the published spec exactly: the layout, the field order, the identifier handling — because a file that's almost right burns your match rate. It comes back as CSV or JSON, delivered as an MCP resource pointing at a temporarily hosted file (see Data handling) — ask to download it, copy it to your system, or hand it wherever it's going.

• Identifiers are hashed wherever the destination requires it. An ad platform's file holds digests, not raw emails — except the fields it matches in the clear, which differ by platform and are named in the confirmation. A lead list for outbound or direct mail carries contact data in the clear — that's its job.
• Some platforms take more than one file (a separate device-ID list, for example). You get every file the spec calls for, each with its own row count.
• Carry more than identifiers. Ask for columns of defining characteristics — the traits that put each person in the audience — and feed them to content generation or personalize the outbound.
• The counts reconcile. Matched vs. exported vs. dropped, each named — anything you heard before the run is repeated after it.

One more promise: a platform that hasn't shipped gets a straight answer — Watt never improvises a "close enough" file for an unsupported format. Missing yours? Tell the team.