Page-Aware Widget

Support that knows where the user is stuck.

The Canonica widget uses safe product-page context so billing, onboarding, team settings, and release questions can resolve to different approved support truth.

app.canonica.app
Widget allowed

Page-Aware Widget

Widget runtime and page context

One script gives the product a support layer that can prefer the current page, related FAQ, release note, and canonical answer before fallback.

Allowed origins

Restrict where the widget can run so copied snippets do not become open support endpoints.

Blocked routes

Hide the launcher on sensitive screens such as payment cards, auth flows, or private admin routes.

Safe page hints

Pass route, feature, workflow, role, or plan context without using raw client data as tenant scope.

Readiness view
Context key
billing_invoices
Answer path
Canonical first
Fallback
Captured

What this gives the owner

The widget is configurable without becoming risky.

Product owners get practical controls for install, appearance, route behavior, and context without exposing internal IDs.

One embed script

Install the widget once and let dashboard settings control runtime behavior.

Route-aware answers

The same question can resolve differently on invoices, onboarding import, team permissions, or release pages.

Hosted help handoff

Users can move from the widget to hosted docs, FAQs, and changelog content on your support domain.

Feedback as signal

Negative feedback and fallback answers become review work, not invisible chat noise.

Mobile-first support

The widget is designed for product screens where users are already working, including mobile surfaces.

Workflow

Install once, then make each product page smarter.

Canonica separates the runtime key, allowed origins, blocked routes, and page context so widget behavior stays maintainable.

1

Generate widget key

Create the widget credential from the Canonica dashboard and copy it during setup.

2

Install the script

Place the widget snippet in the client product shell or selected app surfaces.

3

Configure access

Add allowed origins and blocked routes so the widget appears only where it should.

4

Send safe context

Pass page, feature, workflow, role, or plan hints when they help answer safely.

5

Review gaps

Use fallback and feedback signals to improve canonical answers over time.