• How is website data collected and is it accurate?

    Episerver Personalization receives tracking information from every single page on your entire website. The exact method for transmitting this information depends on the integration type chosen. The Personalization tracking allows us to collect user's interactions with the site and map each user's individual behavior and customer journey as they browse the site. We will know whether the user converts or whether they leave the site without purchasing anything. We will also know whether the conv...

  • Can you provide an example of the JSON tracking code?

    Examples of the tracking code are provided in the JavaScript API integration guide, however your Project Manager can provide you with bespoke examples that are specific to your site as part of the integration process.

  • Where should the one line of tracking script be placed?

    If you are using the JavaScript API to integrate Episerver Personalization on your website, the one line tracking script should be placed just above the closing </body> tag and before any Google Analytics scripts or slow loading social media tags. <script type="text/JavaScript" src="//clientname.peerius.com/tracker/peerius.page" charset="UTF-8"></script>

  • Is the tracking code required on all pages?

    The tracking code is required on all pages that are relevant to the customers purchasing experience. If you use the JavaScript API integration, make sure that the PeeriusCallbacks.track variable is defined and that you are calling the tracking script on all pages. <script type="text/JavaScript" src="//clientname.peerius.com/tracker/peerius.page" charset="UTF-8"></script> If you use the server-to-server API or Episerver Native integration, make sure that a tracking request is sent from the ser...

  • Can you flag pages without tracking code as “other” automatically?

    Unfortunately this is not possible. You need to configure the tracking code on all pages of your site so that they can be tracked by Episerver Personalization.

  • Why do we need to track “unimportant pages” like landing pages, content pages etc?

    It is important that we track the customers' entire journey and therefore need to be able to track all pages. Our personalization engine considers all previous browsing and purchase behavior of a user to create personal profiles for each visitor that, together with placing the emphasis on the intent of the current session, allows for personalized recommendations at individual level and not segment level, resulting in in-session, real-time personalization at each step of the user journey.  

  • What page types are considered as ‘other’ for implementing tracking?

    Any page types that are not within our defined page types are considered as ‘other’, therefore anything that is not one of the following pages: home product category basket checkout order searchresults brand attribute wishlist

  • How long does the Episerver Personalization tracking code need to be on the site before we can start showing recommendations?

    This is dependent on the number of products and the volume of orders/traffic that your site receives. There is no definitive time however the Episerver Personalization team will monitor the coverage of our algorithms and as soon as there is sufficient coverage they will be able to configure the recommendations.