← All projects

AI PROJECT · NEXT UP

LoudCrowd Connector v5 — Commission & Attribution

Upgrade the read-only connector with LoudCrowd's brand-new Orders API: real commission dollars, attribution methods, refund-adjusted revenue.

⏱ Est. 2 hours (David's estimate) Creator MarketingPriority: HIGHUpdated July 28, 2026

What & why

LoudCrowd's Orders API (launched July 28, 2026) finally exposes the two things our connector could never see: commission per order and how each sale was attributed (tracked visit, affiliate code, link discount, external, manual). v5 layers this official data onto our existing 10,141-order mirror — keeping the SKUs and creator names the new API doesn't provide. The whole team keeps read-only access via Google sign-in; nothing gains write ability.

Architecture — how it fits together

HUMAN LANE — all MM staff, read-only MACHINE LANE — no humans · contingent MM team — all ~40 members sign in: MM Google work account loudcrowd-mcp · v5 commission · attribution · refunds · creators READ-ONLY · zero write code Order mirror (D1) SKUs · creator names 10,141 orders kept Shopify API nightly sync LoudCrowd Brand API (read) commission · attribution · refunds Token A — read scopes only Read Programs + Read Orders joined per order ID · recent orders fetched live Loop Returns (read) refunds & exchanges we already track returns-feed pipeline (cron Worker) BUILT ONLY IF the refund audit finds gaps no chat interface · no human hands · audit log scheduled + idempotent + logged LoudCrowd Events API (write) ORDER_CREATE / UPDATE / CANCEL + returns write token used only as HMAC signing key 🅿 Human admin connector — PARKED LoudCrowd has no admin endpoints yet; dual-connector design ready the day they ship one read path — humans write path — machines only, contingent parked until LoudCrowd ships admin endpoints

The plan — step by step

  1. David creates the read-scoped API token in LoudCrowd → Settings → API Keys (Read Programs + Read Orders only) and stores it with wrangler secret put
  2. One test call verifies field shapes and history depth vs the mirror
  3. Refund audit: confirm Loop refunds already appear in the API's refundAmount (decides whether the returns-feed project is ever needed)
  4. Build: Brand API client, commission/refund/attribution columns, backfill merged by order ID, live+mirror hybrid, new tools loudcrowd_commissions + loudcrowd_attribution_breakdown
  5. npm test → npx wrangler deploy → reconnect connector in Claude
  6. Cross-check commission totals vs the LoudCrowd dashboard; then update the hub guide + regenerate the master downloadables

Reasoning & trade-offs

The new API lacks SKUs and creator names, so it merges with — not replaces — the Shopify-fed mirror
commissionAmount is null only while commission is uncalculated; the connector reports that honestly as pending
A human write lane was investigated and parked: LoudCrowd's write scope is a data-ingestion feed, not an admin tool (verified in their API reference)

Related material

Hub guide — LoudCrowd connector  ·  LoudCrowd Brand API docs

← Back to all projects
AI Projects v1.23  ·  MELINDA MARIA × CLAUDE  ·  updated July 28, 2026
Work in progress — suggestions to ✉️ David or 💬 #mm-claude  ·  Onboarding Hub  ·  © Melinda Maria 2026, All Rights Reserved