Target a workflow to specific pages

Why page targeting matters

The same widget can show a different workflow depending on where a visitor is on your site. A visitor on your pricing page is at a very different stage than one on your documentation page. Targeting lets you run the right workflow in the right context.

How targeting works

Page targeting in workflows is controlled by two mechanisms working together:

1. Widget assignment: A workflow only fires on widgets you explicitly link it to. If you have separate widgets per domain section, assign this workflow to the right one.
2. Trigger conditions: Within a trigger type, you can add URL-based conditions to restrict the workflow to specific pages.

Set URL conditions in the trigger

1. Open the workflow and go to the Settings tab.
2. Under Trigger, choose your trigger type (for example Visit or Chat Open).
3. In the trigger configuration, look for Conditions.
4. Add a condition: Current URL → choose a match type:

• Contains: Fires if the URL contains a string (e.g. /pricing matches example.com/pricing and example.com/pricing-faq).
• Equals: Fires only on an exact URL match.
• Starts with: Fires on any URL under a path prefix (e.g. /docs/ matches all documentation pages).
• Regex: Advanced — fires when the URL matches a regular expression pattern.

Add multiple URL conditions with OR logic to cover several paths in one workflow.

Common page-targeting setups

Page	Workflow goal	Condition
Pricing page	Qualify leads, book demo	URL contains /pricing
Documentation	Direct to KB or Vex AI	URL starts with /docs
Checkout	Reduce cart abandonment	URL contains /checkout
Homepage	General welcome + triage	URL equals /

Running multiple workflows on the same page

A single page can trigger multiple workflows if their conditions all match. Priority between workflows is determined by their creation order — the oldest active workflow with a matching condition fires first. For more on this, see Run multiple workflows at the same time.

Visitor property conditions

Beyond URL, you can condition on visitor data: whether the visitor is identified (has a name or email), their plan level, or any custom attribute you pass via Yaplet.identify(). This lets you show a premium-user workflow on the same page where a free-user sees a different one.

Next step

If you need to collect the visitor's data as part of the workflow, see Collect data with a workflow.