Results returning
A campaign is judged by the results that come back. Results return to the Outcome they belong to and are used only for that client.
Three ways back
Section titled “Three ways back”| Path | How it works |
|---|---|
| Site tag | The tag on the client’s site records the inquiry when the form system visibly accepts it. See First-party data and the site tag. |
| Results file | The client uploads a file of people who did it, each with the time it happened. Only confident matches count. |
| Signed push | The client’s own system sends results to Moonbrush, signed so the sender can be verified. |
A scheduled file pickup can also be set up on request.
Every result carries its own event time. A result is attributed by when it happened, not by when it arrived.
Nightly matching
Section titled “Nightly matching”Each night, new results are matched to people where possible and recorded on the Outcome, attributed to the campaign that last reached that person within a fixed window set before launch. See How a result is counted.
What comes in from ad platforms
Section titled “What comes in from ad platforms”- Delivery reports. Daily aggregate reports from the ad platform (impressions, clicks, spend), uploaded per day. They are reported next to Moonbrush’s own numbers and never divided into them.
- Impression files. Impression files are designed to join only on the key Moonbrush uploaded, with the platform’s own user ID and IP address discarded and never stored. They are not yet taken in.