Product capabilities
Combining Source Parameters and Referrer Filters
Campaign parameters express intended attribution while referrer data describes part of the observed path; neither field independently proves origin.
Create a canonical source vocabulary
Define stable values for network, campaign, placement, and creative before links are distributed. Normalize capitalization and encoding at link creation instead of maintaining many rule aliases for the same acquisition source.
Use referrer as contextual evidence
Browser policy, redirects, applications, privacy settings, and direct navigation can suppress or shorten referring-page information. Model expected domains where useful, but keep missing and contradictory values as explicit cases.
Remember that public fields are client controlled
Query values and headers can be copied or forged outside the intended campaign journey. When stronger assurance matters, correlate them with tracker identifiers, signed server context, or additional request evidence appropriate to the integration.
Specify how conflicts resolve
Decide what happens when a known source tag arrives without a referrer, an allowed referrer carries an unknown tag, or redirects expose an intermediary domain. A clear precedence table prevents small template changes from silently moving large traffic segments.
Test every material acquisition path
Open ads inside source applications, hand them to external browsers, follow tracker redirects, copy the final link, and remove selected parameters. Compare received context and destination decisions with the documented contract after each route.