Data analytics are used for reviewing, gathering, and targeting information based on interactions with a webpage or service. These tools can help businesses or organizations make driven decisions based on discoveries or insights from data captured. For example, if you create a website, an administrator can review reports which include data analytics, this can include anything from how many viewers or which pages interacted with on your website.

Tracking or marketing pixels are an HTML code that can be added by developers or administrators (and are usually hidden) on websites which can help also track data analytics. Tracking pixels can be used to capture advanced user interactions, such as unique clicks, advertisements visitors click on, and more. Tracking pixels are also available for different insights, such as for retargeting or conversion data. There are free resources on the web which can help teach or guide you on how to use tracking pixels. You can click here to learn more about tracking pixels from Digital Marketer.

In this case, while using tracking pixels on websites, users will commonly add websites or links into ScreenCloud to display on digital screens. In the background, tracking pixels are still running actively and acquiring data for active user data relating to site visits. For example, this means that each time the ScreenCloud app loads your website to display on the screen that a tracking pixel may treat this as a unique viewer or click each time the page is loaded. This can cause your unique clicks to possibly spike or result in tracking viewer data which is isolated to the ScreenCloud app loading, but the tracking pixel does not know by default that it's an app displaying your webpage.

In order to preserve your tracking data and ensure your pixel is capturing accurate information, you can exclude or create a rule for using the ScreenCloud app from being captured as a unique viewer or click for a website or link. This is not controlled by ScreenCloud as the pixel or analytic tracker is managed from the backend of your website or server directly.

The pixel is triggered due to ScreenCloud acting and serving content through the ScreenCloud Player App as a normal browser. We advise excluding a specific set of source IP addresses associated with our servers, you can also change it if AWS (Amazon Web Services) allows to re-allocate Elastic IP addresses. This is information our team recommends to pass onto your web developer or administrator who manages your analytics tools directly and see if it's possible to exclude ScreenCloud as a unique or triggered viewer in your tracking reports.

If you're unsure of how to proceed, you can Google or search for free resources which include topics such as: