ENGINEERING NOTE 50 / 50 · BOTH
Trace technical content to registration without inventing attribution
A published link, a visit and a new registration are different events. Keep campaign parameters through navigation and exclude known test accounts before reporting acquisition.
Published by OPEN RAMBO. The engineering patterns and pseudocode illustrate designs, not a documented product API. Numerical examples are illustrative.
Give content a stable identity
Use a campaign identifier and article identifier, with a separate source for each external community. Do not overwrite the external source with an internal button label. Keep internal CTA identity separate or retain the incoming parameters when constructing the registration link.
Separate measurement from inference
A registration carrying a valid article tag is measured link attribution. A user saying they found the site on a forum is self-reported evidence. A blank source is unknown unless another reliable record connects it; do not distribute unknown users proportionally to campaigns.
Report the funnel honestly
List published pages, observed visits, registrations and excluded tests separately. Internal QA visits should be tagged or filtered. Neither HTTP checks nor editor previews count as reader traffic, and a test signup does not establish a new customer conversion.
Illustrative implementation
utm_source=community_name
utm_medium=technical_article
utm_campaign=technical_library_20261027
utm_content=en-article-slugAcceptance check
Follow a tagged article link through its CTA and inspect the registration URL without creating an account. Verify real registrations separately from persisted acquisition fields.