This guide treats SubID taxonomy as a controlled workflow: define the boundary, execute a small test, reconcile the result and only then expand. How to design SubID fields for source, campaign, placement, creative and landing page without breaking reporting.
Architecture of SubID taxonomy
Create a stable naming system for source, campaign, placement, creative and landing attribution.
Source boundary
The exact number and names of supported SubID parameters must be checked in the link builder. The taxonomy should remain useful even if tracker or offer changes.
Create a stable identifier scheme: Sneket Partners SubID and ClickID
- Define fields
- Choose controlled values
- Document character limits
- Test encoding through redirects
- Preserve a lookup table
Validate transport and event meaning: Sneket Partners SubID and ClickID
The “Validate transport and event meaning” stage gives SubID taxonomy a defined account, segment, time window and measurable completion condition.
01
filled-field rate.
02
unknown values.
03
truncated values.
04
click-to-event match.
| Control point | Action for SubID taxonomy | Acceptance evidence |
|---|---|---|
| 1 | Define fields. | filled-field rate |
| 2 | choose controlled values. | unknown values |
| 3 | document character limits. | truncated values |
| 4 | test encoding through redirects. | click-to-event match |
| 5 | preserve a lookup table. | filled-field rate |
Monitor freshness and delivery status: Sneket Partners SubID and ClickID
Application to Sneket Partners SubID Taxonomy for Clean Attribution
Handle partial outages safely: Sneket Partners SubID and ClickID
- ScopeFree-text labels fragment reporting.
- Datapersonal data should not be placed in SubIDs.
- Timinginconsistent case and separators create duplicate dimensions.