Ops Lab Playbook: Creator Commerce + Attribution

Last updated: 2026-03-29

1. Purpose and when to use this

Use this playbook when the job is bigger than checkout alone. It packages the current 10x creator stack as one creator-led commerce workflow: payout onboarding, monetized pages, visitor auth, collaborator campaigns, attribution exports, webhook handoffs, and earnings visibility.

This is the right playbook when you need to answer:

• how do we launch a monetized creator offer?
• how do we run one campaign per creator, collaborator, or partner?
• how do we export evidence for settlement and ops review?
• what can 10x prove directly, and what still stays manual?

2. What this combines

Monetization core

• Stripe Connect onboarding
• paid pages and visitor checkout
• visitor magic-link auth and entitlement settlement
• earnings visibility
• optional group-buy style launches

Collaboration and attribution layer

• one campaign per creator, collaborator, or partner
• tracked links with ctx tokens
• idempotent conversion submission
• analytics and exports by campaign, segment, referrer, and revenue

Partner and affiliate extension

• AFFILIATE_CLICKOUT goal type
• webhook-based commission handoffs
• real-time funnel metrics for collaborator campaigns

Operational trust layer

• campaign health
• test conversion
• analytics export
• webhook delivery and retry visibility

3. User roles and auth modes

• JWT owner: connect onboarding, paid page control, earnings, campaign creation, webhook management, exports.
• JWT creator/operator: collaborator campaign management, health checks, test conversions, group-buy publish.
• VISITOR_COOKIE/public: checkout, access checks, and conversion capture.
• NONE: public conversion submit with valid ctx.

4. UI workflow

1. Open https://app.10x.in/apps/creator-revenue.
2. Start Connect onboarding and verify payout readiness.
3. Create and publish the paid page or offer page.
4. Create one campaign per creator, collaborator, or partner.
5. Run health checks and a test conversion before launch.
6. Publish tracked links to each collaborator.
7. Verify earnings, analytics export, and webhook delivery after launch.

5. Public API workflow map

1. CCA-01: POST /v2/handles/{handle}/connect/onboarding
2. CCA-02: GET /v2/handles/{handle}/connect/status
3. CCA-03: POST /v2/handles/{handle}/pages + publish
4. CCA-04: POST /v2/public/pages/{handle}/{pageSlug}/checkout
5. CCA-05: GET /v2/handles/{handle}/earnings
6. CCA-06: POST /v2/handles/{handle}/campaigns
7. CCA-07: GET /v2/handles/{handle}/campaigns/{campaignId}/health
8. CCA-08: POST /v2/handles/{handle}/campaigns/{campaignId}/test-conversion
9. CCA-09: POST /v2/public/conversions
10. CCA-10: GET /v2/handles/{handle}/analytics
11. CCA-11: GET /v2/handles/{handle}/analytics/export
12. CCA-12: POST /v2/handles/{handle}/webhooks

6. Recommended execution order

Step 1. Make payouts real before you sell

Run onboarding and confirm the creator can actually receive funds:

curl -sS -X POST "${API_BASE}/v2/handles/${HANDLE}/connect/onboarding" \
  -H "authorization: Bearer ${JWT_TOKEN}" \
  -H 'content-type: application/json' \
  -d '{}'

curl -sS "${API_BASE}/v2/handles/${HANDLE}/connect/status" \
  -H "authorization: Bearer ${JWT_TOKEN}"

Step 2. Publish the monetized surface

curl -sS -X POST "${API_BASE}/v2/handles/${HANDLE}/pages" \
  -H "authorization: Bearer ${JWT_TOKEN}" \
  -H 'content-type: application/json' \
  -d '{"slug":"creator-club","title":"Creator Club","mode":"PAID","priceCents":2900}'

curl -sS -X POST "${API_BASE}/v2/handles/${HANDLE}/pages/creator-club/publish" \
  -H "authorization: Bearer ${JWT_TOKEN}" \
  -H 'content-type: application/json' \
  -d '{}'

Step 3. Create one campaign per collaborator

Use a separate campaign for each creator or partner sharing the offer:

