Novaxnetwork explains SubID tracking in affiliate marketing as a practical way to see which campaigns, placements, or creatives produced your results. Sub-IDs are additional values passed through supported tracking-link fields. When those values appear in click and conversion reports, you can compare traffic segments instead of treating every visit as part of one undifferentiated campaign.
For example, two placements might send traffic to the same offer. Without separate labels, their combined totals can hide a placement that generates plenty of submissions but few approved leads. Sub-ID tracking gives you the reporting detail needed to investigate that difference.
What is a sub-ID in affiliate marketing?
A sub-ID is a value stored in an additional tracking parameter. Depending on the platform, a field might be named sub1, aff_sub, or something else. Its business meaning comes from the mapping you agree to use.
One field could contain a campaign reference; another could identify a placement or landing-page version. The platform does not necessarily know what creative_07 means. Your naming record supplies that context.
The values can then be used for filtering, grouping, and reconciling supported reports. They provide descriptive information about the referral; they do not independently establish that a conversion qualified for payment.
How is a sub-ID different from a click ID?
A campaign label usually applies to many visits. A click ID references a particular recorded click or click session. If 800 visitors use the same placement, they can share its placement label while having separate click references.
The guide to click IDs in affiliate tracking explains that matching role.
However, some integrations deliberately store an external tracker’s click ID in a sub-parameter. That field is then serving an identification purpose. Check the existing configuration before replacing its value with a campaign name.
TUNE provides a different arrangement: its tracking-link parameter documentation separates non-unique sub-ID labels from dedicated partner click-ID and unique-value fields. Follow the conventions of the system you actually use.
Choose a field mapping before building links
Start with the decisions your reports need to support. For a paid-traffic campaign, a mapping could look like this:
| Available label field | Assigned meaning | Illustrative value |
|---|---|---|
| Campaign field | Campaign reference | camp_104 |
| Placement field | Site, ad group, or approved placement reference | placement_12 |
| Creative field | Ad or creative version | creative_07 |
| Landing-page field | Landing-page version | lp_b |
This is a proposed business mapping, not a universal set of parameter names. Reserve any field already required for click matching or another integration. The number of available fields, permitted values, and reporting options depend on the platform and account configuration.
A short shared record should identify each parameter, its purpose, who supplies it, and whether its value is static or dynamic. That prevents one person using a field for placements while another uses it for creative names.

What does a link with sub-IDs look like?
A TUNE-style example could use these supported parameter names:
https://tracking.example/aff_c?offer_id=123&aff_id=456&aff_sub=camp_104&aff_sub2=placement_12&aff_sub3=creative_07
The example domain and account numbers are illustrative. Obtain the real base link from your platform’s link generator; do not replace its required routing or account parameters with these sample values.
Here, aff_sub carries the campaign label, aff_sub2 the placement, and aff_sub3 the creative. Another platform may accept sub1, sub2, and sub3 instead. Changing the names without checking support can leave the intended reporting fields empty.
Inspect the final destination and recorded click after following the link. A parameter visible in a URL is not sufficient evidence that the intended system captured it.
Should sub-ID values be static or dynamic?
Use a static value when every visit through a particular link should share the same label. For example, a sidebar link on one website could consistently pass sidebar_top.
Use a dynamic value when the sending platform can populate a supported variable for each request, such as an ad or placement reference. The macro syntax belongs to that sending platform; a placeholder copied from another system may remain literal text.
Check an actual permitted test request. If the report contains the placeholder instead of an ad reference, substitution did not work as intended. Do not assume that braces or brackets alone make a value dynamic.
Keep controlled labels consistent. Stable campaign or creative references are easier to reconcile than frequently renamed descriptions. Use a separate lookup sheet for readable names, and preserve the historical meaning of existing labels.

How do sub-IDs reach conversion reports and postbacks?
The tracker must capture the values on the referral record and associate the conversion with that referral. Supported reports can then display the stored labels alongside the attributed event.
Passing the same information to another platform is a separate configuration step. The outgoing notification needs the correct supported macros and receiving parameter names. It also needs to retain any reference required for click matching.
The explanation of S2S postback tracking covers the notification process. A working advertiser-to-network callback does not automatically confirm that every label reaches an affiliate’s separate tracker.
Check each required boundary: incoming link, stored click, attributed conversion, and outgoing notification. Forward only the fields needed by the receiving system.
How can sub-ID reports improve campaign decisions?
Consider two hypothetical placement segments promoting the same offer. Each approved lead earns $5. Assume the records have completed the relevant review period and use matching event definitions.
| Metric | Placement A | Placement B |
|---|---|---|
| Recorded clicks | 1,000 | 1,000 |
| Submitted leads | 60 | 100 |
| Approved leads | 48 | 40 |
| Approved commission | $240 | $200 |
| Traffic cost | $150 | $180 |
| Submission conversion rate | 6% | 10% |
| Lead approval rate | 80% | 40% |
| Approved EPC | $0.24 | $0.20 |
| Commission minus traffic cost | $90 | $20 |
Placement B produces more submissions and a higher submission conversion rate. Placement A produces more approved commission and a larger contribution after traffic cost. The final row excludes other operating costs, so it is not a complete net-profit calculation.
These invented figures illustrate analysis, not Novaxnetwork campaign results or performance benchmarks. The guide to EPC in affiliate marketing explains the earnings-per-click metric used here.
Sub-IDs make this comparison possible, but the labels do not prove what caused the difference. Review traffic mix, creative, landing page, and delivery conditions before treating a placement label as the explanation.

