Translate the tier language into a relationship map
A referral tier generally describes a relationship between a participant and people they refer, or between those referrals and additional participants. Programs can use terms such as direct, sub-affiliate, or second level differently. Do not infer a formula from familiar wording. Start by drawing a simple map: identify your own account, the person or publisher you refer, and any downstream relationship the program says it recognizes. Label every connection according to the program’s definitions, not your own assumptions.
Next, determine what the program means by an eligible referral. Is it a registration, a qualified customer action, an approved account, or another event? The terms may distinguish someone who clicks from someone whose activity qualifies for reporting or commission. Record the exact event and any stated conditions. If the documentation uses a vague label without defining it, ask for clarification in writing before promoting a tier as part of your business case.
- Write down each tier name and its program-defined meaning.
- Draw the referral path from your account to any downstream participant.
- Identify the qualifying event for each relationship and mark undefined terms as unresolved.
Confirm attribution and the boundaries of a tier
A tier model only matters if the program can associate the relevant activity with the correct accounts. Review how the program says it records a direct referral, how a downstream relationship is established, and whether there are conditions that can break or override attribution. Do not assume that attribution for your own referred customer automatically proves attribution for a participant you referred. Those may be separate tracking paths with separate rules.
Ask what happens when a referral already has an account, follows a different link, changes devices, or joins through a route that cannot be attributed. The answer may be in terms, support documentation, or a program representative’s written response. Avoid promising that every downstream action will be credited. Your planning should reflect the documented limits and recognize that reporting may not expose every detail needed to independently verify a tier relationship.
| Term area | Question for the program | Evidence to keep |
|---|---|---|
| Relationship definition | What counts as a direct or downstream referral? | Current written definition |
| Eligibility | Which account or action qualifies? | Eligibility criteria and exclusions |
| Attribution | How is the referral path associated with an account? | Tracking explanation and any limits |
| Commission basis | What event or amount is used in the calculation? | Current calculation language |
| Duration | How long does the relationship or eligibility last? | Time limits, renewal, and change terms |
| Reporting | What tier detail can the participant review? | Report fields and export availability |
Read the calculation and payment conditions carefully
A tier description is incomplete until you understand the calculation behind it. Identify what amount or event the program uses, whether a tier is calculated from a gross or adjusted basis as defined in the terms, and which reversals, refunds, or exclusions may affect the result. Do not translate a percentage, share, or other formula into expected income without knowing its base and qualifying conditions. If there is no precise calculation example in the documentation, request a non-confidential example or a written explanation.
Then trace the result through the program’s ordinary payment process. Check when a reported amount becomes payable, whether approval or a minimum threshold applies, and what records are available to reconcile a statement. These conditions may differ between direct activity and tier activity. Avoid treating a dashboard estimate as a final amount unless the program defines it that way. Keep a copy of the applicable terms and the date you reviewed them, because a later change may alter how you interpret historical results.
Check reports against the structure you were promised
Before relying on tier reporting, determine whether reports distinguish direct activity from activity associated with people you referred. Look for the fields you would need to understand counts, status, qualifying events, reversals, and dates. If the interface provides only a combined total, ask whether more detailed records or exports are available. A summary can be useful for monitoring but may not be enough to explain a discrepancy or validate an operational assumption.
Create a low-risk reporting review once you are approved and have genuine activity to inspect. Compare the program’s stated definitions with the fields it actually displays, and save permitted exports or statements according to your records policy. Do not create fake accounts, self-refer, or generate artificial activity to test the system; that can violate rules and distort reports. If a real referral appears missing, document the relevant date, link or campaign identifier where appropriate, and the support response without sharing personal data unnecessarily.
- Check that report labels match the program’s written tier definitions.
- Find out whether data can be exported and what time period it covers.
- Use legitimate activity only; do not manufacture referrals as a test.
Review restrictions and operational risk before recruiting
Tier structures may introduce rules beyond ordinary traffic permissions. Check whether the program allows you to refer other publishers, whether those publishers must be approved, and whether you can make claims about their potential earnings. Review restrictions on paid recruitment, incentives, brand use, traffic sources, geographic targeting, and related accounts. Do not assume that permission to send visitors also permits recruiting affiliates or describing tier benefits publicly.
Consider the operational work a tier creates. You may need to explain terms accurately, answer questions, keep current links and disclosures, and communicate changes to people you referred. Decide how you will handle program updates and what you will tell participants if attribution, eligibility, or payment conditions change. Do not make your own publisher’s revenue dependent on a downstream forecast that the program does not substantiate. A tier can be an optional feature, but it should not substitute for evaluating the program’s core fit, restrictions, reporting, and payment terms.
- Verify that recruiting and downstream promotion are expressly permitted.
- Avoid earnings promises or claims not supported by current written terms.
- Keep a dated record of terms and changes that affect people you refer.
Common questions
Are referral tiers standardized across affiliate programs?
No. Similar terms can refer to different relationships, qualifying events, calculation bases, or eligibility rules. Use the program’s current written definitions and request clarification where the wording is incomplete.
How can I tell whether a downstream referral was attributed correctly?
Check whether the program reports the relevant relationship and activity separately, then compare that information with the documented rules. If a report lacks enough detail, ask what evidence or export is available. Do not create artificial accounts or activity to test attribution.
Should I include tier income in a business forecast?
Only with appropriate caution and only if the rules and reporting support the assumptions. Treat it as uncertain unless you understand the qualifying events, calculation basis, exclusions, attribution limits, and payment conditions. Do not present projected tier amounts as guaranteed.
What if the program’s tier explanation conflicts with its terms?
Pause promotion of the claim that depends on the conflict. Ask the program for a written clarification, keep the response with the relevant terms, and use the most current authoritative program documentation when deciding what you can state publicly.