State Triggers Overview

State Triggers let you change the quick-action chips your widget shows based on the page the user is on. Define a URL pattern, attach one or more chip messages, and the widget surfaces those chips whenever the user is on a matching URL.

State Triggers are configured per widget — you add them on the Create Widget screen, scoped to the widget being created.

How State Triggers work

Each State Trigger has these parts:

1. URL pattern — Matched against the current page URL. You can use an exact path, a substring (contains), or a wildcard (*). Examples: /pricing, /about, or https://example.com/contact.
2. Messages (chips) — One or more short prompts. Each becomes a tappable chip the widget shows when the pattern matches. At least one message is required.
3. Widget — The widget the trigger belongs to.

When a user lands on a page matching the pattern, the widget shows the trigger’s chips. As the user moves to a different page, the widget applies a matching trigger’s chips or falls back to the widget’s default chips.

Adding a State Trigger

On the Create Widget screen:

1. In the State Triggers section, enter a URL Pattern.
2. Add one or more Messages — each is a chip. Use Add message for more than one.
3. Click Add State Trigger to stage it.
4. Repeat for additional patterns. Staged triggers are saved when you create the widget.

Pattern matching

Patterns support three styles:

| Style | Example | Matches | |-------|---------|---------| | Exact | /pricing | Only the /pricing page. | | Contains | settings | Any URL containing settings. | | Wildcard | /checkout/* | Any URL under /checkout/. |

You can also use a full URL (e.g. https://example.com/contact) when you want to match a specific absolute address.

Common use cases

• Page-specific prompts — Show “Why was I charged twice?” on a billing page and “How do I reset my password?” on an account-security page.
• Funnel coaching — On checkout pages, surface prompts that answer common pre-purchase questions.
• Feature-area help — On a complex settings page, offer chips mapped to the most-asked questions for that surface.

State Triggers vs. Guides

State Triggers swap chips — short prompts the user can tap. Guides are step-by-step walkthroughs the user steps through. Use State Triggers for short contextual prompts; use Guides for end-to-end task instruction. Both are part of User Support.

Tip

Start with a State Trigger for one or two of your most-visited support pages — billing, account settings, or checkout — and watch which chips users actually engage with before expanding coverage.