Show widgets on specific pages of your website

Same bubble. Different page, different door.

The rules belong to the block, not the bubble. Booking, live chat and callbacks can share one bubble and each decide for itself where to show. What turns that into a fork is three choices: the page rule on each block, the list each door files people in, and the goal that counts what each door earns. This is the whole fork, stop by stop, with a tester for the rules and what a month costs.

Flow 04 · The page fork
01 The page and the device arrive 02 Each block checks its own rules 03 The door that passes opens, and its goal counts
01 / Rules

Give each block its own rules.
Not the bubble.

A bubble is a stack of blocks, and every block has an Audience & Rules panel of its own. When the widget loads on a page, each block is checked against its rules and the panel lists only the ones that pass. One script tag can then serve the visitor comparing prices, the one at checkout and the one on a phone, without three versions of your site.

Page rules
Include or Exclude the pages whose address matches: wildcard, equals, does not equal, contains or does not contain. The check is against the full address, query string included, and a block has one rule.
Device
Mobile, Desktop or All. A tablet is neither of the first two, so only blocks set to All show on one.
Visitor
New, Returning or All. Someone stays new for five minutes after they first arrive, then counts as returning.
Source
Traffic Source (Referrer) is text the previous page’s address has to contain, like facebook.com. Past the first page the previous page is your own site.
Handoff 01 → 02
Floating BubbleDoors
What travels
the page address the device new or returning
The one setting
On each block you want to limit, open Audience & Rules (the beaker icon), switch on Page Rules and give it one Include rule: contains, and the part of the address that names the page, such as /pricing.
02 / Doors

Three doors for three moods.
Each files a list.

Say people compare on your pricing page, hesitate at checkout and would rather talk when they are on a phone. A Booking block gives the first a calendar, Live Chat gives the second an answer now, and a Callback block lets the third leave a number. All three end the same way: the person is added to a leads list you choose, so sequences and broadcasts can reach them afterwards.

Booking
Everyone who books joins the list under Add bookers to, and the meeting’s reference, start time and timezone are kept on the lead.
Live chat
Switch on Ask for a name and email, and add visitors to a leads list and chat visitors join the list under Add chat visitors to. Leave it off and they go straight into the conversation.
Callback
Each request joins the list under Add callbacks to, with the time window, timezone and topic they gave kept on the lead.
One person
Someone who chats at checkout and books on pricing is one lead, not two, and is only charged as new the first time.
Handoff 02 → 03
DoorsUser Journey
What travels
a lead in its list where it happened when it happened
The one setting
In User Journey, create one goal per door. Choose Uses your widget, then Books a meeting, Starts a live chat or Asks for a call back. There is no page and no selector to set up.
03 / Count

One goal per door.
Then read where each is reached.

A goal of the type Uses your widget listens for the door itself, on whatever page it opens. It is decided on our side from what the widget reports, so an ad blocker cannot hide it, and each goal keeps a report of its own. One panel in it, Where it was reached, answers the question the rules raised: on which page did this door earn?

The goal
Uses your widget needs no setup. Other actions in the list include Leaves their email, Asks the AI assistant and Opens a support ticket.
The page
Where it was reached lists “the page each conversion happened on”: the latest page User Journey had recorded for that visitor.
The source
Where converters come from shows each source’s conversions and its own conversion rate, so an ad that sends many visitors but no bookers shows up.
The person
On the lead, and on a chat, a panel called Their journey shows where they first came from, how many pages they saw and which goals they reached.
04 / Try it

Pick a visitor.
See which doors they get.

A tester built from the widget’s own checks. Choose a page, a device and who is visiting, change the Booking block’s rules, and see which of four blocks the bubble would list: Booking, Live chat, Callback and an FAQ with no rules at all. Start with a case from the row, then break it on purpose. The checks are the ones the widget runs on every page: where the visitor came from, their device and type, the page rule, and for chat whether anyone is online. Where a block fails more than one, the tester names the first. It is a model of those checks, not the product.

Try it · one visitor, four blocks The widget’s own checks
Try a case
The visitor
Device
Visitor
Someone on your team has Live Chat open
The Booking block’s rules
edit them
Page Rules
Condition Type
Device
Visitor Type
Keep an FAQ block with no rules
What the bubble lists
Doors open1 / 3

Why, block by block
05 / The cost

Four things have a rate.
The rules do not.

Page loads with the widget on them are 10 credits per 1,000. A new person who joins a list is 1 credit, whichever door they came through, and only once: the same person on a second list does not cost again. A live chat that starts is 1 credit more, and each tracked visitor journey is 0.1 credits. Every account gets 250 free credits a month, and packs start at $9.

Credit meter · one month of the fork Rates from the rate card · 250 free every month
5,000

Every page a visitor opens with your widget on it.

40

Each new person who books, asks for a callback or leaves their details in a chat.