Compare approval status and timing fairly
A recent segment may still have many pending leads, while an older segment has completed review. Comparing their approved earnings immediately can favor the older group simply because its records have had more time to mature.
Use a consistent cohort and date basis. Check the attribution window in affiliate marketing and whether the report groups activity by click date or conversion date.
Review rejection information where available. Lead scrubbing in affiliate marketing concerns the validation process that can affect which submitted leads remain payable. A sub-ID label does not override that process.
Also resist splitting reports into more groups than the data can support. A creative with two clicks and one conversion can show an impressive rate without providing a dependable basis for reallocating a campaign budget.
Are sub-IDs the same as UTM parameters?
They can describe similar campaign details, but they are different fields interpreted by different systems. UTM parameters such as utm_source and utm_campaign support campaign measurement in tools such as Google Analytics.
An affiliate tracker does not necessarily populate its sub-ID columns from those values automatically. Any copying or synchronization must be supported and configured. Likewise, adding a sub-ID does not automatically create the equivalent Analytics dimension.
Use compatible naming across both reporting systems while documenting the actual mapping. Matching labels help reconciliation; they do not eliminate differences in attribution, event definitions, or counting rules.
Keep labels and cost data consistent
A label is useful only while its meaning stays clear. If placement_12 refers to a sidebar this week and an email placement next week, combining those records creates a segment that no longer describes one comparable source.
Assign new labels when the underlying item changes materially, and keep a lookup record for retired values. Avoid building every label from a long list of changing attributes. Separate campaign, placement, and creative fields make it easier to investigate one dimension at a time.
Treat missing labels as an issue to investigate. An empty value could mean an untagged link, a failed macro, or a capture problem. It does not establish that the traffic belongs to a particular channel, and it should not be silently reassigned to your best-performing segment.
Cost matching needs the same care. Suppose a campaign costs $100 and produces ten conversions. If an export repeats the campaign’s $100 total on every conversion row, summing that column produces $1,000. The campaign did not suddenly become ten times more expensive; the cost data was joined at the wrong reporting level.
Before calculating segment contribution, establish whether each cost row represents a click, placement, campaign, or reporting period. Join and aggregate accordingly. If spend is available only at campaign level, do not present a precise creative-level margin without explaining how that cost was allocated.
The same principle applies to clicks. A conversion export with several events attributed to one referral is not necessarily a list of separate clicks. Get your denominator from the appropriate click report rather than counting conversion rows as visits.
Test the mapping before using it at scale
Run a small controlled test with recognizable labels:
- Generate a valid tracking link. Preserve the platform’s required parameters.
- Add supported fields. Keep click-matching references in their intended locations.
- Follow the complete journey. Check whether redirects preserve the expected values.
- Inspect the click record. Confirm that each label appears in the intended column.
- Complete an authorized test event. Verify its attribution and stored labels.
- Check the downstream notification. Confirm the values received by any separate tracker.
- Test a second label set. Make sure the two segments remain distinguishable.
Use appropriate URL encoding and check field-length limits. Keep emails, phone numbers, authentication tokens, and other unnecessary sensitive information out of campaign-label fields.

Frequently asked questions
How many sub-ID fields should I use?
Use the supported fields needed for your reporting decisions. Start with a clear mapping rather than filling every available slot. Check whether any fields are reserved by existing integrations.
Can I change what a field means later?
Yes, but document the change and its effective date. Mixing old placement values with new creative values in the same report column makes historical comparisons harder.
Why is my sub-ID missing from reports?
Check the supported parameter name, actual transmitted value, redirect handling, capture configuration, and report settings. A visible URL value may not have reached the field you expected.
Does adding sub-IDs increase conversions?
Adding labels improves reporting detail when configured correctly. Performance changes come from decisions and campaign changes informed by that data, not from the presence of a label alone.
