Start with property-level eligibility

When a publisher operates several websites, an account-level approval does not necessarily answer whether every property is approved. Read the program's current application and operating terms for rules about adding domains, subdomains, applications or other publishing properties. If the language is unclear, request written clarification before placing links on a new property.

Keep a property register that records the domain, audience, content type, owner, approval status and the date the program confirmed its status. This helps prevent a common operational error: treating a program relationship as blanket permission for every site the business owns. It also gives the team a clear source of truth when a domain is redesigned, sold or repurposed.

  • List every property that may send referrals, including any separate apps or subdomains.
  • Record approval evidence and the contact or policy source that confirmed it.
  • Add a review step before launching a new domain or materially changing a site's purpose.

Separate tracking without creating a naming mess

A multi-site account needs enough tracking structure to distinguish properties, campaigns and placements. Determine which identifiers the program supports and what each one records. Then define a naming convention before building links. For example, a convention might include a short site code, placement type and campaign name, while avoiding personal information or sensitive audience labels.

Do not assume that a tracking tag creates a separate account, changes program eligibility or guarantees a particular attribution outcome. It is a reporting aid only if the program documents and supports it. Test a small number of links and confirm that the resulting report fields preserve the distinctions your team needs. Keep an internal mapping between short codes and full property names.

  • Use stable, human-readable codes for each approved property.
  • Document how campaign tags are created and who may change them.
  • Test that reporting retains the property and placement labels after a referral is recorded.

Check whether staff access can follow property boundaries

A business may have writers, analysts or contractors who should work on one site but not see every program property or account setting. Review available user roles and permissions before inviting collaborators. Find out whether access can be limited to reporting, link creation, finance or account administration, and whether one person's changes affect every property.

If the dashboard only provides broad access, establish compensating controls outside the program. Assign a responsible account owner, limit credential sharing, keep a change log and use a process for reviewing new links. Never assume a dashboard's role labels mean the same thing across programs; confirm the actual actions each role can perform.

  • Map team duties to the minimum access each person needs.
  • Identify who can change payment, tracking and property settings.
  • Keep a record of access grants, changes and removals.

Design reports that answer site-level questions

A consolidated account view may make totals easy to see but can conceal differences between properties. Before relying on the dashboard, verify whether reports can be filtered by property, campaign and date range, and whether those dimensions can be exported. Check whether the same conversion or adjustment can be assigned consistently to the site that introduced the visitor.

Create an internal monthly review that compares program records with your own link inventory and publishing log. Investigate unexpected blanks, renamed codes or activity assigned to an unknown property. Keep an untouched copy of source reports alongside any cleaned or combined spreadsheet, so later reviewers can understand where a number came from.

Multi-property affiliate account fit checklist
AreaQuestion to answerEvidence to retain
ApprovalIs each site explicitly permitted?Written confirmation or dated approval record.
TrackingCan activity be distinguished by property?Test link, code map and resulting report.
AccessCan staff permissions match responsibilities?Role list and access-change log.
ReportingCan site-level data be reviewed and exported?Sample report and reconciliation notes.
Ownership changeWhat happens if one property is sold or retired?Policy reference and transition contact.

Plan for property changes and exits

A website may be sold, moved to a new domain, merged, paused or rebuilt. Each change can affect approval status, links, account access and the accuracy of historical reporting. Before making a change, review the program's notice requirements and ask whether the property must be reapproved. Preserve a record of the old and new domains, relevant dates and the pages or campaigns affected.

If a property leaves the business, remove or replace its links according to the program's rules and your agreements with the buyer. Also consider whether staff access, saved reports and tracking codes need to be transferred or closed. Keep program records separate from the site's content and analytics records so a business transition does not erase the ability to explain earlier activity.

  • Set a review trigger for sales, migrations, redesigns and changes of ownership.
  • Keep a link inventory that can be searched by property and campaign.
  • Document how account access and historical records will be handled when a site exits.
FAQ

Common questions

Does one affiliate account automatically approve all websites owned by the same publisher?

Do not assume so. Check the program's terms and approval records for each property. If the rules do not clearly explain how additional sites are handled, ask the program for written clarification before placing links.

Are tracking tags the same as separate property accounts?

No. A tag can help organize reporting when supported, but it does not necessarily create a separate account, change eligibility or guarantee attribution. Confirm what the program records and test the reporting before relying on it.

What should I do before selling one of my websites?

Review the program's rules for domain ownership and link use, document the transition date, remove or transfer links as permitted, update access and preserve relevant reports. Confirm any required notice or reapproval directly with the program.