Chatbot Builder Targeting: Decide Which Visitors See Which Bot, Then Test Your Conditions on Sample Visitors (Free Condition Tester)
Chatbot builder guides spend pages on messages and buttons, then skip the step that decides whether anyone sees them: targeting. Every flow you build needs rules about who gets it, on which page, from which source and on which visit. Get those rules wrong and the right message reaches the wrong person, two messages pop up at once, or a whole group of visitors hears nothing. This guide shows how to plan conditions on paper, write sample visitors, and test them with a free tool before you switch anything on.
β‘ In short
- Targeting decides who sees each flow. It matters as much as the message itself.
- Write your visitor types first, as short sample profiles: page, source, device, language, visits, contact details.
- Give each flow one goal and only the conditions it needs. Fewer, sharper conditions beat long lists.
- Test every flow against every sample visitor. Look for overlaps, gaps and flows that match nobody.

Why targeting
The same message for everyone is the most common mistake
Picture a small furniture shop’s website (an illustrative example). The owner builds one friendly proactive message: “Hi! Looking for something? We deliver across India.” It pops up for everyone, on every page, five seconds after they arrive.
On the home page it’s fine. On the cart page it’s a distraction from paying. For a returning customer who already ordered twice it feels robotic. For a visitor from Dubai it’s wrong, because the shop doesn’t deliver there. For a visitor whose browser is in Hindi it’s a missed chance to greet them in their language.
None of these problems are about the wording. They’re about who sees it. That’s what conditions in a bot builder are for: you describe a type of visitor, and only that visitor gets that flow.
Targeting also protects you from your own enthusiasm. Once you’ve built three or four flows, it’s easy for them to overlap. A visitor on the offers page using a Hindi browser on their phone might match three flows at once. Depending on the tool, they get one of them, or several messages in a row. Either way, you didn’t decide; the overlap did.
The fix is not a cleverer message. It’s a short plan: list the kinds of visitors you get, decide what each one should see, and test that plan before it goes live. You can do it in half an hour with a notebook and the tester further down this page.
The building blocks
What a chatbot builder’s targeting conditions can check
Most tools look at a similar handful of visitor details. These are the ones LiveChatBot Flows use, and what each one is good for.
Page
The page address the visitor is on. Use it to match intent: offers, cart, a product range, contact.
Traffic source
Where they came from: Google, Instagram, Facebook, an ad, or direct. Useful when a campaign promises something specific.
Country
Where the visitor is. Handy for delivery areas, currency questions and time zones.
Device
Phone or computer. Phone visitors need shorter messages and fewer buttons.
Browser language
The language their browser is set to. Lets you greet Hindi or Tamil browsers differently.
Number of visits
First visit or returning. Returning visitors often need a nudge, not an introduction.
Lead score and contact details
Whether they look like a warm lead, and whether you already have their email or phone. No point asking twice.
Step 1
Write your visitor types before you open the builder
Start with people, not settings. On a sheet of paper, write five to eight short descriptions of visitors who actually come to your site. Use your analytics, your visitor list or simply what you notice in chats. Each description should fit on one line and cover the details your tool can see.
For the illustrative furniture shop, the list might look like this:
- A first-time visitor from Google, on the home page, on a computer, browser in English.
- A returning visitor on the offers page, on a phone, browser in Hindi, third visit.
- An Instagram shopper on a product page, on a phone, first visit.
- A known customer, email already saved, on the cart page, sixth visit.
- A visitor from the UAE on a sofa page, from Google.
Write the awkward ones too: the visitor from a country you don’t serve, the one who has already given you their phone number, the one who keeps coming back without buying. Those are the visitors that badly targeted flows annoy most.
Next to each, write in plain words what you’d want them to see. “Nothing, let them browse.” “A reminder that the sale ends Sunday.” “A short note in Hindi.” “Help finishing the order.” “A polite line that we deliver only in India.”
This list is your test set. Later, every flow you build has to pass it. If a visitor type has no line next to it, that’s fine; seeing nothing is a valid answer. What’s not fine is not knowing.
If you track visitors in LiveChatBot, the visitor tracking view shows pages, sources and visit counts for people on your site right now, which makes writing these profiles quick.
Step 2
One goal per flow, and only the conditions it needs
Now turn the right-hand column of your list into flows. Each flow should have one goal you can say in a sentence: “Help phone shoppers from Instagram with delivery questions on product pages.” The conditions follow from the sentence: source is Instagram, device is mobile, page contains /product.
Three habits keep conditions clean.
Start with the page
The page is usually the strongest signal of what a visitor wants. Someone on the cart page wants to finish buying; someone on the returns page has a problem. Most flows should have a page condition, and many need nothing else. Our guide to showing chat on specific pages explains page matching in more detail.
Add a condition only if it changes the message
If the message would be the same for phone and computer visitors, don’t add a device condition. Every extra condition shrinks the audience, and a flow with six conditions may match almost no one. LiveChatBot allows up to six per Flow; most good flows use two or three.
Never ask one field for two values
“Country is AE” plus “country is SA” in the same flow means a visitor must be in both countries at once, so the flow never fires. The same goes for “visits at least 5” with “visits at most 3”. If you want two countries, build two flows. The tester below catches these.
When the flow’s goal is clear, write the message itself. Our chat flow guide walks through templates, delays and the follow-up message.
Free tool
Test your chatbot builder conditions on sample visitors
Type your flows and their conditions, then your sample visitors. The tester shows which flows each visitor would get, flags overlaps and gaps, and catches conditions that can never match.
1. Your flows, one per line: Flow name | condition ; condition. Fields: page, source, country, device, language, visits, contact. Words: contains, is, not, or >= <= = for visits.
2. Sample visitors, one per line: Label: page=/x source=google country=IN device=mobile language=en visits=1 contact=no
Runs only in your browser; nothing is sent or saved. The tester treats every condition in a flow as must-match. It is a planning aid, not a copy of any product’s engine.
Reading the results
Overlaps, gaps and flows that match nobody
Load the example and run it. The illustrative shop has six flows and five visitors, and the report shows the three problems you’ll meet most often.
Overlaps
The returning Hindi visitor on the offers page matches both “Offer nudge” and “Hindi welcome”. That might be fine, or it might mean two messages in a row. Decide which should win. Often the answer is to merge them: a Hindi version of the offer nudge, plus a Hindi welcome that excludes the offers page with a “page not /offers” condition.
Gaps
The known customer at the cart matches nothing. “Cart help” excludes visitors whose contact details you have, and “Loyal customers” is broken. If you want returning customers helped at checkout, you’ve found a hole. If you’re happy to leave them alone, write that down so nobody “fixes” it later.
Notice that “Cart help” also matches nobody in this test set: the only cart visitor is a known customer. Add a first-time cart visitor to your samples, or the tester can’t tell you whether that flow works.
The Dubai visitor also matches nothing, because “Gulf delivery” asks for two countries at once.
Flows that match nobody
“Loyal customers” and “Gulf delivery” both match zero visitors and get a warning explaining why. A flow that matches nobody in your test set will likely match nobody on your site. Either it’s broken, or you forgot to write the visitor it’s for.
Fix the plan, run the tester again, and repeat until every visitor gets either exactly one flow or a deliberate “nothing”. That’s the moment to build the flows for real.
The tester is a planning aid. It treats every condition as must-match and doesn’t know how a particular product picks between overlapping flows, so check your tool’s own help for that. The logic of overlaps, gaps and impossible rules is the same everywhere.
Worked example
The shop’s plan after one round of fixes
| Flow | Conditions | Message (illustrative) |
|---|---|---|
| Offer nudge | page contains /offers Β· visits β₯ 2 Β· language not hi | βThe sale ends Sunday. Want help choosing?β |
| Offer nudge (Hindi) | page contains /offers Β· visits β₯ 2 Β· language is hi | The same offer line, written in Hindi |
| Cart help | page contains /cart | βAny question before you pay? We’re here.β |
| Instagram product help | source is instagram Β· device is mobile Β· page contains /product | βSeen it on Instagram? Ask us about size or delivery.β |
| Delivery area (UAE) | country is AE | βWe currently deliver only within India.β |
| Delivery area (Saudi) | country is SA | Same message as the UAE flow |
Timing and follow-ups
When the flow fires matters as much as who gets it
Conditions decide who. Timing decides when. A well-targeted message that appears in the first second still feels pushy, and one that appears after two minutes may reach nobody, because most visitors have already left.
A practical starting point for small sites: a short delay on browsing pages, so the visitor has time to look around, and a slightly longer one on product pages, where people are reading details. On cart and checkout pages, be careful. A message there should offer help, not interrupt, so keep it quiet and short. These are starting points to test, not rules.
LiveChatBot Flows can send a follow-up message if the visitor doesn’t reply within a set time. Use it only when the second line adds something new, like a delivery date or a link to the size guide. “Hello?” is not a follow-up.
The chat rescuer is different: it sends a short automatic check-in after a period of silence in an ongoing chat, such as “Still there? Happy to help with anything else.” It keeps conversations from dying quietly when the visitor gets distracted.
When you test, include timing in your sample visitors’ story. “Returning visitor on offers page, stays 40 seconds, scrolls, doesn’t reply.” Ask yourself what they’d see, in what order, and whether it feels like a helpful shop assistant or a salesperson following them around. Our guide to proactive chat has more on timing and tone, and the advanced bot techniques post covers the follow-up and rescuer together.
Checklist
Before you switch your flows on
After launch
Re-test whenever something changes
Targeting plans age. You add a new page, start an Instagram campaign, open delivery to a new country, or translate the site. Each change can create an overlap or a gap that wasn’t there before.
Make a habit of re-running your test set whenever you add or edit a flow. Keep your flow lines and sample visitors in a text file, so it takes a minute: paste both into the tester, run it, and read the summary line. If it still says every visitor gets exactly one flow or a deliberate nothing, you’re done.
Once a month, look at real chats that started from a flow. Did people reply? Did any complain about pop-ups? Did a group of visitors never get a message you expected them to get? Add any new visitor type you spot to your sample list. Over time, the list becomes a realistic picture of your audience, and your flows get sharper without getting more complicated.
If you’re still choosing a tool, test targeting during your trial. A good chatbot builder should let you combine page, source, device and visit conditions, and show you clearly which flow a visitor will get. Our chatbot maker red flags post and the no-code booking walkthrough cover what else to check before you commit.
LiveChatBot’s free plan includes Flows with templates, up to six conditions, the follow-up message and the chat rescuer, along with the team inbox, the Android app, visitor tracking and the AI Agent, for two websites with 100 visitors per website each month. See pricing and start at livechatbot.in.
Frequently asked questions
What should I set up first in a chatbot builder: messages or targeting?
Plan targeting first, at least on paper. Knowing exactly who will see a flow makes the message easier to write and shorter.
How many conditions should one flow have?
Usually two or three. LiveChatBot allows up to six per Flow, but every extra condition shrinks the audience. Add one only if it changes the message.
What happens if a visitor matches two flows?
It depends on the tool. Rather than rely on that, use the tester to find overlaps and narrow one flow so each visitor gets the one you intended.
Can I target visitors by language?
Yes. LiveChatBot Flows can use the browser language as a condition, so you can greet Hindi or Tamil browsers in their language.
Does the condition tester send my data anywhere?
No. It runs entirely in your browser and nothing is sent or saved. Use made-up sample visitors rather than real people’s details.
Keep reading
Related guides
Chatbot Bot Backup Plan: Who Answers in Your Chat Window When the AI Is Off, Used Up or Stumped (Free Fallback Map)
Chatbot Characteristics You Can Test in 10 Minutes: Ten Messages That Show What Any Bot Is Really Like (Free Test Script Builder)
Chatbot Best Practices That Fit Your Team: What a Solo Owner, a Small Team and a Busy Shop Should Do First
Show the right message to the right visitor
Build Flows with page, source, country, device, language and visit conditions, then test them before going live. Start free on livechatbot.in.