tvScientific offers a range of ways to track events from your website and mobile app. Below you will find descriptions of the tracking methods we offer — refer to the links to find the guide you need.
Website Tracking Methods
Pixel Tracking
JavaScript pixel tracking is a method of tracking and reporting conversion events to tvScientific. It consists of JavaScript code snippets placed in your website code.
usually with a tag manager. Pixel tracking, also known as client-side or in-browser tracking, is reasonably the most common method because of its simplicity.
This integration requires a skilled web developer comfortable with JavaScript, HTML, tag managers, and browser developer tools to configure, install, and test.
Postback Tracking
Postback tracking, also known as server-to-server (S2S), server-side, or server call, is a method of tracking and reporting conversion events to tvScientific. A postback transfers event information from your server to another vendor's server (tvScientitifc) and the client is not engaged in this transfer. The transfer happens in the backend (vs pixel where the tracking is client-side). This method operates without the user’s browser, instead, it relies on the advertiser servers to send an HTTP request to tvScientific.
This integration requires a skilled developer, a server, and technology to send postback requests. Postback integrations are typically more expensive and complex to implement.
Mobile App Tracking Methods
Mobile Measurement Partner (MMP) Integrations
tvScientific can integrate with your MMP, allowing tvScientific to receive event data through automated postbacks.
Direct Postback Tracking
Postback tracking, also known as server-to-server (S2S), server-side, or server call, is a method of tracking and reporting conversion events to tvScientific. A postback transfers event information from your server to another vendor's server (tvScientitifc) and the MMP is not required for this transfer. The transfer happens in the backend. This method operates without the advertiser's MMP and requires the advertiser's server to track all in-app and install events.
This integration requires a skilled developer, a server, and technology to send postback requests. Postback integrations are typically more expensive and complex to implement.