15

Each conversation a visitor starts with your team.

800

Each tracked visitor journey is one unit.

Credits a month
185
Free every month
250
250 free
  • Page loads 10 credits per 1,000 50
  • New people 1 credit per new person, once 40
  • Live chats 1 credit per chat started 15
  • Visitor journeys 0.1 credits per tracked visitor 80

It fits inside the free credits, with 65 to spare.

Over by 0 credits. One Starter pack (1,000 credits, $9) covers that for about 0 months at this size. Purchased credits never expire.

  • The rate card has no charge for page rules, goals, bookings or callbacks. A booking or a callback costs what its new contact costs.
  • A person who is already on your lists, or who joins a second list, is not charged as a new person again.
  • A chat visitor who leaves their details counts as a new person as well as the chat itself.
06 / When it breaks

Six ways the right door goes missing,
and the setting behind each.

The Booking block vanishes for visitors who arrive from an ad.
Cause
A page rule compares the full address, query string included. equals https://acme.co/pricing is not https://acme.co/pricing?utm_source=google, and it is not the same address with a trailing slash or a #anchor either.
Fix
Use contains /pricing, or a wildcard such as https://acme.co/pricing*. In a wildcard only the star is yours: a ? keeps its pattern meaning and will not match a question mark, so use contains for an address that has one.
Nobody on an iPad sees my mobile block, or my desktop one.
Cause
Device has three choices, Mobile, Desktop and All, and a tablet is detected as a tablet. It matches neither of the first two.
Fix
Keep Device on All unless a block really is for phones only or computers only. Tablets see only the blocks set to All.
My “new visitors” block fades out mid-visit, and my “from Facebook” block only shows on the first page.
Cause
A visitor counts as new for five minutes after they first arrive, then as returning. And Traffic Source (Referrer) reads the page they came from, which after the first click is your own site, not Facebook.
Fix
Use New and Traffic Source for the landing page only. To pick out a campaign, send it to its own landing page and give the block a page rule for that address.
On some pages the bubble opens to “No blocks found”.
Cause
The bubble button shows wherever the widget loads, and the panel lists only the blocks whose rules pass. A page that none of your blocks match gets the button and an empty panel.
Fix
Keep one block with no rules, such as an FAQ or a contact link, so every page has something behind the button, and run each page you care about through Try it above.
The chat block never shows, though my team is at work.
Cause
Only show when an agent is online checks whether someone on your team has the Live Chat module open, not your opening hours. It hides the block while nobody does, and brings it back the moment someone opens the conversation list or a chat.
Fix
Keep the module open while you are available, or switch the option off and put a Callback block beside the chat, so a visitor who finds the chat gone can still reach you.
The goal says zero, though people have been booking for weeks.
Cause
A Uses your widget goal counts from the next matching visit after you create it, and only for visitors User Journey is tracking. Earlier bookings are not added, and neither is a visitor who was not recorded, such as one who declined analytics while Wait for cookie consent is on.
Fix
Create the goals before you change the rules, and compare from that date. Latest conversions in the goal’s report lists each one within seconds of it happening, so you can see straight away whether it counts.
Questions

Page rules, before you ask.

Open the block in your Floating Bubble, choose Audience & Rules, switch on Page Rules and set a Condition Type (Include or Exclude), a Matching Rule and a Value. The rule is checked against the full address of the page, query string included. Each block has its own rule, so one bubble can show a different set of blocks on each page.

Contains is the safer choice. Equals compares the whole address, so https://acme.co/pricing does not equal https://acme.co/pricing?utm_source=google and the block disappears for anyone arriving from an ad. Contains /pricing matches both, and so does a wildcard such as https://acme.co/pricing*, where the star stands for any text.

Device has three choices: Mobile, Desktop and All. A tablet is detected as a tablet, which matches neither Mobile nor Desktop, so only blocks set to All appear on one. If tablet visitors need a block, leave its Device on All.

With Only show when an agent is online switched on, the block is hidden while nobody on your team has the Live Chat module open, and it comes back the moment someone opens the conversation list or a chat. It checks whether someone has the module open, not your opening hours, so keep the module open while you are available or switch the option off.

Add one User Journey goal for each door. The goal type Uses your widget offers Books a meeting, Starts a live chat and Asks for a call back, and each goal's report shows where it was reached. Counting starts with the next matching visit, so create the goals before you change the rules.

Page loads with the widget on them are 10 credits per 1,000, a new person who joins a list is 1 credit, once, a new live chat is 1 credit and each tracked visitor journey is 0.1 credits. The rules, bookings and callbacks have no rate of their own. Every account gets 250 free credits a month, packs start at $9 and purchased credits never expire.

Stop losing the visitors
you already paid for.

More leads from the traffic you already have, and follow-up that sends itself. Free to start. No card, no monthly fee.