Ops Lab Playbook: Traffic Conflict Ops
Last updated: 2026-03-08
1. Purpose and when to use this
Use this module to investigate routing conflicts, evaluate destination-domain decisions, and run link health checks before traffic-impacting changes.
2. User roles and auth modes
JWT operator: route preview, destination decision checks, health diagnostics.
3. Prerequisites checklist
- Primer completed: Onboarding and API Primer
- Existing link slug and destination domain.
JWT_TOKENwith operator access.
4. UI onboarding flow
- Open
https://app.10x.in/creator/traffic-conflicts. - Run route preview with market/device context.
- Evaluate destination-domain decision for target domain.
- Execute link health check and inspect issues.
5. API workflow map
TC-01:POST /v2/handles/{handle}/links/{slug}/route-previewTC-02:POST /v2/handles/{handle}/destination-domains/{domain}/decisionTC-03:GET /v2/handles/{handle}/links/health-check
6. cURL examples
Set module variables:
export SLUG="launch"
export DOMAIN_NAME="destination.example"
TC-01 Route preview
curl -sS -X POST "${API_BASE}/v2/handles/${HANDLE}/links/${SLUG}/route-preview" \
-H "authorization: Bearer ${JWT_TOKEN}" \
-H 'content-type: application/json' \
-d '{"country":"US","source":"email","device":"mobile"}'
TC-02 Destination decision
curl -sS -X POST "${API_BASE}/v2/handles/${HANDLE}/destination-domains/${DOMAIN_NAME}/decision" \
-H "authorization: Bearer ${JWT_TOKEN}" \
-H 'content-type: application/json' \
-d '{"source":"creator-suite"}'
TC-03 Health check
curl -sS "${API_BASE}/v2/handles/${HANDLE}/links/health-check" \
-H "authorization: Bearer ${JWT_TOKEN}"
7. Expected success outputs and verification checks
- Route preview returns deterministic decision payload.
- Domain decision call returns trust/risk posture envelope.
- Health endpoint returns actionable diagnostics and failing counts if present.
8. Failure modes and remediation
403on destination decision route:- Remediation: verify role and whether platform-admin decision route is required in your org policy.
- Route preview mismatch with expectations:
- Remediation: re-check active personalization/campaign rules and request context fields.
- Health endpoint returns repeated failures:
- Remediation: update broken destinations and rerun checks.
9. Async behavior notes
Traffic conflict module endpoints are synchronous in registry scenarios (SYNC).