Page Targeting

Target messages based on where users are in your application. Show contextually relevant messages on specific pages.

Available Fields

Field	Description	Example
Page URL	Full URL including domain	https://app.example.com/dashboard?tab=overview
Page Path	Path only (no domain or query)	/dashboard

When to Use Each

Page URL

Use for:

• Exact URL matching

• URLs with specific query parameters

• External or specific domain pages

Page Path

Use for:

• Path-based matching (recommended)

• Works across domains (dev, staging, prod)

• Cleaner rules without domain clutter

Common Patterns

Specific Page

Show on exact page:

Page Path → Equals → "/dashboard"

Section of Your App

Show on all pages in a section:

Page Path → Starts With → "/settings"

This matches:

• /settings

• /settings/profile

• /settings/team

• /settings/billing

Excluding Pages

Show everywhere except specific pages:

Page Path → Not Equals → "/checkout"

Or exclude a section:

Page Path → Does Not Start With → "/admin"

Multiple Pages (OR)

Show on several specific pages:

Group 1: Page Path → Equals → "/dashboard"
OR
Group 2: Page Path → Equals → "/projects"
OR
Group 3: Page Path → Equals → "/reports"

URL Contains

Match pages containing a pattern:

Page Path → Contains → "/settings"

This matches:

• /settings

• /user/settings

• /account/settings/profile

With Query Parameters

Match specific URLs with parameters:

Page URL → Contains → "?upgrade=true"

Or:

Page URL → Contains → "ref=email"

Operators

Operator	Description	Example
Equals	Exact match	Path equals /dashboard
Not Equals	Doesn't match	Path not equals /login
Contains	Appears anywhere	Path contains settings
Not Contains	Doesn't appear	Path not contains admin
Starts With	Begins with	Path starts with /app
Ends With	Ends with	Path ends with /edit

Examples by Use Case

Dashboard Announcement

Show feature tip on dashboard:

Page Path → Equals → "/dashboard"

Checkout Offer

Show discount on billing pages:

Page Path → Starts With → "/billing"

Settings Help

Show help on any settings page:

Page Path → Contains → "settings"

Feature Page Banner

Announce related feature on specific page:

Page Path → Equals → "/reports"
AND
Contact Property → Plan → Equals → "free"

"Upgrade to Pro for advanced reports"

Onboarding by Page

Show contextual onboarding tips:

On projects page:

Page Path → Equals → "/projects"
AND
Event → project_created → Has Not Done

"Create your first project to get started"

On team page:

Page Path → Equals → "/team"
AND
Event → team_member_invited → Has Not Done

"Invite your team to collaborate"

Exclude Login/Signup

Show to authenticated pages only:

Page Path → Does Not Start With → "/login"
AND
Page Path → Does Not Start With → "/signup"

Combining with Other Rules

Page + Contact

Show upgrade prompt on billing page to free users:

Page Path → Equals → "/billing"
AND
Plan → Equals → "free"

Page + Event

Show feature tip to users who haven't used it:

Page Path → Equals → "/analytics"
AND
Event → custom_report_created → Has Not Done

Page + Time

Show to new users on specific page:

Page Path → Starts With → "/dashboard"
AND
Signed Up At → Is Within → 7 days

SPA Navigation

Cueflow automatically detects page changes in single-page applications (SPAs) by listening to the History API.

When users navigate:

1. Page context is re-evaluated

2. New matching messages appear

3. Non-matching messages are hidden

You can also manually trigger a check:

Cueflow.check();

Best Practices

Use Page Path

Prefer page path over full URL:

• Works across environments

• Simpler rules

• No domain issues

Be Specific

• Match exact paths when possible

• Use starts with for sections

• Avoid overly broad contains rules

Test Navigation

• Verify messages appear/disappear on navigation

• Check SPA transitions work correctly

• Test browser back/forward

Consider Context

• Match message content to page

• Don't show unrelated messages

• Use page context to enhance relevance

Troubleshooting

Message shows on wrong pages

1. Check rule operator (equals vs contains)

2. Verify path format (leading slash)

3. Test with exact path from browser

Message doesn't appear on any page

1. Check the path value matches exactly

2. Verify no conflicting rules

3. Test with simpler rules first

SPA navigation issues

1. Ensure Cueflow.init() was called

2. Check console for errors

3. Try Cueflow.check() manually