Free · numbers computed server-side
Show orders, bookings, appointments and average ratings in small notices. Masamenu.tr calculates the figures; you do not enter your own numbers or notification text.
The widget is free. It needs recent events in Masamenu.tr; notices stay hidden when there is too little data or a threshold is not met.
They start looking at your offer. The badge doesn’t jump out at once: you set the delay before the first one, and by default the widget lets people settle in.
Examples: “14 orders today” or “★ 4.8 — 37 ratings”. Your site shows eligible account data, not these demonstration figures.
The badge leaves by itself, and the next one appears no sooner than the pause you set — 45 seconds by default, counted from the moment the previous one left, so nothing flickers.
The cross switches the badges off for the rest of the visit. If they just move to another tab, impressions wait for them instead of being spent.
Signup opens setup for the selected product. Have your domain and permission to insert code ready.
Follow your platform instructions. Blocking trackers before consent requires the early CMP script, not just the shared async tag.
Enable the widget and try the visitor action on the published page. Settings may appear after the cache refreshes.
The tag
<script src="https://cdn.masamenu.tr/site/v1.js" data-domain="your-site.com" async></script> Shared widget tag. See the separate CMP instructions for blocking trackers before consent.
Figures come from events in your Masamenu.tr account: placed orders, created bookings and appointments, and received ratings. Installing the tag on another shop does not import its orders. Counts represent placed orders or created bookings and appointments, not paid purchases, completed visits or revenue.
Settings have no field for a custom count or notification text. Wording follows the event type and count; public notices show no guest names, review text or purchased items.
Anything older than 36 hours is not displayed in any form, and “today” is checked against the venue’s own calendar: once the day turns over, yesterday’s orders stop counting as today’s. Best for venues with days off and uneven flow.
A number below the threshold isn’t shown at all — 3 by default. The average rating has a floor of its own: it only appears from 5 ratings over 90 days, and that floor cannot be lowered. Best for new locations and seasonal businesses with sparse data.
Up to 4 badges per visit by default, the pause counted from the moment the previous one left, a hidden tab spends no impressions, the cross switches the badges off for the session, and the animation respects the system “reduce motion” setting. Best for sites with long sessions.
Any of the four corners, your own accent colour, page masks, device and a schedule. If one of our floating buttons already sits at the bottom, the badge rises above it instead of landing on top. Best for sites running several widgets.
Example: “14 orders today” on the menu page shows the visitor that people have already ordered through the site today.
Example: “7 appointments this week” on a service page shows real demand without a single invented review.
Example: “The table was booked 5 times today” belongs exactly where a guest is choosing between you and the place next door.
Example: “★ 4.8 — 37 ratings” comes from your own reviews over 90 days and appears only from 5 ratings.
Masks keep the badges on the landing pages you choose, and away from the blog and the legal sections.
While the numbers are small the widget stays silent: the decency threshold won’t advertise an empty room, and the badges appear by themselves once the flow starts.
Example interface. Customise colours, position and labels, then check your page on desktop and mobile.
Exact menu names and plan requirements, taken from each platform’s own help center.
Sites built with our website builder ship with the widgets already wired — nothing to paste.
Step-by-step guides per platform — in the help center →Free
Basic versions of eight widgets are free. Table booking, popups, help and legal pages on external sites are extensions. Connected services can cost extra.
| Without the widget | With the widget | |
|---|---|---|
| Where the number comes from | ✕ Account activity is not visible to site visitors | ✓ Our server counts the number as the order, booking, appointment or review lands |
| Badge text | ✕ Figures must be copied into page text manually | ✓ There is no “badge text” field: the system builds the wording from type and number |
| Stale data | ✕ Published figures need manual freshness checks | ✓ Anything older than 36 hours is hidden, and “today” follows the venue’s calendar |
| Personal data | ✕ Your publication method determines which details are public | ✓ The public schema has no fields for a name, a city or one person’s purchase |
| Cost | ✕ You need a way to display account activity | ✓ The widget is free and works on your site and on the storefront at once |
Social proof on a website is a short note that other people have already made a choice: how many orders today, how many bookings this week, what the average rating is. It works on a simple basis — people feel safer where others have been before them.
The trouble is that the genre damaged itself. More often than not the badge is arbitrary text that arrived from outside, and in places the events are typed in by hand. Visitors sense it, and a line like “someone from the next town just bought this” produces distrust rather than trust — and it rubs off on your offer.
This widget is built differently at the schema level: our server counts the number as an order, booking, appointment or review lands, and the public file has no free-text field at all — there is physically nowhere to put a name or an invented purchase, and a build test checks it. Stale data retires itself: anything older than 36 hours is hidden, “today” is checked against the venue’s calendar, and the average rating is only published from 5 ratings over 90 days. The owner chooses WHAT to show and from which threshold — not what it will say.
Social proof is the wrong widget for a young site with no orders and no ratings yet: the thresholds are built so that with empty data the badge simply never appears, which is better than invented activity. And it is not a popup — proof can say nothing beyond a counted number. If you need to carry an offer, a discount or capture a contact, that is the job of smart popups.
There will be no orders badge until the number reaches the decency threshold — 3 by default. Other enabled fact types can still show if they pass their own conditions. If nothing qualifies, the widget stays silent, and that is deliberate: advertising an empty room does more harm than showing nothing.
Settings have no field for a custom count or notification text. Wording follows the event type and count; public notices show no guest names, review text or purchased items.
Figures come from events in your Masamenu.tr account: placed orders, created bookings and appointments, and received ratings. Installing the tag on another shop does not import its orders. Counts represent placed orders or created bookings and appointments, not paid purchases, completed visits or revenue.
From your own events: an order reaching the “placed” status, a table booking or a service appointment being created, a review being applied. The recalculation happens as the event lands, not on a schedule.
Up to 4 per visit by default, each staying for a few seconds, with the pause counted from the moment the previous one left (45 seconds by default). The cross switches the badges off for the session, and a hidden tab spends no impressions.
The average and the number of ratings over 90 days from your own reviews — three numbers and nothing more. It is published from 5 ratings; review texts, names and dates are not in the public file.
Yes. One toggle switches the widget on for both your website and your Masamenu.tr storefront: the same selection rules, the same timings, the same text. There is deliberately no surface switch — you cannot enable the badges on only one of them.
The widget reads a public aggregate and selects eligible facts to display. The loader, data file and interface use network and device resources. Test speed and positioning on your page, especially beside other widgets.
Social proof is the lightest of our page widgets: about 15 KB gzipped, with the async attribute and after the page has loaded. It doesn't compute anything in the browser — our server refreshes a ready public file the moment an order, booking or review happens, and the widget reads it once. No database calls, no work on the visitor's device. The badge lives in a Shadow DOM.
The site receives public numeric aggregates without names or review text. The widget also sends load, display and dismissal events for statistics.
An account, your website domain and permission to insert code. Prepare the selected widget’s data and test your published page. Follow the separate cookie banner instructions for early tracker blocking.
Style isolation reduces conflicts but does not replace testing. Check buttons, forms, mobile layout and other scripts on your site.
Set your own texts separately; built-in labels fall back to English where translations are missing. Core data is stored in the brand’s cloud. Connected AI, telephony and other services have separate processing terms.
More — installation per platform, settings and troubleshooting — in the help center. Installation guide →
Signup opens activity-notice setup. Choose fact types, a threshold and display pages, then check the published site.
Set up activity noticesThe widget is free. It needs recent events in Masamenu.tr; notices stay hidden when there is too little data or a threshold is not met.