Web Messages

Web Messages show targeted in-app announcements or start a chat without requiring a separate push-notification service. They use the same public script as the Managani widget.

Build a Message

Choose a custom announcement or chat format. Add rich content, an optional call-to-action label, and an action that opens chat, feedback, a URL, or nothing.

Messages can inherit the active site theme or use their own position, width, colors, radius, and shadow.

Target and Schedule Delivery

Control eligibility with:

• One or more widget deployments
• Included and excluded URL rules
• Customer profile conditions matched as all or any
• Time-on-page or exit-intent display conditions
• Once-per-day, one-time, once-per-session, or every-page frequency
• Stop after click, dismissal, first display, or a configured view count
• Priority when several messages are eligible

Anonymous visitors can receive messages. Signed identity is required for customer-level targeting and history.

Measure Results

Managani records shown, clicked, and dismissed totals. Review these metrics in Web messages and use Tracking for the surrounding product activity.

Prepare and Review a Message

Start with the action you want the visitor to take. A release announcement might link to a product page, while a help prompt can open chat. Keep the call-to-action label consistent with its destination so customers know what will happen when they select it.

Check targeting before adjusting appearance. Review included and excluded pages, the selected widget deployment, and whether the audience requires signed customer information. An anonymous visitor cannot be matched using customer-specific history, so test anonymous and signed-in experiences separately when both matter.

Use frequency and stopping rules to avoid showing an announcement long after it is useful. When several campaigns are active, review priority so the most relevant message wins. After launch, compare shown, clicked, and dismissed totals with the surrounding product activity. A high display count alone does not establish that the announcement helped customers complete the intended task.