curl -sS -X POST "${API_BASE}/v2/handles/${HANDLE}/campaigns" \
  -H "authorization: Bearer ${JWT_TOKEN}" \
  -H 'content-type: application/json' \
  -d '{
    "campaignId":"creator-a-launch",
    "goalType":"PRODUCT_SALE",
    "status":"ACTIVE",
    "primarySlug":"creator-club"
  }'

Repeat with a unique campaignId for every collaborator. This is the core pattern that keeps attribution legible.

Step 4. QA before spend or traffic ramps

curl -sS "${API_BASE}/v2/handles/${HANDLE}/campaigns/creator-a-launch/health" \
  -H "authorization: Bearer ${JWT_TOKEN}"

curl -sS -X POST "${API_BASE}/v2/handles/${HANDLE}/campaigns/creator-a-launch/test-conversion" \
  -H "authorization: Bearer ${JWT_TOKEN}" \
  -H 'content-type: application/json' \
  -d '{"conversionEventType":"purchase"}'

Step 5. Capture and export proof

Read live analytics:

curl -sS "${API_BASE}/v2/handles/${HANDLE}/analytics?funnel=true&campaignId=creator-a-launch" \
  -H "authorization: Bearer ${JWT_TOKEN}"

Export settlement evidence:

curl -sS "${API_BASE}/v2/handles/${HANDLE}/analytics/export?format=csv&campaignId=creator-a-launch" \
  -H "authorization: Bearer ${JWT_TOKEN}"

Read the creator earnings rollup:

curl -sS "${API_BASE}/v2/handles/${HANDLE}/earnings" \
  -H "authorization: Bearer ${JWT_TOKEN}"

Step 6. Hand commission or settlement events downstream

curl -sS -X POST "${API_BASE}/v2/handles/${HANDLE}/webhooks" \
  -H "authorization: Bearer ${JWT_TOKEN}" \
  -H 'content-type: application/json' \
  -d '{
    "endpointUrl":"https://commissions.example.com/ingest",
    "eventTypes":["link.clicked","conversion.tested"]
  }'

7. Proof scenarios to run

• creator onboarding: start Connect, verify status, publish a paid page, run checkout, verify earnings readback
• collaborator attribution: launch separate campaigns for creator A and creator B, then compare exports
• affiliate extension: create an AFFILIATE_CLICKOUT campaign, submit conversion with ctx, confirm webhook delivery to the commission sink
• creator launch QA: run campaign health, test conversion, public checkout path, and analytics export before launch-day traffic
• failure drills: replay duplicate conversions, test invalid or missing ctx, force a failing webhook endpoint, and verify stale-health or low-confidence visibility

8. What is not possible on current infra

• no cross-platform creator attribution for conversions that never pass through 10x-managed campaign or link flows
• no view-through, assist, or long-tail attribution model for “saw creator, converted later elsewhere”
• no automated creator marketplace, discovery, outreach, contracting, or UGC ops workflow
• no native commission ledger that fully automates partner settlement for external storefront sales
• no automatic revenue-split engine across multiple creators on one external transaction
• no full physical-commerce back office for shipment allocation, landed-cost control, or final invoice settlement
• no native Shopify, Meta, or GA4 connector fabric that makes 10x the owner of those systems
• no multi-touch identity stitching across ad platforms, storefront sessions, and creator content reuse

These limits matter. Use this playbook when you want the parts 10x can prove directly, and keep the rest operationally explicit instead of pretending it is already solved.

9. Expected success outputs

• Connect status shows a ready or clearly actionable onboarding state.
• Paid pages publish successfully and can be checked out with visitor auth.
• Each collaborator has a distinct campaignId.
• Analytics and exports isolate clicks, conversions, and revenue per creator or partner.
• Earnings reads return gross/net/platform-fee aggregates.
• Webhook deliveries produce verifiable downstream evidence.

10. Related links

• Creator Revenue
• Creator Economy
• Affiliate and Partnerships
• Campaign Funnel Workflow
• Analytics Exports and Reconciliation
• Webhook Delivery and Failure Handling