Getting and Installing Web Tracking Script

To get the web tracking script, go to your account settings → Web tracking tab, and click Start the web tracking.

Getting and Installing Script

1. Enter your domain name and click Get script.

📘

Note

The script works for second-level domains and subdomains (mysite.com, blog.mysite.com). It is generated per domain, and the interface doesn't support setting up web tracking for a second, unrelated domain within the same account — to track one, use a separate account.

2. Copy the script and add it to the page code before the closing </body> tag on every website page.

📘

Important

Install the script on both desktop and mobile versions of your website.

Checking Script Status

After installing the script, click the Check status button.

If there are any problems, you will see a warning message with a hint.

When the installation is completed successfully, the status will change.

📘

Note

You can also check whether the script is installed on a specific page in the browser console: the window.eS object must exist (not be undefined). If 'eS' in window returns false, the script isn't installed on this page.

Now you can return to the main web tracking page, where user activity on your site is tracked (Settings → Web tracking).

Here, you can see the number of page views yesterday and today and how many are unique. The Additional events list will not display statistics until the product feed is loaded into the system and these events are configured. After processing, events appear in the list automatically; there is no fixed refresh interval, so new events can appear with a delay. For stable operation of events, we recommend configuring their sending by calling eS.JS functions. This method allows you to independently control the transfer of data and promptly respond to changes on the site.

🚧

Important

If you install a script via Google Tag Manager or any other tag manager, you may lose tracked data as it may be blocked by content filters.

FAQ

Does installing the script affect SEO? No. Placing it before the closing </body> tag means it loads after your page's content, so it doesn't block rendering or interfere with how search engine crawlers index your page.

Is it safe to install? Yes. The script only collects the behavioral and contact data needed for tracking and doesn't require exposing any sensitive credentials on the page.

Should I load it via a tag manager for better performance? We recommend a direct install instead — as noted above, tag managers can be blocked by content filters, which may cause tracked data to be lost.

How do I test tracking and recommendation blocks on a development environment? Install the web tracking script on the development site and configure event sending there, the same way you would on production. A separate account for testing isn't required.

Can I send events from the site frontend instead of the backend? Yes. Sending events with the script in the browser is a standard integration method and doesn't require server-side development. The script can't be restricted to a specific domain, and there are no separate reduced-permission credentials for it. If your security policy requires the calls to be made server-side, you can move them to your backend — this is implemented on your side.