On-Site Engagement Campaigns
Engagement campaigns are popups, offers, and coupon reveals on your storefront that appear to a guest based on a rule you set — on exit intent, after N seconds on a page, when an item is added to the cart, and so on. The section lives in Admin Panel → Website → "Configure site" → "Proactive messages" (admin.masamenu.tr) and works on any vertical — restaurant menu, shop, hotel, salon — except kiosk mode.
A campaign only appears on the storefront once you've created and enabled it — the section ships with nothing turned on by default.
Campaign types and display formats
Each campaign is one of six actions:
| Type | What it does |
|---|---|
| Announcement | Plain text with a title — an announcement, reminder, or informational message |
| Offer | Text + a button linking to a promo page, category, or specific item |
| Email capture | An email field + a consent checkbox → a subscriber added to the newsletter list |
| Coupon reveal | A real coupon code from the location + a "Copy" button; a countdown timer if the coupon has an expiry |
| Open AI chat | Opens the location's AI assistant chat with a preset first message |
| Open staff chat | Opens the guest chat with a staff member with a preset first message |
Display is one of three formats: a modal window (screen center), a slide-in panel (side/bottom), or a thin bar at the bottom of the screen that doesn't cover the content.
AI campaign draft by text or voice
The campaign editor has a panel where you can describe in words — typed or spoken via the browser microphone — what the campaign should do: "offer a discount to people leaving a product page above $50" or "remind everyone who came from ads about free shipping over $100." The model produces a draft — copy in the location's languages, a button, a trigger type, and audience conditions — using the location's real data: existing coupons, catalog categories, enabled languages and currency, not invented values.
The draft opens in the editor for review — it is not saved automatically; you review it, adjust if needed, and save it, exactly as with a campaign built by hand.
Triggers, audience, schedule, show limits
When to show it — one of these triggers:
- time on page — after a set number of seconds since the page loaded;
- exit intent — the cursor leaves the window on desktop; idle time on mobile;
- scroll depth — after scrolling a set percentage of the page;
- idle time — the guest hasn't moved the cursor or scrolled for a set time;
- cart change — with a condition on cart total or item count;
- pages per session — starting from the Nth page viewed in a visit.
Who to show it to — you can restrict by: new vs. returning guests, device type (mobile/desktop), interface language, traffic source (utm), specific site pages (by path mask), and the content of the open page — a catalog section, item tags, or the price of the open product.
When it's active — an optional schedule: a date range, days of week, business hours.
How many times to show it — a show limit and period (e.g., no more than once every 7 days), stopping after the guest takes the target action, plus an overall cap on popups per visit and per day — so different campaigns don't bury one guest under a stack of windows. Campaigns stay out of checkout's way: modal and slide-in formats don't show over an open checkout by default.
Ready-made shop campaigns
Separate from the campaign builder, retail storefronts get ready-made widgets in the site appearance settings — they work as soon as you turn them on, with no trigger configuration needed:
- Lucky wheel — the guest enters an email, spins the wheel, and gets a code for one of the location's coupons; enabled in the storefront appearance settings;
- Free-shipping progress bar — shown in the cart, tells the guest how much more they need to spend to reach the free-shipping threshold; it appears on its own once a threshold is set in delivery settings;
- Back-in-stock subscription — a form on an out-of-stock product page: the guest leaves a contact, and an email is sent automatically once the item is back on the storefront;
- Callback request form — a "Request a call" widget on the site: the request lands in the owner's inbox by email, and the request list is on the Customers page, "Callback requests" tab.
These widgets and the campaign builder run side by side on the same page without conflicting — only one popup shows at a time.
What you can see about results
Every campaign view, click, dismiss, and conversion is sent as an event to the location's Google Analytics (if a GA4 property is connected — see Analytics). There isn't yet a built-in campaign report inside the admin panel itself — how many times a campaign was shown, how many clicks, how many signups or offer click-throughs — those numbers currently live only in GA4.
Related sections
- Website builder — where the "Configure site" section lives
- Customers — callback requests and newsletter subscribers
- Analytics — where campaign events are sent
FAQ
The campaign shows in the editor but isn't visible on the site — why?
Check that the campaign is enabled, not just saved as a draft, and that a few seconds have passed since the page loaded — popups are intentionally silent for the first moments of a visit so they don't interrupt the guest.
Can I limit a campaign to one product category?
Yes — audience conditions let you target specific catalog sections, item tags, or a price range of the open product; the campaign only fires on a matching page.
Can the AI invent a coupon that doesn't exist?
No, the model only inserts coupons, languages, and categories that actually exist at the location — a draft referencing a nonexistent coupon code is rejected before it reaches you.
Do campaigns get in the way of checkout?
No, by default modal windows and slide-in panels don't show over an open checkout; the bottom bar doesn't block the interface and can stay visible.