Comparison · popups and forms
Getsitecontrol and our Smart Popups do the same job: show the right message at the right moment and capture a contact. They diverge after the submit — in what gets metered and where the lead lands. This page is about both, without "we are better".
Facts about Getsitecontrol were captured from its own pages on 1 and 12 September 2026; each one carries a link and a date. getsitecontrol.com
Signing up is free and needs no card · the popups themselves are a paid extension, $9/mo
A visitor is reading a product page and about to leave. You need to show an offer and capture a contact. Here is what happens on each side — first through the visitor's eyes, then through the owner's.
What the visitor sees, and what happens once they leave a contact.
Vendor · Getsitecontrol
Us · Cenaly.com
What you configure, what you pay for, and how you know the campaign works.
Vendor · Getsitecontrol
Us · Cenaly.com
This is the real divergence. With a standalone widget service the contact stays in its own dashboard and its own mailings — that is how the product is built, and it is not a criticism. With us the popup is part of the system you already run your shift in.
One list of everything inbound for the location: popup leads, storefront form answers, contact-form messages, callback requests, appointments and table bookings. Groups build themselves — per campaign and per specific form — with nothing to configure.
Surface (your site or the Cenaly.com storefront), campaign, the page with a link to it, UTM tags, referral class — maps, search, social, direct — and device. It is computed on read from fields that are stored anyway, so no second truth about the lead's origin ever appears.
A popup action can open the guest chat with a pre-written question or add an item to the order widget's cart. If the neighbour is not on the page, the campaign does not show and does not burn its frequency cap — better than a button that leads nowhere.
A form already sitting on your site and posting to your own backend can be captured by a rule: selector, field mapping, page masks. Only name, phone and email leave the page, the native submit is untouched, and a repeat within ten minutes produces one lead. Up to ten rules per location.
The code issued by a campaign is validated through a public endpoint and works in a storefront order — instead of staying a string the cashier types by hand.
The tag, Google Tag Manager, single-page apps and Content-Security-Policy break widgets more often than anything else. Below: what our snapshot of the vendor's pages says, and what we know about ourselves — including the awkward parts.
| What we compare | Getsitecontrol | Cenaly.com |
|---|---|---|
| What goes on the site | There is a JavaScript API (gsc), webhooks and Zapier; for Shopify, a dedicated app and its own Aurora theme. With a built-in email stack, fewer third-party integrations are needed. source · 2026-09-01 | One site/v1.js tag for all twelve widgets: what runs is decided by toggles in the admin panel, and the tag never changes again. A settings change reaches the site in five minutes — that is the CDN cache. |
| Installing through Google Tag Manager | The pages captured on 1 and 12 September 2026 do not describe installation through GTM — worth checking in the vendor's own documentation. (not stated on the pages we captured) | It works, but our server-side install check will never see such a tag: it reads the page markup rather than executing it. That is exactly why we never raise a "your tag is gone" alert for GTM sites — it would always be a false alarm. |
| A single-page app (React, Vue, Next) | The captured pages list behavioural and page-level display conditions; behaviour during navigation without a reload is not described separately. (not stated on the pages we captured) | A URL change without a reload counts as a new page of the session: campaigns are re-evaluated, the pages-per-session counter grows, scroll depth resets. An inline block survives a transition only together with its container — otherwise it is removed rather than sticking to the whole site. |
| A site with Content-Security-Policy | The captured pages carry no CSP requirements and no list of hosts to allow. (not stated on the pages we captured) | The loader copies its own nonce onto every tag it injects. But two lazy halves of the popups — engage/rich-v1.js and engage/slots-v1.js — are not covered yet: under a nonce-only policy without our CDN host they will not load, and rich campaigns (quiz, wheel, boxes) will not appear. Window styles live in a Shadow DOM and need style-src 'unsafe-inline'. |
An empty cell on the left is not a complaint about the vendor — it is an honest description of our snapshot of its marketing pages. Its documentation may well say more. Check before you choose if your site is a single-page app or runs a strict CSP.
Comparing monthly prices is pointless until the unit matches. Getsitecontrol meters widget views and sent emails; we charge a subscription per location.
| What we compare | Getsitecontrol | Cenaly.com |
|---|---|---|
| Widget views | The main unit: Free — 10,000 views a month, Pro $19 — 100,000, Pro Max $29 — unlimited views. source · 2026-09-01 | Not metered at all: there is no view counter on any tier. |
| Sent emails | Billed separately from views: $2 per thousand emails on Free, $1.60 on Pro, $1.40 on Pro Max. source · 2026-09-01 | Not charged, because we have no marketing mailings to popup leads at all — only the notification path sends email. That is a missing feature, not a benefit. |
| Contacts in the base | Unlimited contacts are stated on every tier, including the free one. source · 2026-09-01 | Not metered: neither leads, nor contacts, nor sites appear on the bill. |
| The widget itself | Popups are part of the general plan alongside the email stack; annual payment is 25% cheaper. source · 2026-09-01 | The Smart Popups extension costs $9/mo. Paid annually, you pay for ten months instead of twelve. One subscription covers both your site and the Cenaly.com storefront. |
| Removing the branding | Branding removal is available on every tier, including the free one. source · 2026-09-01 | Nothing to pay for: there is no "made with Cenaly.com" mark on the widgets on any tier. |
Cases where the honest answer is "take theirs". We do not cover these, and we are not going to pretend otherwise.
Broadcasts, email templates, action-based automations and contact segmentation sit next to the popups on their side (captured 2026-09-01). We have no marketing mailings to popup leads at all: you can export the contact, but no campaign email will leave our system.
A Shopify app, the Aurora theme, add-to-cart and remove-from-cart triggers, and targeting by cart contents and product data are their stated focus (captured 2026-09-01). Our popup only knows about a third-party cart what the site tells it through an API call or an event.
Hide rules (the widget removes itself after N seconds or past a scroll depth) and stop rules ("forever after submit", "N days after a close", "after X views") are an explicit model on their side (captured 2026-09-01). We have campaign frequency caps, but not that explicit a lifecycle matrix.
Geo down to region and city, operating system, browser language, screen width, session count — and on the developer tier, cookies, IP address and a custom JS condition (captured 2026-09-01). We offer page masks, device, referrer, UTM, country, new-versus-returning and the cart, but not those axes.
Our main argument is that the lead lands in the same account as orders, bookings and the shift. If you run orders and appointments in another system, that argument does not hold — and with it goes the reason to choose us.
CenalyEngage.cart or a GTM event — or what our own order widget sees on the same page. Every claim above was captured from these pages on the date shown. The vendor may have changed since — the links go to the original, check for yourself.
We do not quote third-party reviews, logos or screenshots, and we never present a vendor's numbers as our own. Found a discrepancy with the vendor's page? Tell us and this page gets corrected.
There is no automatic import: the formats and the condition model differ, so a campaign has to be rebuilt in the editor by hand. Contacts you have already collected stay in their base; our system would not email them anyway.
In where the lead goes. A builder's popup shows the window and files the contact in its own list; ours lands in the Leads inbox next to bookings, appointments and orders, with an origin passport — page, campaign, UTM, device.
The Smart Popups extension costs $9/mo; paid annually you pay for ten months instead of twelve. It includes every format plus the inline block, forms and quizzes, coupons, targeting, frequency caps and A/B. Views, campaigns and captured leads are not metered.
Yes, and it is the same per-location subscription. The teaser bubble and the issued-code reminder share one key, so a code obtained on your site is visible on the storefront too.
Yes, the tag goes into the page or site HTML block. But on site builders you do not control the Content-Security-Policy header, and if it is strict there, only an allowed CDN host helps — a nonce will not.
Call CenalyEngage.getDiagnostics() in the console: it names the reason per campaign — using the same predicate the real selection uses — and shows whether the container for an inline block was found.
More detail — per-platform installation, settings and troubleshooting — in the docs. Installation guide →
The widget page explains how it works on our side, the docs cover installation and setup, the hub lists the other eleven.
Sign up, paste the shared website tag and turn on Smart Popups — the leads arrive in the same place where you look at bookings and orders.
Get started freeNo card · views and leads are not metered · popups are a paid extension