Integrations

Your developers add our script to your website once, then place a tag wherever an experience should appear, such as Sofa Configurator on a product page. The script works with any website, and every experience runs in a secure frame, kept apart from your code.

Platforms our customers run

  • Shopify
  • Salesforce Commerce Cloud
  • THG Altitude
  • Magento
  • Custom

One script, one tag

Your developers add our script once and place a tag where each experience goes, with no JavaScript written against our code.

Any front end

React, Vue, Angular, plain HTML or server templates such as Liquid and Twig, with no SDK to install per framework.

Placed by product

Pass a SKU and the experiences for that product load automatically. A product with no experience simply shows nothing.

Several experiences on one page

Each experience sizes to fit the content and resizes automatically, so any number can share a page.

Google Tag Manager route

If your team can only add code through Google Tag Manager, there is an install recipe for that.

Your own basket

Experiences send the chosen products and quantities to your cart with a custom connector.

Through to your product pages

Shoppers can click from inside an experience straight to the product page on your site.

Locked down by default

Experiences cannot open dialogs over your page or use the camera, microphone or location, and experiences only accept messages from our CDN.

Every step a shopper takes

We record when an experience loads, appears on screen and closes, which features shoppers use, which products shoppers see and click, and every wishlist, add to basket and checkout.

Successes and failures

Every add to bag attempt is paired with the result, so we can detect failed attempts.

Credited to the experience

Each product is attributed to the experience responsible, across sessions and subdomains, through to a completed checkout.

Clean numbers

Bots can be filtered out, and campaign parameters are stripped from page addresses so each page counts once.

Nothing personal stored

Events are linked by a short-lived session id rather than a user id, so no personal data is stored.

By device and place

Every event carries the browser, operating system, device type, country and city, with currencies converted.

Any source

HTTPS, SFTP or FTPS, or straight from your Shopify store with variants merged and metafields as columns.

Any format

CSV and other delimited files, XML or JSON, mapped to our product model by configuration rather than code.

On your schedule

Each feed runs on a set schedule, every two hours by default, and skips processing when nothing has changed.

Checked on every load

Ten default checks cover links, photos, dimensions, price and category, and your own rules can be added.

Safety stops

A load stops if the file is unexpectedly small or would delete too many products, so a bad export can't empty your catalogue.

Your APIs too

Experiences can call your own stock, recommendation or content services, when the experience is built or while shoppers use the experience, and fall back to the last good answer if a call fails.

FAQ

Does Hullabalook work with our platform?

Yes. Hullabalook works on any front end, from Shopify and Salesforce Commerce Cloud to custom React or Vue sites and server templates such as Liquid and Twig.

Do our developers have to write code?

Your developers add our script once and place one HTML tag where each experience should appear, with no JavaScript written against our code.

Can we add Hullabalook through Google Tag Manager?

Yes. There is an install route for sites that can only add code through Google Tag Manager.

What does our security team need to know?

Your Content Security Policy needs to allow your Hullabalook CDN address. Each experience runs in a sandboxed frame that cannot open dialogs over your page or use the camera, microphone or location.

What product data do you need?

A product feed in CSV, XML or JSON over HTTPS, SFTP or FTPS, or a connection to your Shopify store.

Do you store personal data?

No. Events are linked by a short-lived session id rather than a user id, so nothing personal is stored.

Got an integration question?

A thirty-minute call with an engineer usually answers every one.

Talk to an engineer →