MONITORING 2.0
In the near future, web browsers will limit the use of third-party cookies — cookies from external websites that have so far made it possible to track users across different sites and target ads precisely.
This is a result of growing user expectations regarding privacy and increasingly strict GDPR regulations.
Therefore, companies must transition to first-party cookies — data collected directly on their own website, with the user’s explicit consent.
This is not only a necessity but also an opportunity: first-party data offers greater control, regulatory compliance, and the ability to build stronger, longer-term relationships with customers.
The transition to first-party data requires the implementation of the new iPresso tracking code on all subpages of the website.
This is a key element — without it, it’s not possible to collect data directly from users.
The new code replaces previous solutions based on third-party cookies and enables tracking of visitor behavior in a way that meets user expectations and remains fully under your control.
Only full implementation across the entire domain will ensure complete data collection and proper system operation.
Adding a new site
To add a new website, you must provide its address. It’s important that this is only the main address — without subpages, e.g.:
- Correct: https://my-site.pl
- Incorrect: https://my-site.pl/news
All subpages within one domain should use the same monitoring code. It is enough to generate one code to add it to each subpage - no need to create separate ones for subpages. However, it is necessary to add each subdomain as separate pages.
You can also enter just the domain name, for example:
In both cases, this will be just “my-site.com” (without the protocol). This way, these sites will share anonymous visitors whose cookies will be set for the specified domain.
Tracking code
After adding a website, you can download its tracking code. This code should be placed in your website’s source code — either in the <head> or <body> section.
You can also embed it via Google Tag Manager (GTM).
On the monitored sites list, click More options — there you can download a .txt file containing the full script to paste into your site’s code. You must not place more than one tracking code on a single page.
Proper embedding of the new code on your website is essential for the entire system’s operation. This enables data collection about user visits (tracking visits to monitored sites activity) and activation of additional features, such as recommendation frames or On-site actions.
The code also provides a JS API — a set of tools that allows integration with other elements of the website. Without its implementation, these mechanisms simply will not work.
How to transition to the new tracking system?
Updating monitoring requires several actions on the client’s side.
You must update the tracking code and replace JS API methods on all pages integrated with iPresso.
To ensure the entire solution works properly, this process should be carried out in cooperation with our team. This allows us to properly adjust settings on our side and guarantee full system compatibility.
Below are the steps to follow:
-
Activate all necessary “JS API V2 Method Settings” for the monitored website being migrated.
-
Replace the tracking code on the website (either directly in the source code or via Google Tag Manager, depending on where the previous code was placed).
-
If the website collects Web Push tokens, take the following additional steps:
- Upload the ServiceWorker file to your website’s server (available for download in the web push settings of the monitored site). It may have a new name, e.g. pushServiceWorkerV2.js.
- As soon as possible after uploading the file, update the ServiceWorker address in the settings if its name or location has changed. This will minimize the time during which token collection may not function correctly.
- Upload the ServiceWorker file to your website’s server (available for download in the web push settings of the monitored site). It may have a new name, e.g. pushServiceWorkerV2.js.
Replacing the tracking pixel
Since the new tracking system is based on first-party data, the previous pixel (e.g., used when adding a contact via API) will no longer work correctly.
To ensure contact tracking in the browser works according to the new model, you must use the new methods described in the Identification section. These methods allow you to correctly associate a user with their On-site actions.
JS API documentation is available at:
https://ipresso-js-api-doc-v2.web.app/methods/identification/set-contact-id
Comments
0 comments
Article is closed for comments.