Easy Installation

Instructions on how to install HiConversion on your site

Click your eCommerce platform logo to begin your installation process:


HiConversion tag is a small JavaScript code snippet that integrates your website with HiConversion’s customer experience optimization cloud. The code snippet contains a unique Site ID.

Web browsers execute this code to download all additional code and content from HiConversion’s cloud that your site needs to run tests and personalization experiments in real time.

In addition, this code is used to send back all visitor tracking data via single pixel image download.


HiConversion’s tag is a small JavaScript code snippet that should be added to all pages of the site.

Depending on the server side technology the site tag can be added in two different ways:

  • Manual installation: IT person directly places HiConversion code at the top of the <head> tag of all web pages.
  • Connector: natively integrated eCommerce platforms (see the list above) enable HiConversion installation through use of a platform specific connector.


Here is what happens when HiConversion tag is active on a site:

  • The HiConversion code snippet is embedded into the web page and delivered by the website server to a visitor browser whenever visitor lands on any page or site that is HiConversion enabled
  • Web browser executes HiConversion’s code snippet whose mission is to call back the HiConversion’s customer experience optimization cloud and request further instructions
  • Based on the end user setup the HiConversion’s cloud will respond in the following ways:
    • this page is not active (none of HiConversion’s applications is running a live experiment) – here is the code for tracking web visitor activity
    • this page is active (there are one or more live experiments), here is the code and content needed to make user specific web page changes – track web visitor activity
  • Web browser executes the code received from the HiConversion cloud
  • Visitor tracking data is send back to HiConversion’s cloud via single pixel image call

If a page was active, web browsers will manipulate the existing web page and render a new version for a specific visitor to see. A visitor has no idea that he is seeing a new version of the page since all of this happens in milliseconds.

Technically speaking

The information below is for those who are more technical and desire to understand specifics of all network calls.


{Client Specific HiConversion Site ID}
Asynchronous core tag, includes all Client and Campaign settings for collecting analytics and running experiences.

Asynchronous fetch for end-user specific segmentation data. For example geographical and device characterization data.

Pixel Call

All data is passed back to our system through requests to this pixel as parameter. This includes client segmentation data, page data, test delivery results, product data, cart data, and standard and custom events (such as clicks and loads). This call may fire many times in a single page with varying parameters.

Yes, but only if your tag management solution can inject our tag into <head> section of the web page. Unfortunately, many major tag management solutions can only place tags in the <body> tag section of the web site pages.

The main purpose of our tag is to enable real time content and layout changes on your site. Therefore, our tag needs to load as soon as possible so that we can transform your web pages without any page flicker (i.e. user seeing one page element being replaced with a new one).

Nothing visible.

HiConversion tag will act like Google Analytics or similar tag. Its mission is to track visitors and visitor activity anonymously.

A complete installation requires tag placement and site configuration:

Native integration: If you used native integration connector to add HiConversion tag, your installation is complete. Our system will automatically recognize your site organization and collect all eCommerce transaction details.

Direct integration: if you added HiConversion’s tag directly, then a technician needs to manually configure your site setup. This is done within the Site Settings interface. Feel free to ask for HiConversion’s free assistance.

At any time later you can configure your custom goals, segments, pages, users, etc.

Our solution enables tag implementation testing. Just go to HiConversion’s console and Admin > Tag Integration section to run the test.

You and your visitors will not be able to visually detect any abnormalities. Our tag operates in asynchronous mode, enabling unaltered page content to load in parallel. In the unlikely case that HiConversion’s service is offline, web browsers will ignore our script and render the unchanged web page as if we do not exist at all.

HiConversion’s tag is designed to collect only non-personal data. This includes visitor session meta data about pages visited, time on site, actions taken, products purchased, etc. Please check our Privacy Policy for more information.

The universal tag will not be changing at all. The native integration capabilities might change from time to time to stay in sync with the new capabilities of evolving e-commerce platforms. However, we will always be backwards compatible so that you can update your integration at your own choosing.

The increase in the page load time is minimal.

The HiConversion tag is loaded and executed by the browser in parallel with the rest of the page content loading. Depending on the campaign, it might take 100ms-300ms to load the optimization instructions and content. However, since this happens in parallel, the net impact on page load time is less than 200ms.

The simplest thing to do is to go into the HiConversion App in your Shopify admin and toggle the enable/disable button so that the tag gets re-injected into your theme. This can occur at times if edits are made to the theme.


Absolutely not. We are like your traditional web analytics solution that tracks visitor attributes and visitor behavior, like page loads, or clicks.

Since HiConversion doesn’t process, store, or transmit credit card information, most of the compliance requirements are mitigated.

HiConversion is, however, often used on the pages in a checkout funnel where visitors are asked to enter their credit card details. Although HiConversion doesn’t transmit or process data at this point, this is a touchpoint with your visitor’s customer data. Generally, any system that could potentially be used to get to your visitors’ credit card data is within scope of PCI DSS and therefore has to adhere to the strict rules the payment industry has worked out to protect cardholder’s sensitive information.

There are two options for using HiConversion in compliance with PCI DSS.

Option 1: do not place HiConversion’s tag on the page where visitor can enter payment information.

You can deploy HiConversion’s tag on all other pages. There will be no impact on your PCI DSS compliance.

Option 2: embed a Credit Card form field through an iFrame
If you want to remove HiConversion from the scope of PCI DSS compliance completely, you can choose to add the actual form field where customers enter their credit card details onto your page through an iframe or redirect users to a payment page hosted by your payment processor. This is the case with many popular payment processors such as Stripe, Paypal or Adyen.

HiConversion code then can’t access these fields, essentially shielding it from our snippet. On the down side, you also won’t be able to change these fields and optimize them without actually making a separate version of this form available.


We designed our TOS to be industry-standard so that it meets the needs of all types of companies. Our TOS are happily being used by a wide range of our customers, both big and small. So we prefer to keep it standardized to be fair to all types of customers who use HiConversion. If our TOS don’t meet your needs, please contact us and we’d be happy to help.