The OneSpot Script and CSS tags

Getting Started > The OneSpot Script and CSS tags

Nothing happens until our tag is placed, but don’t worry, it’s not hard to do.

Why do we need the tag and CSS?

Before we can personalize your site or email, we must first understand the content on your site and who is looking at it. This is accomplished by placing a small tag in the pages of your website.

The OneSpot script tag allows us to ingest all your content, observe and track visitor engagement with your content, anonymously map your website visitors to your email subscribers and inject content back into your site to personalize the experience. For more information on what the OneSpot script tag does, see What Does OneSpot’s Script Do?

The OneSpot CSS tag allows us to make CSS changes related to Onsite A/B tests. When we’re conducting A/B tests in which Onsite units replace elements of your site (control units), we use the CSS file to make the control units invisible on page load. Our script quickly executes and determines whether the user is in a test or control group, then either makes the control units visible, or replaces them and shows the Onsite units. We do this in order to prevent a flash of Onsite units replacing control units for a better user experience.

Where to put it

The OneSpot script tag should be placed in the header of your site and should be published to all content pages and any page where user behavior should be observed. If there are any specific instructions for your site, your implementation lead will discuss that with you.

IMPORTANT Do not place the OneSpot tags inside an iFrame. If you do, it won't work.

The OneSpot CSS tag should also be placed in the header of your site, below any other CSS file inclusions.

IMPORTANT The OneSpot Script and CSS files must be loaded from our hosted locations. To function properly, the source of these files should not be bundled or copied into your own files.

WARNING Do not use a tag manager to implement the OneSpot script. Implementations via tag managers such as Google Tag Manager will not allow the service to operate properly.

Content-Security-Policy Headers

If your site servers employ Content-Security-Policy headers, you will likely need to whitelist the following domains from which our script is loaded. Please whitelist the following domains:

Whitelist Domain

https://d2vxvnufz8f5c5.cloudfront.net
https://d2gxssc8hszgww.cloudfront.net

What does it look like?

The tags will be provided by the OneSpot team and will be configured specifically for your site. Below is an example. This tag should not be used as it is just a sample.

Sample OneSpot Tag (Again, do not use this one)

<!--START ONESPOT SCRIPT-->
	<link rel="dns-prefetch" href="https://d2vxvnufz8f5c5.cloudfront.net" />
	<script src="https://d2vxvnufz8f5c5.cloudfront.net/4xrt6r.bundle.js" async></script>
<!--END ONESPOT SCRIPT-->

<!--START ONESPOT CSS-->
<link rel="stylesheet" type="text/css" href="https://d2vxvnufz8f5c5.cloudfront.net/4xrt6r.css" />
<!--END ONESPOT CSS-->

Will the tags slow down my site?

No. We have conducted multiple tests to demonstrate that site performance is not impacted by the presence of the OneSpot tags. It script loads asynchronously and will not hold up anything else.