Affiliate data

Six Affiliate sources cover outreach and sales, sample conversion, review, fulfillment, and linked orders. They are overlapping perspectives, not six independent performance totals. See Affiliate operations for permissions and workflows.

Every table contains fictional sample data, not a live report or a new interface. Currencies appear in headers. Each section illustrates its own source slice, not one complete ledger. A reviewer is not necessarily the owning BD; ownership analysis also requires authorized relationship records.

#Attributed order detail

Find which Creator and content contributed to an order and whether commission has settled. A row is an Affiliate order-SKU/content attribution record. Fields include Creator, content type and ID, product, payment, estimated/actual commission, and payment or commission timestamps.

Export 30-day Affiliate order detail. Separate estimated and actual commission, retain content and order IDs, and keep currencies separate.

#Sample raw detail

Do not replace unavailable actual commission with zero. Commission settlement differs from Shop fulfillment state. History can change with commission, refunds, and fulfillment. Buyer payment is not seller payout.

#Platform outreach and sales performance

Track invitations, responses, and sales using supported Shop, Campaign, Target Collaboration, Creator, or product combinations. Daily, weekly, and monthly views expose outreach stages, replies, orders, GMV, commission, and attribution coverage.

Compare this week's sent invitations, replies, and net GMV by Campaign. Show Campaign mapping coverage rather than treating unmatched data as zero sales.

#Sample summary data

These stages are not automatically the same Creators entering on that day. Do not interpret one daily row as a strict same-cohort funnel. Invitations do not establish BD ownership; see Team & Channels.

#Sample application and conversion summary

Assess application, approval, shipment, and fulfillment outcomes. Available measures include created applications, current decisions, observed shipments, completion, content, orders, and sales across supported daily, weekly, monthly, and business scopes.

Compare sample approval, observed shipment, and completion by product. State rate denominators and keep sample conversion separate from platform-wide sales.

#Sample summary data

These are current outcomes for applications, not approval actions performed that day. Row one's approval rate is 6 ÷ 10; its observed fulfillment rate uses approved applications, 4 ÷ 6. Sample and platform performance can include the same sales; do not add their GMV.

#Sample review detail

Trace decisions to applications and information available at application time. A row represents one Shop Sample Application. Fields include application date, Creator, product, current decision, decision origin, reviewer, and available application-time Creator performance.

List this month's applications by reviewer and current decision, preserving application-time followers and post rate. Do not fill a missing historical snapshot with today's profile.

#Sample raw detail

Application-time performance requires a nearby acquisition record; otherwise leave it unavailable. Some provider metrics, including GMV, do not specify their reporting period and must not be relabeled “last 30 days.” Human approval requirements remain governed by safety policies.

#Sample fulfillment detail

Check shipment, content, and subsequent orders after approval. Each row remains one Sample Application. Available context includes sample order, tracking, first observed shipment, content and post-application-order indicators, and to-date attributed content, orders, and units.

List applications created this month with observed shipment but no content. Include tracking and the post-application-order indicator. Prepare a follow-up list only; do not send messages.

#Sample raw detail

Row two is possible: to-date attributed orders can precede the application, while the post-application indicator concerns later outcomes. Shipment observations are evidence acquired by the system; a missing observation is not proof that no shipment occurred.

#Sample-linked order detail

Identify sales linked after a particular application. Each row is an application-to-attributed-order-line contribution, with application/order dates, Creator, product, content, units, and post-application net GMV.

Expand these applications' subsequent orders. Preserve application, order, and content relationships; separately calculate unduplicated sales and explain the deduplication basis.

#Sample raw detail

The same order contribution is linked to two applications here; it is not 160 USD of independent sales. Use order or platform performance for overall totals. Preserve many-to-many relationships when explaining application-level attribution.

Return to Business data. For AI review and escalation, see Agent Workbench; for direct staff operations, see Manual Workbench.