From brief to field.Without double buys.
Relay DSA (Data Sampling Automation) takes a sampling request, sets up the survey, checks price and targeting, puts it live and watches every phase until it closes. Each step is logged. When something is unclear, it stops and asks instead of buying twice.
- ✓Request validated · country, tier, currency, LOI09:41
- ✓Survey cloned and ready09:44
- ✓Price from rate card · 200 completes09:45
- →Creating marketplace survey · once09:45
review
Fast or careful.Pick both.
Sampling is a chain of small hand-offs: brief, survey platform, marketplace, price, targeting, mails. Done by hand, every link is a chance to lose an hour, a field or money.
Hand-offs cost hours
Copying a brief field by field into two systems is slow, and nobody wants to do it at 22:00 when a phase needs to resume.
Mistakes cost money
A retried create call or a wrong price bucket buys completes twice. In sampling, a second click is a second invoice.
Silence costs trust
When a step fails overnight, the first person to notice should be you, with the cause and the next step, not the client asking where the data is.
From request to live.Checked at every step.
Every run follows the same durable path. Steps retry on their own, results of anything that costs money are written down at once, and a run that is unsure pauses for a person.
Brief in, validated first
Requests arrive through the API or the console. Country, tier, currency and LOI are checked before anything happens elsewhere.
- API v2 · OpenAPI
- Readable 400s
Survey set up
The survey is cloned in the survey platform and polled until it is actually ready, instead of waiting a fixed time and hoping.
- Polling, not sleeping
- Retries with backoff
Priced by the rules
Price comes from the rate card by country tier and incidence. Targeting is mapped by qualification code and checked before launch.
- Rate cards
- Targeting check
Live once, then watched
The marketplace survey is created exactly once. Phases are monitored; completions and errors go out as short, factual mails.
- Idempotent launch
- Phase monitoring
Checks, with context.Cause first, then the next step.
Automation is only useful if you can see what it decided and why. These are the moments where a manual process usually slips.
| Situation | By hand | With Relay DSA |
|---|---|---|
| The same survey is requested twice | Second purchase is possible | Rejected with 409; the first run stays the only one |
| A create call times out | Retry and hope it did not go through | Run stops and asks for a check before anything is bought again |
| Unknown country, tier or currency | Found after launch | Refused up front with a message a person can read |
| Incidence below the rate card | Price guessed | Fallback bucket applied, logged and flagged in the mail |
| A phase fails overnight | Noticed the next morning | Error mail with the cause and what to do next |
Every step, payload and decision is kept in the run log and the audit trail.
How Relay DSA behaves.Three rules we do not bend.
Traceable
Every step is logged and explainable. We show what happened, not only that something happened.
Careful with money
Better to stop and ask than to buy twice. Uncertainty is shown, not hidden.
Calm
We only report what needs an action. No noise, no exclamation marks, no urgency without a reason.
Built around the peoplewho run fieldwork.
Request and forget, until it matters
Send a request, get the survey IDs back and a mail when a phase completes or needs you.
One console for every run
Runs, manual reviews, history and logs in one place. Production and staging side by side, never mixed up.
A documented API
Sampling API v2 with API keys per company, an OpenAPI document and a targeting builder to try requests.
Know what is running.And why.
Start with the API guide, or sign in to the console if your team already uses Relay DSA.