Affiliate SubID Naming Conventions: Keep Placement Reports Understandable

Begin with reporting questions

Decide which questions you need the field to answer. A small publisher might distinguish article, placement, and campaign version. An example internal code is “deskguide_table_v1,” meaning a specific guide, its comparison-table placement, and the first link configuration. The example is a naming concept, not a universal parameter syntax. Programs differ in accepted fields, character restrictions, and reporting support. Check your platform’s documentation and link generator before appending any value to a working tracking link.

Separate stable identity from changing labels

Give each piece of content a stable short identifier and keep the human-readable title in a lookup sheet. A title can change for editorial reasons; the identifier should remain interpretable. Use a new version only when it represents a meaningful reporting distinction. If the same link appears in a table and an end-of-article recommendation, assign placement values that reflect that difference when the program permits it. Avoid using a new random ID for every minor wording edit, which can fragment reports beyond useful interpretation.

Build a controlled vocabulary

Define allowed placement terms, such as “intro,” “table,” and “summary,” and document them. Choose consistent casing and separators compatible with the system. Reserve a value for genuinely unknown or unmapped placements rather than silently guessing. A small team benefits from a single register with content ID, placement ID, offer, creation date, destination, and owner. Add examples of valid codes. If someone cannot decode a value using that register, the naming convention is not yet doing its job.

Avoid personal and sensitive values

Use content and campaign descriptors instead of names, email addresses, account details, or other personal information. The purpose is placement reporting, not identifying individual readers. A useful code such as “backupguide_summary_v2” answers an editorial question without exposing a person. Consider what will appear in reports, URLs, logs, and screenshots before approving a taxonomy. Follow the program’s rules and your organization’s data-handling requirements. If a field’s purpose is unclear, ask the platform rather than filling it with whatever your analytics system happens to collect.

Validate and preserve the map

Generate a sample link through the approved workflow and confirm that the intended value appears in the reporting location you will use. Check how unsupported characters, length limits, and exports are handled. Preserve the lookup sheet when articles are archived or renamed so historical results remain intelligible. Review unmapped values regularly and correct the source of inconsistency. A clean taxonomy should make it possible to answer a focused question, such as whether the table placement attracts suitable referrals, without rebuilding the campaign from memory.

Frequently asked questions