atlas overview
atlas is for enterprise marketing, data and CRM teams that already hold first-party data. It resolves that data to people and households, scores it with the Gravity catalog, and returns scores and audiences as downloadable packages and files.
The workflow
Section titled “The workflow”- Match. Upload a file of people. Each row is matched deterministically, and the match rate is shown in the preview before any paid build runs. See Matching.
- Enrich and score. Matched records receive catalog scores and picks. Export columns are limited to fields cleared for clients, and anything refused is named. See Scores and columns.
- Deliver. Audiences, seed lists and suppression lists leave as packages of SHA-256 hashed identifiers for upload to media platforms. See Delivery.
- Bring results back. Results return by the site tag, an uploaded results file or a signed push. They are matched nightly and used only for that client. See Results returning.
What goes in, what comes out
Section titled “What goes in, what comes out”| In | Out |
|---|---|
| A file of people: email, phone, postal address with a name, or a Moonbrush ID | Per-record scores from 0 to 1, each with model version and date |
| Optional dated results for an Outcome | Picks, audience group labels and group descriptions |
| Optional suppression and do-not-contact lists | Packages of hashed identifiers, laid out for each destination |
What a client configures
Section titled “What a client configures”- The Outcome. The action that counts, where it happens, and its target. See Outcomes and reports.
- The universe. The population audiences are drawn from.
- Suppression lists. Applied when an audience is built and kept out of every later list.
- Destination and columns. Where the package goes and which cleared columns it carries.
- The collection profile. What the site tag stores. See First-party data and the site tag.
- The held-back switch. Whether a share of each list is set aside for comparison. Off unless switched on. See Held-back groups.