Return to Answer

It sounds like site B may have implemented a same-origin (or no-referrer) Referrer-Policy which affects the HTTP Referer header that browsers send with all outgoing links (in compliant browsers).

With a same-origin (or no-referrer) policy then no Referer header will be sent by the browser when following a link from Site B to Site A, so GA will not be able to report on this. Every link will look like a direct request.

Reference:

• https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy

UPDATE: Also check your server access logs to make sure there are no Referer showing Site B.

It sounds like site B may have implemented a same-origin (or no-referrer) Referrer-Policy which affects the HTTP Referer header that browsers send with all outgoing links (in compliant browsers).

With a same-origin (or no-referrer) policy then no Referer header will be sent by the browser when following a link from Site B to Site A, so GA will not be able to report on this. Every link will look like a direct request.

Reference:

• https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy

UPDATE: Also check your server access logs to make sure there are no (or very few) logged Referer showing Site B.

It sounds like site B may have implemented a same-origin (or no-referrer) Referrer-Policy which affects the HTTP Referer header that browsers send with all outgoing links (in compliant browsers).

With a same-origin (or no-referrer) policy then no Referer header will be sent by the browser when following a link from Site B to Site A, so GA will not be able to report on this. Every link will look like a direct request.

Reference:

• https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy

It sounds like site B may have implemented a same-origin (or no-referrer) Referrer-Policy which affects the HTTP Referer header that browsers send with all outgoing links (in compliant browsers).

With a same-origin (or no-referrer) policy then no Referer header will be sent by the browser when following a link from Site B to Site A, so GA will not be able to report on this. Every link will look like a direct request.

Reference:

• https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy

UPDATE: Also check your server access logs to make sure there are no Referer showing Site B.

It sounds like site B may have implemented a same-origin (or no-referrer) Referrer-Policy which affects the HTTP Referer header that browsers send with all outgoing links (in compliant browsers).

With a same-origin (or no-referrer) policy then no Referer header will be sent by the browser when following a link from Site B to Site A.

Reference:

• https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy

It sounds like site B may have implemented a same-origin (or no-referrer) Referrer-Policy which affects the HTTP Referer header that browsers send with all outgoing links (in compliant browsers).

With a same-origin (or no-referrer) policy then no Referer header will be sent by the browser when following a link from Site B to Site A, so GA will not be able to report on this. Every link will look like a direct request.

Reference:

• https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy