Configuring Widget Behavior and Page Targeting Rules
Last updated: September 29, 2026
Not every page needs the same agent. Widget Behaviour lets you decide, for each approved domain, which pages show the widget and when it invites the visitor to start talking.
You will find it as the third section of the agent's Widget tab.
What do you need before you can set widget behaviour?
You need at least one whitelisted domain. Widget Behaviour builds one card per approved domain, so until you add one the section reads "Add at least one domain to the whitelist to get started."
Add your domains first, following Whitelisting Domains for Your Marketing Agent Widget.
How do you open Widget Behaviour?
- Sign in to app.docketai.com.
- Select Marketing Agent Configuration in the left sidebar, then open your agent.
- Open the Widget tab.
- Expand Widget Behaviour using the chevron on the left of the section.
Each whitelisted domain gets its own card, so settings on one domain do not affect another.
Where should the widget appear on each domain?
Each card offers three options under Show Widget on.
| Option | What visitors see | Use it when |
|---|---|---|
| All Pages | The widget appears everywhere on that domain. | The agent is useful across the whole site. |
| Selected Pages | The widget appears only on the pages you list. | The agent is built for one journey, such as pricing or demo pages. |
| On Click (Function Call) | Nothing appears until your own button opens it. | You want a specific call to action to start the conversation. |
Choosing On Click (Function Call) needs a small change on your site as well. Setting up OnClick Trigger for the widget walks through it.
Selected Pages is an include list
Selected Pages works by listing the pages that should show the widget. There is no matching list for pages that should hide it, so you cannot start from "everywhere" and carve out exceptions.
If you mostly want the widget site-wide with a handful of pages excluded, you have two practical routes. Either list the pages that should have it, which keeps everything inside Docket, or keep All Pages and control where the script loads from your tag manager. Installing the Widget with Google Tag Manager covers the second approach, where exception triggers decide which pages the script fires on.
When should the widget invite the visitor to talk?
On domains set to All Pages or Selected Pages, When to trigger a callout decides the moment a short prompt appears beside the widget.
| Trigger | What it waits for |
|---|---|
| Time Spent On Page | The visitor has been on the page for the time you choose. |
| Page Scroll | The visitor has scrolled the percentage you choose. |
Time works well on high-intent pages like pricing, where a visitor needs a moment to orient before being offered help. Scroll suits long content pages, where getting part way down is a better signal of interest than time alone.
The option disappears on domains set to On Click, because there is no widget on screen to attach a callout to.
How do you save and test a behaviour change?
- Set Show Widget on for the domain.
- If you chose All Pages or Selected Pages, set When to trigger a callout.
- Select Save.
- Open an included page in a private window and confirm the widget appears.
- Wait or scroll to reproduce your callout setting.
- Open a page that should not show the widget and confirm it stays hidden.
Testing both sides matters. A rule that is broader than you intended only shows up when you check a page that should have been excluded.
How should behaviour differ across domains?
Set each domain to match how people use it. A marketing site often suits All Pages, a documentation site suits Selected Pages, and a campaign landing page often suits On Click so the page's own call to action stays in control.
Frequently asked questions
Can I hide the widget on specific pages?
Not directly. Selected Pages lists pages that should show the widget rather than pages that should hide it. To exclude a small number of pages from an otherwise site-wide deployment, control where the script loads using your tag manager.
Why is Widget Behaviour empty?
No domains are whitelisted for this agent yet. Add one and a card appears for it.
Can one domain behave differently on desktop and mobile?
No. The setting applies per domain, not per device. Teams that need this keep the widget hidden and call it from their own code after checking screen width.
The widget is showing on a page I excluded. What should I check?
Confirm you edited the right domain card, then re-read the saved Selected Pages entries for a rule broader than you intended. Test in a private window so you are not seeing a cached page.
My callout never appears. Why?
Check that a trigger is set for that domain and that you are reproducing it in a fresh session. A callout that has already been shown and dismissed will not immediately reappear for the same page.
Do behaviour changes apply immediately?
They apply to new page loads. Reload without cached content, and clear your CDN or CMS cache if you use one.
Is the callout trigger the same thing as Contextual Callouts?
No. This setting decides when a prompt appears. Contextual Callouts are the AI-written prompts themselves, managed separately by Docket. See Contextual Callouts.