XML Schema Guide

Much of Bunting’s power comes from its knowledge of your products, and its ability to cross reference them with visitor profiles. You should now select a method of sending information about your products to Bunting.

 

Specification

Below are the specifications showing the mandatory, recommended and optional fields to allow your fields to be configured.

Benefits of using an XML within Bunting.

 

Unique Product Code <upc> Mandatory

The identifier for each product has to be unique within your account, and cannot be re-used. You can use any sequence of letters and digits for the product ID.

Type: Character Limit: Example Value: XML Example:
Text 250 Characters Max abc123 <upc>abc123</upc>
Important: Once a product has been submitted, the ID must not be changed when you update your data or be used for a different product at a later point in time.

Continue reading XML Schema Guide

Installation checklist

The purpose of this checklist is to give you assurance that every component of Bunting was installed correctly. This will give you troubleshooting advice about how to double-check and resolve any issues that might crop up.  It’s useful to do this immediately after completing the install to give peace of mind that you’re ready to begin using Bunting.

At a high level, the following should be checked:

  1. Conversions are being tracked by Bunting.
  2. Abandoned Carts are being tracked.
  3. Products in your XML feed match those on your website.
  4. Page specific Visitor Targeting will work correctly.
  5. On the Homepage.
  6. On the Category pages.
  7. On the Product Pages.
  8. On the Cart page.

Firstly, let’s deal with conversions. 💰

If you have installed the Conversion Complete Page script. Go ahead and do the following test:

Continue reading Installation checklist

How to set up a split test and measure the results!

When you create a piece of content with Bunting, you run through a 3 step process, Visitor targeting > Content > Measure Impact.

To set up split testing, all you have to do is change the drop-down under “Run a split test to measure impact?” on the Measure Impact page to Yes and let Bunting do all the hard work for you. Once you have done this click Save Changes and you are ready to start collecting Results when your Campaign is Activated.

Running a split test demonstration
Running a split test within the Bunting platform.

Where can I see the Results?

In the campaign lists within Bunting when a split test has been set up for the campaign you can see the results on the right-hand site similar to the image below.

If the Split test has not yet reached its confidence target within Bunting then it will still display that the split test between variations is still active.

If you click on one of these split test result figures it will take you to the Split Test Results page for that campaign and will display all the available metrics:

  • Converted Visitors
  • Revenue
  • Cart Products per Visitor
  • Visits per Visitor
  • Average Visit Duration
  • Bounce Rate
  • Product Views per Visit
  • Page Views per Visit
Split Test Results Page
Image showing split test results page within Bunting.

You can even select a specific variation to see the results for that variation at a much more granular level. Showing a graph of results as well as a history of the variation’s performance.

There is an advanced option to alter the amount of traffic that is able to view the split tests. The default for this is 50/50, but this can be catered to the specific campaign you are testing.

Advanced Split Test Screen
Advanced Split Test Results Screen

 

In addition to this, the confidence target can be changed. This is the metric that is calculated by Bunting as the probability for that variation to be the most effective. Once this target is reached it will deactivate the other variations.

All of the traffic is then routed to the winning variation from the deactivated variations and the control group.

To ensure there are no false positives Bunting will only automatically end the split test and show this campaign to all visitors when the confidence target is reached with more than 200 conversions.

Note: Google analytics has been turned on for this Campaign to further measure the impact. If you want to read more about Google analytics event tracking and what information Bunting passes to it click here.

What is a Product Data Feed and why do I need it?

Product feeds exist as a way of defining what products are within your inventory.

They include useful information such as the Product Name, Product Image, Stock Level, etc.

Bunting can read this data to begin attaching statistical probabilities that a user will purchase a particular product, and is the core of how the recommendation algorithm learns about your company.

What formats are supported?

We support XML and CSV/TSV formats.

What does it do?

This is where Bunting gains its knowledge of your products. This data is crucial to get the most value out of Bunting. A product feed with an updated index of products will allow the platform to provide much more efficiently.

Product feeds are ingested by default every 12 hours, and new products are then reasoned about.

Continue reading What is a Product Data Feed and why do I need it?

How to setup Multi Language support using Bunting?

How does this work?

Using Bunting you can set up Multi-Language support with ease, allowing translation for specific countries for text content as well as currency for the specific country.

This can be found from the within Bunting on a website monitor page. then selecting Settings to the right of the Performance button above the Personalization Cloud settings.

Setting up Multi-Language support within Bunting

This will set up the site in a way that allows the appropriate translation to be applied depending on the location in which the user is visiting the site from.

Server Side A/B Split Testing with Bunting

Server-side split testing with Bunting is quick and easy to set up with this guide. However, before we continue, it is important to define what a server side split test is in Bunting, and how it differs from a client side split test.

Definitions

Server side: Content is delivered from your servers before page load, not from Bunting after page load. Your server must define who to show content to, and informs Bunting via Javascript which variation/control group each visitor is in.

Client side: Content is delivered from Bunting’s servers via Javascript. Bunting handles the visitor targeting, and manages the distribution of visitors across each of the different variation/control groups for you.

Continue reading Server Side A/B Split Testing with Bunting

Does Basic Authentication on my website affect the use of Bunting?

The basic authentication is often used on staging sites, as a way of preventing unwanted access.

Basic authentication should not affect your use of Bunting, as Bunting’s javascript API is being called from your Basic Auth site, rather than the API requesting information from it. Therefore, you should be able to implement the javascript tracking code as you would on any regular website.

The only area that will be slightly different is the method that Bunting uses to collect your XML product feed, if that feed is also behind basic authentication. For this you will just have to enter your basic authorization username and password when you enter your product feed address into your Bunting account.

Should I include product variants within my Bunting XML feed?

Let’s say you have a product, such as a t-shirt, in several sizes. Should you submit the product several times in each size?

The answer is: no. You should only submit the product once.

To produce content, such as product recommendations, Bunting only needs to know general information about products, such as their names, prices, and image URLs, etc.

Including the same product multiple times in different variations can, and probably will, result in multiples of the same product being recommended at the same time.

Continue reading Should I include product variants within my Bunting XML feed?

How can test my Bunting installation?

To test your Bunting installation on any page, simply get your website URL and append the following value:

#bunting_installation_mode=yes

For example:

http://www.your-website.com/page.html#bunting_installation_mode=yes

An information popup will appear, containing all the data that is being sent from your website to Bunting. Your product pages should contain an indented section with the product ID, whereas your cart and conversion complete pages should also contain similar page-specific information.

Continue reading How can test my Bunting installation?