UC-07: Campaign Lifecycle and Conversion Tests

Role-gated control-plane steps are intentionally excluded from this public guide; use support escalation when those operations are required. Shared company context: Gharart.com Company Context Need operator help? Escalate through Troubleshooting and Support with request IDs and repro artifacts.

Developer Outcome

Ship campaign lifecycle and conversion tests for Gharart.com with reproducible API steps, operational limits, and clear debugging playbooks.

Prerequisites

• A valid handle and environment access for Gharart.com.
• JWT and/or PAT credentials with required scope for this use case.
• Access to logs, support escalation endpoints, and test workspace.
• For lead-capture funnels, a test email address and a fresh ctx token from a real tracked click.

Gharart Scenario

New buyer funnel A/B test launch.

Persona: Lifecycle marketing manager

Business goal: Ship and validate campaign funnels with deterministic conversion test signals.

Step-by-Step Flow (UI + API)

1. Open the relevant Gharart workflow in the dashboard and confirm actor role access.
2. Execute route calls in sequence for this use case and capture response IDs.
3. Validate expected state in UI and API after each step before moving forward.
4. Record artifacts (request ID, run ID, deployment ID, slug, or token) for support handoff.

Primary API Routes

Limits and Quotas

• Respect per-route throttles and daily write limits before bulk operations.
• Use idempotency-safe retries for write endpoints to avoid duplicate business actions.
• Schedule high-volume workflows outside peak campaign windows where possible.

Where This Breaks

• test-conversion endpoint returns invalid_ctx
• campaign health drops from missing traffic tags
• conversion dedupe confusion from reused idempotency key
• lead capture rejects invalid email or stale ctx payloads

How Gharart Debugs It

1. Run campaign health endpoint before spend ramp
2. Run the PAT/public campaign health route if the workflow is being monitored by automation.
3. For LEAD_CAPTURE funnels, submit one public lead and verify creator review/export routes show the record.
4. Issue controlled test-conversion for each campaign variant
5. Verify campaign detail page is published with FREE_WITH_LOGIN and schema fetch succeeds
6. Verify public conversion payload includes fresh ctx token

Escalation

Use end-user escalation path:

• Submit POST /v2/support/report.
• Include summary, details, and when available handle, sessionId, requestId, reproArtifact.

Audience boundaries:

• POST /v2/operator/escalations is an internal operator workflow and not an end-user escalation action.
• POST /v2/public/content-report is for public abuse moderation reports, not product incident escalation.