To integrate with your website, Fresh Relevance requires a JavaScript file that captures page, product, and cart activity. This allows us to power triggered campaigns using real browsing behaviour.
We’ve designed the script to minimise performance impact:
it is minified to reduce file size,
it is served in a non-blocking way so it doesn’t delay initial HTML parsing,
and it is cached to reduce repeat downloads for returning visitors.
As with any third-party JavaScript, the script still adds some network and processing overhead, but these measures help keep the impact low. Learn more about script attributes.
Checking what the script collects
You can see what the script is collecting on any page by opening the Site Info Bar. To open the Site Info Bar, expand the User menu and select Open Site Info Bar.
You can also inspect the data in your browser’s developer tools:
Open the page in Chrome or Firefox.
Press F12 to open Developer Tools.
Select the Console tab.
Look for the object containing page and cart information (for example, p or cart).
If the script URL looks unusual
When adding the script to your site, you may notice that the script URL does not start with `http:` or `https:`.
This is expected. The script uses a protocol-relative URL, which means it inherits the same protocol as the page it is loaded on, either `http` or `https`.
In practice, this means the script matches the protocol of the page automatically, which helps avoid issues such as security warnings.
This type of URL is widely supported by browsers and should not cause a problem when adding the script to your site.
In some cases, incorrectly coded bots or crawlers may log errors against this type of URL, but these should not affect the performance of your site or the script for real visitors.