Traffic Flow

Who this is for: Supply integrators routing respondents. When to use it: when wiring up how respondents enter a survey and return. What happens next: you'll have an end-to-end path with a tracked participant identifier.

A respondent's journey through a survey, end to end:

 Provider              Zamplia                 Survey / Client
    │                     │                          │
    │  GenerateLink ──────▶                          │
    │  ◀──── entry link    │                          │
    │                     │                          │
    │  send respondent ───┼──────────────────────────▶  respondent takes survey
    │                     │                          │
    │  ◀───────── redirect back with status ─────────┤
    │                     │                          │
    │  GetReconciliation ─▶  confirm outcome          │

Steps

1. Generate an entry link with GenerateLink / EntryLink. The link carries the participant identifier used to track this session end to end.
2. Send the respondent to that link. They pass through Zamplia into the buyer's survey.
3. Receive the redirect back with the session outcome — see Redirect Handling.
4. Reconcile with GetReconciliation to confirm the final status.

Quality & integrity

• Honor IP/geo and security checks (e.g. GetBlockIp) before sending traffic.
• Validate session integrity with HMAC where applicable — see the HMAC Validation guide in the sidebar.
• Don't reuse entry links across respondents; generate one per session.

tip

Send respondents only when a matching quota cell is open to minimize wasted starts.