relayDSA Open console
Data Sampling Automation

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.

A.01 · Launch · Production
Test survey A
Running
Step 5 of 12 · 7 open
  • ✓Request validated · country, tier, currency, LOI09:41
  • ✓Survey cloned and ready09:44
  • ✓Price from rate card · 200 completes09:45
  • →Creating marketplace survey · once09:45
3Manual
review
2Running
7Successful
01 · Why

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.

01

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.

02

Mistakes cost money

A retried create call or a wrong price bucket buys completes twice. In sampling, a second click is a second invoice.

03

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.

02 · How it works

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.

01 · Request

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
02 · Clone

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
03 · Price & target

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
04 · Live & watch

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
03 · Checks

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.

SituationBy handWith Relay DSA
The same survey is requested twiceSecond purchase is possibleRejected with 409; the first run stays the only one
A create call times outRetry and hope it did not go throughRun stops and asks for a check before anything is bought again
Unknown country, tier or currencyFound after launchRefused up front with a message a person can read
Incidence below the rate cardPrice guessedFallback bucket applied, logged and flagged in the mail
A phase fails overnightNoticed the next morningError mail with the cause and what to do next

Every step, payload and decision is kept in the run log and the audit trail.

04 · Principles

How Relay DSA behaves.Three rules we do not bend.

01

Traceable

Every step is logged and explainable. We show what happened, not only that something happened.

02

Careful with money

Better to stop and ask than to buy twice. Uncertainty is shown, not hidden.

03

Calm

We only report what needs an action. No noise, no exclamation marks, no urgency without a reason.

05 · Teams

Built around the peoplewho run fieldwork.

Project managers

Request and forget, until it matters

Send a request, get the survey IDs back and a mail when a phase completes or needs you.

Operations

One console for every run

Runs, manual reviews, history and logs in one place. Production and staging side by side, never mixed up.

Open console →

Developers

A documented API

Sampling API v2 with API keys per company, an OpenAPI document and a targeting builder to try requests.

API docs →

Know what is running.And why.

Start with the API guide, or sign in to the console if your team already uses Relay DSA.