Proper Pixel Usage for Accurate Session Tracking Across Multiple Domains

Each Domain Requires Its Own Pixel:

A pixel created for one domain (e.g., example.com) should not be used on other domains (e.g., anotherdomain.com).

Using the same pixel across multiple domains can cause inaccurate session tracking.

Impact of Using the Same Pixel Across Multiple Domains:

Sessions on the additional domain (e.g., anotherdomain.com) will show as "/" (the root page) instead of the actual page visited.

The referrer URL will incorrectly point back to the original domain (example.com) where the pixel was created.

Example of Misconfiguration:

A pixel is created for example.com.

The same pixel is then used on anotherdomain.com.

Sessions on anotherdomain.com will show as visits to "/", and referrer data will point back to example.com.

Solution to Ensure Accurate Session Tracking:

Each domain should have its own dedicated pixel (i.e., one pixel for example.com and a different one for anotherdomain.com).

This ensures that sessions accurately track user behavior on the correct domain, and the referrer URL reflects the actual domain.