Skip to main content

Revenue Boosting Webshop: Frequently Asked Questions

Answers to the most common vendor questions about the Revenue Boosting Webshop, from cookie consent to customisation limits.

D
Written by Deniz Ozakar

Haven't set up your Revenue Boosting Webshop yet? Start with quick setup. Looking to style it? See advanced settings.

My Revenue Boosting Webshop isn't showing up. What should I check?

This is almost always a cookie consent setting, not a bug — the widget only displays once a visitor's browser has the "Media" cookie category accepted. Check your cookie tool's documentation to confirm "Media" is included as a category. For example, if you use Contao Cookiebar, see their extended usage docs or cookiebar.html.

Can I adjust the border radius (rounded corners) of the widget button?

Yes — customize the button's corner radius using the global radius CSS variables. This lets you match the widget's look to your website's style.

What does the "Display AI chat" toggle on my widget settings do?

That turns on the AI Sales & Support Agent — a separate feature, powered by our partner Punku, that answers visitor questions and can hand them a prefilled checkout link. It uses the same embed code as your Revenue Boosting Webshop, so there's nothing new to install.

You don't have to decide at setup — you can turn it on whenever you're ready, and vendors running both typically see the best overall sales performance, since the widget and the agent work as two stacked conversion layers rather than one. Full setup and FAQs live in the AI Sales & Support Agent collection; see Revenue Boosting Webshop: advanced settings for where to find the toggle.

Can I customize the CTA button's text or font?

Not yet. Today, CTA buttons can only be styled using the palette configuration (colours and theme) — changing the text or font isn't available, though it's planned for a future update.

Can I show a longer description for each experience in the widget?

Not currently. The Revenue Boosting Webshop doesn't support long-form experience descriptions yet, to keep the widget lightweight — this is being explored for future updates.

Can I show open-date tickets if there's no fixed appointment in the future?

Yes — open-date tickets, Flexible Offers, and Season Passes are all supported in the Revenue Boosting Webshop. Select them the same way you'd select dated tickets or vouchers.

What languages does the Revenue Boosting Webshop support, and how is the language chosen?

The widget supports 27 languages: English (UK), German, French, Spanish, Italian, Dutch, Czech, Finnish, Danish, Norwegian, Swedish, Greek, Japanese, Polish, Portuguese, Chinese (Simplified), Hungarian, Latvian, Lithuanian, Estonian, Slovenian, Croatian, Slovak, Romanian, Bulgarian, Russian, and Ukrainian.

By default, it's automatic: the Language setting on the Palette tab is set to "auto detected language," meaning the widget picks up your visitor's browser language, falling back to English if that language isn't available. To force a specific language instead of auto-detecting, set it directly on the Palette tab, or — for developers — pass a data-locale attribute (e.g. data-locale="de-DE") on the <bk-floating-widget> element, which overrides both the setting and the browser fallback.

This is the widget's overall language. To override just the trigger button's label text per language, see the next question.

How do I localize the trigger button's label per language?

Use the data-localisation attribute on the <bk-floating-widget> element:

<bk-floating-widget
data-widget-id="[WIDGET_ID]"
data-localisation='{
"de-DE": { "floatingWidget": { "trigger": { "label": "TICKETS" } } },
"en-GB": { "floatingWidget": { "trigger": { "label": "TICKETS" } } },
"sv-SE": { "floatingWidget": { "trigger": { "label": "TICKETS" } } }
}'>
</bk-floating-widget>

To implement this:

  • Replace [WIDGET_ID] with your actual widget ID.

  • Update the locale codes (e.g. de-DE, en-GB, sv-SE) to match the languages you want to support.

  • Set the label text for each language.

  • Add this code to your website wherever the widget is integrated.

This can't be done through CSS or backend settings alone — the trigger label requires this code change on your site to take effect. Worth looping in a webmaster if you need this.

How do I know my Revenue Boosting Webshop is tracking bookings?

It's automatic — page views, item views, clicks, and the full booking funnel are sent to your window.dataLayer as soon as it's live. See the Analytics section in quick setup for details.

Related articles

Back to setup

Did this answer your question?