Customer Attribution, Channel Pricing, and Distribution Revenue

Whether the white label business can be settled correctly is not about whether the page looks like yours, but whether the first registration entry for new customers, invitation relationships, order channel prices, and final distribution records can correspond.

Complete closed loop from access, registration, purchase, use to attribution and revenue

Completion Effect

A test customer who has never registered before enters from your Studio or API Platform; after registration, they hit the expected invitation relationship. The business completes a small purchase and use when it is clear that costs are allowed, and the order, quota, usage, and distribution records can be cross-verified.

Preparation Before Starting

  • An email or phone number that has never been registered;
  • A formal page domain that has been completed;
  • A default or mandatory inviter has been determined;
  • Channel markup rules have been established;
  • Acknowledgment that real purchases will incur costs;
  • Do not use existing accounts to test first attribution;
  • This document's screenshots are read-only, do not place orders or change invitation relationships.

Step 1: Configure Distribution Relationships

Studio

  1. Click Manage in "My Substation" of the official Studio;
  2. Open Distribution Settings in the substation settings;
  3. Set the default inviter;
  4. Only consider mandatory inviters when the business explicitly requires overriding all other sources;
  5. Save and record the configuration time.

API Platform

  1. Open the Distribution Settings of the Site;
  2. Set the "Default Distribution Relationship";
  3. Use "Mandatory Distribution Relationship" with caution;
  4. Read the explanation on the priority of promotional links and invitation cookies on the page;
  5. After saving, do not display names, emails, or user IDs in public screenshots.

Mandatory relationships will override promotional links, invitation cookies, and default relationships, and must be confirmed with business rules and user notification methods before enabling.

Step 2: Register with a Brand New Customer

  1. Open a new incognito window;
  2. Enter from the official Studio or Platform page domain;
  3. Complete registration;
  4. Record the entry domain, test account, and exact time;
  5. Query the test customer in the authorized distribution/customer backend;
  6. Verify the actual invitation relationship.

Attribution is usually determined at the time of first registration. Existing accounts in the shared system already have relationships and cannot reliably verify the default attribution of the new Site.

Step 3: Verify Channel Pricing

When entering through the normal white label purchase process:

Channel Display Price = Platform Price × (1 + Site or Single Service Markup Ratio)

Service-specific markups take precedence over the default value for the entire site. The display currency is not equal to the order settlement currency, and the final settlement page and order snapshot shall prevail.

Site markup is the pricing rule for the current white label browser channel, not a strong tenant price that cannot be bypassed by accounts across all domains and all purchase entries.

Step 4: Complete a Small Closed Loop After Clear Authorization

  1. Have the test customer purchase the smallest available package;
  2. Record the actual payment amount and order number;
  3. Execute a low-cost Studio or API request once;
  4. Verify the quota and usage records;
  5. Cross-check the transaction amount on the webmaster side with the distribution records;
  6. If a refund occurs, verify whether the revenue is adjusted according to the rules.

This document update does not execute these paid operations; they should be accepted separately after the business explicitly authorizes the costs.

Step 5: Understand Revenue Metrics

Webmaster Revenue = Valid Order Amount that Meets the Rules × Current Distribution Ratio

Actual settlement is also affected by the following factors:

  • Current distribution level;
  • Default, mandatory, promotional links, or historical invitation relationships;
  • Whether the order is completed;
  • Refunds and risk control;
  • Settlement rules and timing.

Therefore, do not directly calculate revenue using the "difference between platform price and channel price," and do not promise fixed commissions, payment speeds, or income figures.

Step 6: Check Ongoing Relationships

  1. Log out of the test customer;
  2. Log in again from the white label domain after some time;
  3. Complete a second low-cost use;
  4. Confirm that existing invitation relationships have not been accidentally overridden by ordinary entry;
  5. Verify subsequent orders and usage records that meet the rules.

Current Boundaries

  • The Site does not own an independent user database, balance, or package;
  • The first registration entry affects the invitation relationship, but the account still belongs to a shared identity system;
  • Channel markup is not a mandatory tenant price across all entries;
  • Distribution relationships and revenue are not isolated or controlled by Site data;
  • Hiding recharge, services, and documents will not change existing accounts or historical invitation relationships.

Success Indicators

  • A brand new test customer hits the expected invitation relationship;
  • Registration entry, account, time, and relationship records can correspond;
  • Channel settlement price complies with the rules for the entire site/single service;
  • Orders, quotas, usage, and distribution records can be cross-verified;
  • The team will not claim the markup difference as total revenue;
  • Customer materials do not contain internal user IDs, complete keys, or sensitive payment information.

Frequently Asked Questions

New customer not attributed to the expected inviter

First, confirm whether the account has truly never registered, then verify the default/mandatory relationships, promotional links, invitation cookies, entry domain, and exact time.

Price is correct, but revenue is not the markup difference

This is a normal mechanism. Revenue is calculated based on valid order amounts, current distribution ratios, and order status, not a full refund of the markup difference.

Order completed but revenue has not yet appeared

Check the order status, refunds/risk control, and settlement timing. Use the final valid distribution record as the standard, and do not calculate based on frontend prices.

Next Article

Finally, read White Label Boundaries, Troubleshooting, and Daily Operations to turn a one-time acceptance into a long-term process.