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.

(more…)

‘Bunting’ Terms of Service

This agreement (the “Agreement”) is a legal agreement between the Customer and Bunting Software Ltd (a company registered in England and Wales with company number 08712116) whose registered office is The Media Centre, 07 Northumberland Street, Huddersfield, West Yorkshire, England, HD1 1RL (“Bunting”).

Bunting permits use of the Software Services and Documentation by the Customer on the basis of this Agreement. By checking the box confirming the Customer’s acceptance of this Agreement, the Customer agrees to be bound by the terms of this Agreement.

Bunting and the Customer now agree as follows:

(more…)

Removing / Updating Product Accolades

Every product accolade within Bunting has its own CSS class. These are listed as follows:

  • .bunting_accolade-most_popular
  • .bunting_accolade-best_seller
  • .bunting_accolade-lowest_price
  • .bunting_accolade-last_one
  • .bunting_accolade-last_chance
  • .bunting_accolade-best_offer

(more…)

My tracking code isn’t working

A common cause of this issue is when a Bunting user has multiple websites, and has copy/pasted tracking codes between websites.

Each website set up on Bunting has a unique tracking code especially for that site. Therefore, if you set up more than one website on Bunting then don’t copy across the tracking code from your other sites. Instead, go to the Installation page (under Setup) in your Bunting account, and get the new tracking code from there.

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.

(more…)

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.

(more…)

Will Bunting slow down my website?

Bunting won’t affect your website’s speed at all. Our Javascript loads asynchronously, just like Google Analytics. This means that it loads in the background, and so won’t ever cause your site to pause while loading. Even if our servers were to fail completely (which wouldn’t happen as they are well backed up) then your website would be completely unaffected. The only difference would be that content delivered by Bunting simply wouldn’t load. Your website would just look as it did before Bunting was installed.

(more…)

Triggered emails not being sent / arriving in inbox

Are email going into spam folder?

How to Diagnose: Check your inbox – are the emails landing in your spam folder? If the inbox is a Gmail account then check the ‘Promotions’ tab as, being promotional, Bunting’s triggered emails often land in here.

Explanation: Bunting’s triggered emails (abandoned cart, ‘we miss you’, etc) are promotional in nature, and email clients like Gmail will often categorise them as such. Likewise, email clients with spam filters set high might automatically redirect Bunting’s emails to the spam bin, depending on the wording you use in your email. For example, words like ‘sale’, ‘offer’, ‘discount’, etc will often trigger spam filters.

Orders aren’t being recorded correctly

Is the order code correct?

How to Diagnose: Get a copy of the order confirmation (‘thank you’ page) javascript code, as it appears on the website. Look for the value within the following variable

$_Bunting.d.uc = “value“;

Does this value match that on the installation page script within your Bunting account?

Explanation: The value of the $_Bunting.d.uc variable in your order complete ‘thank you’ page must not be edited, and must be the same as that detailed within the installation page on your Bunting account. Please update the script, ensuring that the $_Bunting.d.uc value is the same as on your installation page.

1 2 3