A campaign can involve a publisher article, a brand landing page and an enquiry form hosted elsewhere. It is tempting to treat every domain in that journey as one analytics configuration. The first question is simpler: which sites can your team actually configure and measure?
Make a map showing the domains, the owner of each one and the action a reader takes between them. A third-party publisher is not automatically part of the brand's own measurement setup merely because it carries a campaign link.
Separate referral traffic from continuity
For an external publisher article, record the incoming visit using the campaign measurement method agreed with the publisher and analytics owner. Do not assume access to that publisher's tags or visitor data. A transition between two sites you control raises a different question: whether analytics should recognise the same journey across those sites.
Google's cross-domain measurement documentation explains a configuration for measuring journeys across domains and a verification process. Its checks include following a link between configured domains and inspecting the destination's linker parameter. Redirects that remove that parameter can interrupt the intended transfer.
Give the analytics owner a bounded brief
List the real start page, the destination and any redirect or form service between them. Identify the analytics property and the person responsible for configuration. The brief should ask what can be measured, not assume that every vendor permits the same tagging or consent configuration.
Use a controlled test journey with no genuine customer details. Record the time, browser and expected next page. If consent affects whether analytics runs, document the test's consent state rather than treating missing events as automatic proof of a broken link. Do not put personal information into campaign parameters.
Illustrative example: article to enquiry
Illustrative example: a fictional sports software brand receives a visit from a tennis publisher. The visitor reaches the brand's main site, then follows a link to a separate enquiry domain owned by the same brand. The analytics owner reviews continuity between the two brand-controlled domains; the publisher remains the external referral source.
The team tests the redirect and checks the enquiry completion event independently. It records what happened in the test without claiming that one observed journey establishes campaign conversion performance. A successful configuration test and a commercial result are different pieces of evidence.
Do not hide unexplained referrals
If an unexpected domain appears in reporting, investigate the path before changing settings simply to remove it. It may be a real referral, a service in the journey or a tracking configuration problem. Keep a change record so future reports can distinguish a measurement change from a change in customer behaviour.
When selecting from the Route77Media inventory, agree the campaign destination through our placement service. If you use the free article-video offer, give the video its own agreed campaign link where appropriate. Keep the analytics configuration with the team that controls the destination sites, rather than expecting an article publisher to resolve every downstream measurement issue.
Sources
Sources checked 3 November 2026.