Delivery
Audiences leave Moonbrush as a package: a ZIP file built on Moonbrush servers. Raw emails and phone numbers are never written into a package.
What a package holds
Section titled “What a package holds”Directorycampaign-package.zip
- manifest.json audiences, groups, notes, overlap policy, score versions
- README.md
Directoryaudiences/
- lapsed-members.csv one file per audience
Directorygroups/
Directoryg1-researchers/
- members.csv one file per audience group
- README.md segment name, landing-link suffix, impression pixel where supported
Directorycreative/
- …
Directoryg2-deal-seekers/
- …
- manifest.json lists the audiences and groups, notes, the overlap policy, and the score version each person was sent under. People withheld for any reason appear only as counts.
- Member files carry hashed identifiers and an export-scoped row key. They never carry Moonbrush’s internal person ID.
- Group READMEs give the segment name to use in the media platform, the landing-link suffix to append, and an impression pixel where the destination supports one.
See Package and file formats for column-level detail.
File layouts
Section titled “File layouts”Five layouts exist. Each is shaped to what its destination’s upload accepts.
| Layout | Use for |
|---|---|
| Generic | Any DSP or platform that accepts hashed customer lists |
| Meta | Meta custom audiences |
| Google Customer Match | |
| TikTok | TikTok custom audiences |
| LiveRamp | Onboarding through LiveRamp |
All layouts carry SHA-256 hashed email and phone. Most also carry hashed first and last names, with ZIP and country as plain values, as the destinations require.
Hashing
Section titled “Hashing”SHA-256, lowercase hexadecimal, unsalted, which is the form ad platforms require for matching.
| Field | Before hashing |
|---|---|
| Trim spaces, lowercase | |
| Phone | Normalize to E.164, with or without the plus sign as the destination requires |
| First and last name | Trim spaces, lowercase |
| ZIP | Never hashed |
| Empty value | Never hashed |
A person with several emails gets one row per hash.
Overlap
Section titled “Overlap”When a person belongs to more than one audience in a campaign, the manifest’s overlap policy decides what happens. By default they ship once, in their highest-priority audience. Nothing is deduplicated outside that policy.
Readiness and records
Section titled “Readiness and records”- Readiness check. Before download, each audience is checked against each destination’s minimum list size.
- Send record. Every export writes a send record before the file is returned, and counts against the organization’s processing cap.
- Ad links. Each group’s links carry an audience-group code and an optional creative reference, written by the export and never by hand. Links never carry a per-person identifier.
Destinations available today
Section titled “Destinations available today”| Path | Status |
|---|---|
| Packages uploaded by the client or agency to ad platforms and DSPs | Available |
| Direct push to Meta and Google | Coming soon |
| Delivery into a client’s data warehouse or a clean room | Not offered today |