Skip to main content

Advanced Visibility: Controlling Where Your Widget Appears

Welcome to the advanced visibility guide! If you're here, you've probably mastered the basics of your WhatsApp chat widget and want even more precise control over where it appears on your website.

Who Is This Guide For?​

This guide is for you if:

  • ✅ You've already set up your WhatsApp chat widget successfully
  • ✅ You understand what "paths" are on a website (if not, read our custom messages guide first!)
  • ✅ You want to hide the widget on specific pages (like checkout or internal pages)
  • ✅ You want the widget to appear ONLY on certain pages
  • ✅ You need sophisticated control for complex website structures
Prerequisites Required

This guide assumes you understand:

  • How to access and edit your widget settings
  • What website paths are (like /blog or /contact-us)
  • The difference between exact paths and wildcard paths (like /blog/*)

If any of these sound unfamiliar, please read our "Customizing Welcome Messages for Different Pages" guide first. It teaches these concepts in a gentler, more beginner-friendly way.

What You'll Learn​

In this guide, you'll master:

  1. Understanding the visibility rule system and how it makes decisions
  2. Setting up "Exclude Paths" to hide the widget on specific pages
  3. Setting up "Include Paths" to show the widget only where you want it
  4. Combining rules to create sophisticated visibility logic
  5. Troubleshooting when things don't work as expected

Why Control Widget Visibility?​

At first glance, showing your chat widget everywhere seems like a good idea—more visibility means more conversations, right? But there are many situations where hiding the widget actually improves your visitor's experience and your conversion rates.

Common Reasons to Hide the Widget​

When Less Is More

During Checkout

  • Visitors are focused on completing their purchase
  • Pop-ups and chat widgets can distract them and increase cart abandonment
  • If they have questions, they'll reach out before getting to this step

On Thank You Pages

  • They've already converted—no need to sell anymore
  • Keep the page clean and focused on confirming their action
  • They already have your contact information if they need to follow up

Internal or Administrative Pages

  • Pages meant only for your team shouldn't have customer chat widgets
  • Login pages, admin dashboards, internal tools
  • Staff directories or internal documentation

Specific Landing Pages

  • Some marketing campaigns work better without any distractions
  • A/B testing might require removing the widget from test pages
  • High-converting landing pages might perform better without the widget

Application or Form Pages

  • When someone is filling out a detailed form, don't distract them
  • Let them complete what they're doing
  • They can always find the chat widget on other pages afterward

Common Reasons to Show the Widget ONLY on Specific Pages​

Sometimes you want the opposite approach—hide the widget everywhere EXCEPT certain key pages:

  • Lead generation strategy: Show it only on high-intent pages (pricing, contact, product pages)
  • Minimalist approach: Reduce clutter on most pages but make help available where it matters most
  • Selective support: Offer chat support only to visitors viewing specific products or services
  • Testing: Trial the widget on just a few pages before rolling it out site-wide

Understanding the Visibility Rule System​

Before we start setting up rules, it's crucial to understand how the system makes decisions. This will help you avoid confusion and create the exact visibility behavior you want.

The Three-Step Decision Process​

Every time someone visits a page on your website, the system asks three questions in this exact order:

The Decision Flow

Step 1: What's the Default Behavior?
The system first looks at your base setting:

  • "Show on all pages" OR
  • "Hide on all pages"

This is your starting point. Think of it as the general rule before any exceptions.

Step 2: Are There Any Include Paths (Force Show)?
Next, the system checks if the current page matches any "Include Paths" you've set up:

  • If YES → The widget WILL show (overriding the default if necessary)
  • If NO → Continue to Step 3

Think of Include Paths as VIP passes that guarantee the widget appears, even if the default says hide.

Step 3: Are There Any Exclude Paths (Force Hide)?
Finally, the system checks if the current page matches any "Exclude Paths":

  • If YES → The widget WILL NOT show (this overrides everything)
  • If NO → Use the result from Step 2 (or Step 1 if no Include Paths matched)

Think of Exclude Paths as a "no entry" list that has the final say, blocking the widget no matter what.

The Last Rule Wins!

Why This Order Matters​

The order is intentional and powerful. Here's why:

  1. Default Behavior gives you a safe, predictable starting point
  2. Include Paths let you add exceptions to show the widget
  3. Exclude Paths let you add exceptions to hide the widget, and they always win in conflicts

This three-step system lets you create both simple and complex visibility rules.

Visualizing the Logic​

Let's look at a simple example:

Settings:
- Default: Show on all pages
- Include Paths: (none)
- Exclude Paths: /checkout, /checkout/*

Result:
- Homepage (/) → Shows ✅ (default says show, no exceptions)
- About page (/about) → Shows ✅ (default says show, no exceptions)
- Blog (/blog/post-1) → Shows ✅ (default says show, no exceptions)
- Checkout (/checkout) → Hidden ❌ (excluded path overrides default)
- Checkout step 2 (/checkout/payment) → Hidden ❌ (excluded path /checkout/* matches)

See how it works? The default rule applies everywhere EXCEPT where you've created specific exceptions.

Start Simple

When you're first setting up visibility rules, start with the simplest approach possible:

  • Choose your default (show or hide)
  • Add just 1-2 exception paths
  • Test thoroughly
  • Add more complexity only if needed

It's easier to add more rules later than to untangle overly complicated rules that aren't working right.

Step 1: Access Visibility Rules​

Let's open the right section to start controlling your widget's visibility.

  1. Navigate to Admin View

  2. Click on "Website Chat Widget" in the left menu

  3. Find your WhatsApp widget and click "Edit Widget"

  4. Click on the "Visibility Rules" tab at the top

You should now see the Widget Visibility section with several parts:

  • Default Behaviour (with two radio button options)
  • Exception Rules (with Include Paths and Exclude Paths subsections)

Step 2: Choosing Your Default Behavior​

This is your foundation—the base rule before any exceptions.

Your Two Options​

⚪ Show on all pages

  • The widget appears on every page of your website
  • Then you use Exclude Paths to hide it from specific pages
  • Best for: Most businesses who want to be available everywhere except a few specific pages

⚪ Hide on all pages

  • The widget is hidden on every page of your website
  • Then you use Include Paths to show it only on specific pages
  • Best for: Businesses who want the widget only on high-intent pages or those testing the widget gradually
Which Should You Choose?

Choose "Show on all pages" if:

  • You want maximum visibility and availability
  • You only need to hide the widget from a few specific pages (checkout, thank you pages, etc.)
  • You're okay with the widget appearing on new pages you create in the future

Choose "Hide on all pages" if:

  • You want to carefully control where people can contact you
  • You only want the widget on 3-5 key pages
  • You want to test the widget on a small section of your site first
  • You're worried about the widget being distracting on most pages

Most Common Choice: "Show on all pages" with a few Exclude Paths. This ensures you're capturing leads everywhere while hiding the widget only where it would genuinely hurt the user experience.

Make Your Selection​

  1. Click the radio button next to your chosen default behavior

  2. The change is applied immediately in your admin panel (but remember, nothing goes live until you click "Save Widget" at the end!)

Now let's set up your exception rules based on which default you chose.

Step 3: Using Exclude Paths (Force Hide)​

Exclude Paths are perfect when you want the widget visible almost everywhere, but need to hide it from specific pages.

When to Use Exclude Paths​

Perfect scenarios:

  • Default is set to "Show on all pages"
  • You want to hide the widget from checkout, payment, or confirmation pages
  • You want to hide it from internal pages, admin areas, or login pages
  • You want to hide it from specific landing pages or A/B test variants
  • You want to hide it from your blog section

Understanding the Exclude Paths Interface​

Look for the "Exclude Paths" section. You'll see:

  • A text input field with placeholder text like "e.g. /blog, /admin/*"
  • A red "+" button to add paths
  • Any paths you've already added will appear as tags with a light red background labeled "Force Hide"

The red color is intentional—it's a warning color reminding you these paths will BLOCK the widget.

Adding Your First Exclude Path​

Let's hide the widget from your checkout page:

  1. In the "Exclude Paths" text field, type:

    /checkout
    Remember Path Rules
    • Always start with / (forward slash)
    • Use exact path for one specific page: /checkout
    • Use wildcard for multiple pages: /checkout/*
    • Paths are case-sensitive: /Checkout ≠ /checkout

  2. Click the red "+" button

  3. Your path appears as a red tag labeled "Force Hide"

That's it! The widget will no longer appear on www.yourwebsite.com/checkout.

Adding Multiple Exclude Paths​

Want to hide the widget from your entire checkout process? Let's add a wildcard path:

  1. Type in the text field:

    /checkout/*

    This will hide the widget from any page that starts with /checkout/, like:

    • /checkout/cart
    • /checkout/payment
    • /checkout/confirmation
    • And any other /checkout/ subpages

  2. Click the red "+" button

  3. Another red tag appears

Now you have two Exclude Paths! The widget is hidden from /checkout AND all pages within the checkout section.

Common Exclude Path Examples​

Here are paths that businesses commonly exclude:

Path to ExcludeWhat It DoesWhy You'd Do This
/checkoutHides on checkout page onlyDon't distract during payment
/checkout/*Hides on entire checkout flowKeep the entire process distraction-free
/thank-youHides on confirmation pageThey already converted
/adminHides on admin loginInternal page, not for customers
/admin/*Hides on entire admin sectionHide from all internal pages
/blog/*Hides on all blog postsMaybe you prefer email opt-ins on blog

Removing an Exclude Path​

Changed your mind? Easy to remove!

  1. Find the red tag for the path you want to remove

  2. Click the small "x" button on the right side of the tag

  3. The path is removed immediately

The widget will now show on that path again (assuming your default is "Show on all pages").

Step 4: Using Include Paths (Force Show)​

Include Paths work the opposite way—they force the widget to appear on specific pages, even if your default is "Hide on all pages."

When to Use Include Paths​

Perfect scenarios:

  • Default is set to "Hide on all pages"
  • You only want the widget on your homepage, contact page, and pricing page
  • You want to test the widget on just a few high-intent pages first
  • You want to run an experiment showing the widget only to specific visitor segments

Understanding the Include Paths Interface​

Look for the "Include Paths" section. You'll see:

  • A text input field with placeholder text like "e.g. /contact, /support/*"
  • A green "+" button to add paths
  • Any paths you've already added will appear as tags with a light green background labeled "Force Show"

The green color signals permission—these paths get special access to show the widget.

Adding Your First Include Path​

Let's show the widget ONLY on your homepage and contact page:

  1. First, make sure your Default Behavior is set to "Hide on all pages"

    This is crucial! If your default is "Show on all pages," Include Paths don't really do anything (the widget already shows everywhere).

  2. In the "Include Paths" text field, type:

    /
    The Root Path

    A single forward slash / represents your homepage—the page people see at www.yourwebsite.com with nothing after it.

    This is one of the most common Include Paths!

  3. Click the green "+" button

  4. A green tag appears labeled "Force Show"

Now the widget will appear ONLY on your homepage (and nowhere else, since the default is "Hide on all pages").

Adding More Include Paths​

Let's also show the widget on your contact page:

  1. Type in the text field:

    /contact-us

  2. Click the green "+" button

  3. Another green tag appears

Perfect! Now the widget shows on your homepage AND your contact page, but remains hidden everywhere else.

Using Wildcard Include Paths​

Want to show the widget on all your product pages but nowhere else?

  1. Make sure default is "Hide on all pages"

  2. Type:

    /products/*

  3. Click the green "+" button

Now the widget appears on /products/shoes, /products/clothing, and any other product page, but stays hidden on your blog, about page, and everywhere else.

Common Include Path Examples​

Here are paths that businesses commonly include:

Path to IncludeWhat It DoesWhy You'd Do This
/Shows only on homepageMain landing page where you want engagement
/contactShows only on contact pageHelp people who are ready to reach out
/contact-usShows only on contact pageAlternative spelling of contact page
/pricingShows only on pricing pageCapture leads considering purchase
/products/*Shows on all product pagesHelp shoppers with questions
/services/*Shows on all service pagesEngage potential clients

Removing an Include Path​

  1. Find the green tag for the path you want to remove

  2. Click the small "x" button on the tag

  3. The path is removed

The widget will now be hidden on that path again (since your default is "Hide on all pages").

Step 5: Combining Rules for Advanced Control​

Now that you understand both Include and Exclude paths, let's look at how you can combine them for sophisticated visibility control.

Remember the Priority Order​

The Rule Hierarchy
  1. Default Behavior (first decision)
  2. Include Paths (second decision - can override default)
  3. Exclude Paths (final decision - always wins)

Exclude Paths beat everything!

This means if a page matches BOTH an Include Path and an Exclude Path, the Exclude Path wins and the widget stays hidden.

Example Scenario 1: Show Everywhere Except Checkout​

This is the most common setup.

Configuration:

  • Default Behavior: ✅ Show on all pages
  • Include Paths: (leave empty)
  • Exclude Paths: /checkout, /checkout/*

Results:

PageWidget Shows?Why?
/ (homepage)✅ YesDefault says show, no exceptions
/about✅ YesDefault says show, no exceptions
/blog/post-1✅ YesDefault says show, no exceptions
/products/shoes✅ YesDefault says show, no exceptions
/contact-us✅ YesDefault says show, no exceptions
/checkout❌ NoExcluded path overrides default
/checkout/payment❌ NoExcluded path /checkout/* matches
/checkout/confirmation❌ NoExcluded path /checkout/* matches
Perfect For

This setup is ideal for 90% of businesses. You're available everywhere to help visitors, but you don't distract them during the critical checkout process.

Example Scenario 2: Show Only on Key Pages​

Configuration:

  • Default Behavior: ✅ Hide on all pages
  • Include Paths: /, /pricing, /contact-us
  • Exclude Paths: (leave empty)

Results:

PageWidget Shows?Why?
/ (homepage)✅ YesIncluded path overrides default
/pricing✅ YesIncluded path overrides default
/contact-us✅ YesIncluded path overrides default
/about❌ NoDefault says hide, not included
/blog/post-1❌ NoDefault says hide, not included
/products/shoes❌ NoDefault says hide, not included
/checkout❌ NoDefault says hide, not included
Perfect For

This setup works great when you want to carefully control visitor interactions. You're showing the widget only on pages where people are most likely to convert or need help.

Example Scenario 3: Show on Services, Hide on One Specific Service​

This is where combining rules gets powerful.

Configuration:

  • Default Behavior: ✅ Hide on all pages
  • Include Paths: /services/*
  • Exclude Paths: /services/free-consultation

Results:

PageWidget Shows?Why?
/services/web-design✅ YesIncluded path /services/* matches
/services/seo✅ YesIncluded path /services/* matches
/services/marketing✅ YesIncluded path /services/* matches
/services/free-consultation❌ NoExcluded path beats included path!
/about❌ NoDefault says hide, not included
/❌ NoDefault says hide, not included

Why This Is Useful: Maybe you want the chat widget on all your paid service pages to convert interested visitors, BUT your free consultation page has its own form and you don't want to confuse visitors with multiple calls-to-action.

Example Scenario 4: Show on Contact Section Except Thank You Page​

Configuration:

  • Default Behavior: ✅ Hide on all pages
  • Include Paths: /contact, /contact/*
  • Exclude Paths: /contact/thank-you

Results:

PageWidget Shows?Why?
/contact✅ YesIncluded path matches
/contact/sales✅ YesIncluded path /contact/* matches
/contact/support✅ YesIncluded path /contact/* matches
/contact/thank-you❌ NoExcluded path has final say!
/❌ NoDefault says hide, not included

Why This Is Useful: You want the widget available while people are navigating your contact section and deciding who to reach out to, but once they submit the form and land on the thank-you page, they're done—no need for the widget anymore.

Watch for Conflicts

When you have both Include and Exclude paths, be very careful about overlaps:

  • If you include /blog/* but exclude /blog/special-post, the widget will be hidden on that special post (Exclude wins)
  • If you include /products but exclude /products, the widget will be hidden (Exclude wins)

Always remember: Exclude Paths have the final word. Use the preview feature (if available for visibility) or test on your live site to verify behavior.

Step 6: Testing Your Visibility Rules​

This is THE most important step. Visibility rules can get complex, and the only way to be 100% sure they're working correctly is to test them on your actual website.

Why Testing Is Critical​

Test Before You Assume!

Even if your rules look perfect in the admin panel, paths might not match exactly, or you might have overlooked something. The difference between /blog and /blog/ or a capital letter can completely change your results.

Always test your live website!

How to Test Properly​

1. Write Down Your Expected Behavior

Before testing, document what SHOULD happen on your most important pages:

Expected Behavior:
- Homepage (/) → Should show widget ✅
- About (/about) → Should show widget ✅
- Checkout (/checkout) → Should NOT show widget ❌
- Checkout Payment (/checkout/payment) → Should NOT show widget ❌
- Blog post (/blog/summer-tips) → Should show widget ✅

2. Open an Incognito/Private Browser Window

  • Chrome: Ctrl+Shift+N (Windows) or Cmd+Shift+N (Mac)
  • Firefox: Ctrl+Shift+P (Windows) or Cmd+Shift+P (Mac)
  • Safari: File > New Private Window
  • Edge: Ctrl+Shift+N

3. Visit Each Page in Your Test Plan

Go to each page and check if the widget appears or not. Compare against your expected behavior list.

4. Check the Exact Path in Your Browser

Sometimes paths aren't what you expect:

  • You might think your blog is at /blog but it's actually at /posts
  • Your contact page might be /contact but it's actually /contact-us
  • There might be trailing slashes you didn't account for (/about vs /about/)

Copy the exact path from your browser's address bar and verify it matches your rules.

5. Test Wildcards Thoroughly

If you used wildcard paths like /products/*, make sure to test:

  • The exact parent page: /products
  • Multiple subpages: /products/shoes, /products/clothing, /products/accessories
  • Deeply nested pages: /products/shoes/sneakers (does your wildcard still match?)

Common Testing Discoveries​

You might find:

  1. Paths don't match

    • You excluded /Blog but the actual path is /blog (case matters!)
    • You included /contact but the page is actually /contact-us

  2. Wildcards don't work as expected

    • You used /blog* instead of /blog/* (missing the slash!)
    • Your wildcard is too broad or too narrow

  3. Conflicts between Include and Exclude

    • You included /services/* and excluded /services/consultation
    • The Exclude is winning (as designed) but you forgot you set it up

  4. Rules apply to unexpected pages

    • Your /products/* wildcard is hiding the widget on /products-archive (wildcards match the pattern anywhere!)

What to Do If Something's Wrong​

  1. Go back to Admin View → Edit Widget → Visibility Rules

  2. Double-check your paths:

    • Are they spelled correctly?
    • Do they match the EXACT paths in your browser?
    • Did you include the leading /?
    • For wildcards, did you include /* at the end?

  3. Review your logic:

    • Is your Default Behavior what you intended?
    • Are your Include and Exclude paths conflicting?
    • Are you using the right type of path (exact vs wildcard)?

  4. Make corrections and save again

  5. Test again in incognito mode

Test on Mobile Too

If possible, test on a mobile device as well. Sometimes website structures differ between desktop and mobile versions, and you want to make sure your visibility rules work correctly on both!

Troubleshooting Common Issues​

"The widget isn't hiding on pages I excluded"​

Possible causes:

  1. Path mismatch

    • Your actual path is /Checkout but you excluded /checkout
    • Your actual path has a trailing slash /blog/ but you excluded /blog
    • Solution: Copy the exact path from your browser's address bar and use that

  2. Wildcard not working correctly

    • You used /checkout* instead of /checkout/*
    • Solution: Make sure there's a / before the *

  3. Changes didn't save

    • You added the Exclude Path but didn't click "Save Widget" at the bottom
    • Solution: Always save after making changes!

  4. Browser cache

    • Your browser is showing an old version of the widget
    • Solution: Hard refresh (Ctrl+Shift+R or Cmd+Shift+R) or test in incognito

"The widget isn't showing on pages I included"​

Possible causes:

  1. Default Behavior is wrong

    • You set up Include Paths but your default is "Show on all pages"
    • Include Paths only matter when the default is "Hide on all pages"
    • Solution: Change default to "Hide on all pages"

  2. Conflicting Exclude Path

    • You included /services/* but also excluded /services/web-design
    • Remember: Exclude always wins!
    • Solution: Remove the conflicting Exclude Path

  3. Path doesn't match

    • You included /contact but the page is actually /contact-us
    • Solution: Check the exact path and update your Include Path

"The widget shows/hides inconsistently"​

Possible causes:

  1. Complex rule interactions

    • You have many Include and Exclude paths that overlap in confusing ways
    • Solution: Simplify! Remove paths until you find the conflict, then rebuild carefully

  2. Dynamic URLs

    • Your site adds query parameters like ?ref=facebook to URLs
    • The widget should ignore these, but verify
    • Solution: Test the same page with and without query parameters

  3. Multiple versions of the same page

    • Your site has www.yoursite.com/about and yoursite.com/about
    • These might be treated differently
    • Solution: Ensure your site redirects to one canonical version

"I'm completely confused—help!"​

Starting Over

If your visibility rules have become too complex and confusing:

  1. Remove ALL your Include and Exclude paths (click the "x" on every tag)
  2. Set a simple default (usually "Show on all pages")
  3. Test - widget should now show everywhere
  4. Add just ONE rule (maybe Exclude your checkout page)
  5. Test again
  6. Add rules one at a time, testing after each addition

This step-by-step approach helps you identify exactly which rule is causing problems.

Advanced Use Cases and Examples​

Let's look at some sophisticated real-world scenarios and how to implement them.

Use Case 1: E-Commerce Store with Checkout Protection​

Business: Online store that wants maximum engagement without disrupting sales

Goals:

  • Show widget on product pages to answer questions
  • Show widget during browsing to capture leads
  • Hide widget during checkout to prevent cart abandonment
  • Hide widget on thank-you pages

Configuration:

Default Behavior: Show on all pages

Include Paths: (none needed)

Exclude Paths:
- /cart/checkout
- /cart/checkout/*
- /order/confirmation
- /thank-you

Why This Works: The default ensures the widget is available everywhere to help shoppers. Exclude paths protect the critical conversion funnel from distractions.

Use Case 2: SaaS Company with Targeted Lead Capture​

Business: Software company that wants leads only from high-intent pages

Goals:

  • Show widget only on pages where visitors are considering purchase
  • Hide widget from blog and educational content
  • Capture leads at decision-making points

Configuration:

Default Behavior: Hide on all pages

Include Paths:
- /
- /pricing
- /pricing/*
- /demo
- /contact
- /features/enterprise

Exclude Paths: (none needed)

Why This Works: By defaulting to hide and only including key pages, the company focuses conversations on qualified leads who are further in the buying journey.

Use Case 3: Multi-Location Business​

Business: Restaurant chain with location-specific pages

Goals:

  • Show widget on general company pages
  • Show widget on location pages to help with reservations
  • Hide widget on the blog and news section
  • Hide widget on online ordering checkout

Configuration:

Default Behavior: Show on all pages

Include Paths: (none needed)

Exclude Paths:
- /blog
- /blog/*
- /news
- /news/*
- /order/checkout
- /order/checkout/*

Why This Works: The business maximizes availability for customer service while avoiding distractions in content areas and during transactions.

Use Case 4: Agency with Selective Service Pages​

Business: Marketing agency that wants to promote certain services over others

Goals:

  • Show widget only on premium service pages
  • Hide widget from basic/entry-level service pages (push them to fill out forms instead)
  • Show widget on case studies related to premium services

Configuration:

Default Behavior: Hide on all pages

Include Paths:
- /services/enterprise-seo
- /services/content-strategy
- /services/conversion-optimization
- /case-studies/enterprise/*

Exclude Paths:
- /services/basic-seo
- /services/social-media-starter

Why This Works: The agency can prioritize conversations with high-value prospects while directing smaller leads through automated form funnels.

Best Practices for Visibility Rules​

Start Simple, Iterate Based on Data​

The 80/20 Rule

80% of businesses only need simple visibility rules:

  • Default: Show on all pages
  • Exclude: 2-3 checkout or internal pages

Don't overcomplicate unless you have specific data showing you need more control!

Recommended Approach:

  1. Week 1: Use only default behavior (show or hide everywhere)
  2. Week 2: Add 1-2 basic rules based on obvious needs
  3. Week 3+: Monitor where conversations are happening and refine

Document Your Rules​

As your rules get more complex, keep a simple document explaining your setup:

Widget Visibility Rules - Updated: Nov 2025

Goal: Maximize engagement while protecting checkout flow

Default: Show on all pages

Excluded:
- /checkout - Don't distract during payment
- /checkout/* - Hide on entire checkout flow
- /order-confirmation - They already ordered
- /admin/* - Internal pages

Notes:
- Tested on mobile and desktop
- Checkout abandonment dropped 5% after hiding widget
- Will consider excluding blog in future if engagement is low

Monitor Performance​

Pay attention to how your visibility rules affect your business:

Metrics to Watch:

  • Where are most WhatsApp conversations starting from?
  • Did checkout conversion rates improve after excluding widget?
  • Are you missing opportunities on pages where the widget is hidden?
  • Are visitors asking the same questions repeatedly (might need custom messages OR visibility changes)

Adjust Based on Data:

  • If no one contacts you from blog pages → Consider excluding them to reduce load
  • If lots of people ask questions on a specific page → Make sure the widget shows there!
  • If checkout conversion drops → Check if you accidentally hid the widget somewhere earlier in the funnel

Test Major Changes​

Whenever you make significant visibility rule changes:

  1. ✅ Test immediately on your live site
  2. ✅ Test on multiple devices (desktop, mobile, tablet)
  3. ✅ Monitor for 2-3 days to see impact
  4. ✅ Be ready to roll back if something breaks

Keep Mobile in Mind​

Remember that mobile visitors have less screen space. Consider:

  • Is the widget too intrusive on mobile for certain pages?
  • Do mobile users navigate your site differently?
  • Are there mobile-specific pages where the widget should behave differently?

Unfortunately, this system doesn't allow device-specific rules, but you can use path-based rules if your mobile site uses different URLs.

Frequently Asked Questions​

"Can I set different visibility rules for mobile vs desktop?"​

Not directly through this interface. The visibility rules apply to all devices. However, if your website uses different URL structures for mobile (like m.yoursite.com or /mobile/ paths), you could potentially use path-based rules.

For most modern responsive websites, this isn't possible with the current system.

"Will my visibility rules affect my custom welcome messages?"​

No! These are two independent systems:

  • Visibility rules determine IF the widget appears
  • Custom welcome messages determine WHAT message shows if the widget appears

If visibility rules hide the widget on a page, it doesn't matter what custom message you set up—the widget won't appear at all.

"Can I schedule visibility rules to change at certain times?"​

No, the current system doesn't support time-based rules. Your visibility settings are always active. If you need time-based changes, you would have to manually update the rules when needed (like hiding the widget during a sale event, then showing it again afterward).

"What happens if I have conflicting rules?"​

Remember the priority:

  1. Default Behavior
  2. Include Paths (can override default)
  3. Exclude Paths (always win)

If a page matches both an Include and Exclude path, it will be hidden. The Exclude Path always has the final say.

"Do visibility rules slow down my website?"​

Not noticeably. The widget script checks visibility rules when it loads, but this is a very fast operation that happens in milliseconds. The impact on your website's performance is negligible.

"Can I export or backup my visibility rules?"​

Not directly, but you can:

  1. Take screenshots of your Include and Exclude paths
  2. Copy them into a document for your records
  3. Keep notes about why you set up each rule

This is helpful if you ever need to recreate your setup or want to remember your reasoning later.

"What if I want to hide the widget on my entire blog but show it on one specific blog post?"​

This requires careful setup:

Default Behavior: Show on all pages

Include Paths:
- /blog/special-post (the one post where you want it to show)

Exclude Paths:
- /blog
- /blog/* (hides on all blog posts)

Why this works: The /blog/* wildcard hides the widget on all blog posts. But because Include paths are evaluated before Exclude paths, you can...

Actually, wait! This won't work because Exclude paths always win.

The correct approach: You can't easily do this with the current system. Your best option is to not exclude /blog/* and instead exclude individual blog posts you DON'T want the widget on. This is more work but achieves the goal.

Saving and Publishing Your Visibility Rules​

Just like with custom messages, your visibility rules aren't live until you save them!

Final Pre-Publishing Checklist​

Before clicking that save button:

  1. ✅ Review your Default Behavior - Is it set correctly?
  2. ✅ Review all Include Paths - Are they spelled correctly? Do they make sense?
  3. ✅ Review all Exclude Paths - Are they spelled correctly? Any conflicts with Include Paths?
  4. ✅ Check for typos - Especially in paths (case-sensitive!)
  5. ✅ Think through key pages - Mentally walk through your most important pages and verify the widget will behave as expected
Last Chance to Check

Once you save, these rules go live immediately. While you can always change them back, visitors might have a weird experience in the meantime. Triple-check before saving!

Publish Your Changes​

  1. Scroll to the bottom of the Edit Widget screen

  2. Click "Save Widget" or "Next"

  3. Your changes are now live!

Immediate Testing (Required!)​

Do not skip this step!

  1. Open an incognito browser window

  2. Visit at least 5 key pages:

    • Homepage
    • A page where the widget should show
    • A page where the widget should be hidden
    • A page with a wildcard Include path
    • A page with a wildcard Exclude path

  3. Verify the widget appears (or doesn't appear) correctly on each page

  4. If something's wrong:

    • Go back to admin
    • Fix the rules
    • Save again
    • Test again
Quick Rollback

If your new rules are causing major issues and you need to revert immediately:

  1. Go back to admin
  2. Remove ALL your Include and Exclude paths
  3. Set Default Behavior to "Show on all pages"
  4. Save

This instantly returns you to the basic setup while you figure out what went wrong.

What's Next?​

Congratulations! You now have complete control over where your WhatsApp chat widget appears on your website. You understand the three-step decision process, how to use Include and Exclude paths, and how to test everything thoroughly.

Combining with Custom Messages​

Don't forget—you can use both custom welcome messages AND visibility rules together!

For example:

  • Show the widget on all product pages (/products/*)
  • Set custom welcome messages for different product categories
  • Hide the widget only during checkout

This combination gives you incredible control over both WHERE the widget appears and WHAT message visitors see when they click it.

Need Help?​

If you're stuck or confused:

  1. Re-read the relevant sections - Sometimes a second read clarifies things
  2. Simplify your rules - Remove complexity until you find what's causing problems
  3. Test one rule at a time - Add rules individually and test after each addition
  4. Check the troubleshooting section - Most common issues have solutions there
  5. Contact support - We're here to help with complex scenarios!

Final Thoughts​

Visibility rules give you powerful control, but with great power comes... well, you know. Use them thoughtfully:

  • Don't hide the widget everywhere - You'll miss valuable conversations
  • Don't overcomplicate - Simple rules are easier to maintain and debug
  • Do test thoroughly - Always verify on your live site
  • Do monitor results - Let data guide your decisions
  • Do iterate - Your first setup probably won't be perfect, and that's okay!

The goal is to maximize helpful conversations with visitors while avoiding distractions at critical moments. Keep that balance in mind as you refine your visibility strategy.

Happy optimizing! 🎯✨