Popups and A/B tests

Popups is an optional module under Marketing. Web and Era desktop use the same editor. Enable Website and Forms first; lead capture also needs CRM. Install through Settings → Modules. Reading needs read, editing manage, deletion delete.

Prepare an offer

Open /popups, choose Yeni popup, then select a website. Enter the A and B titles, plain text, optional HTTPS image and CTA. The B traffic share is 0–100%; zero serves A only. Optional start and end dates use the editor’s local time. Drafts never reach visitors. Saving starts a new revision and keeps earlier results.

Choose arrival, delay in seconds, exit intent or scroll percentage. Page targets are pathname prefixes: / matches everything; /products matches that section. Filter new/returning visits and mobile/desktop. Frequency is once per session, once in 24 hours or once. Browser storage holds these preferences, so another device or clearing storage resets them. Exit intent uses the mouse leaving the top edge and does not fire on touch-only devices.

Capture a lead

Select an active lead form from the same workspace. Questions, validation and consent come from Forms. The existing form engine creates the CRM lead; there is no separate popup form engine. Table forms are excluded. A different workspace’s form cannot receive the popup’s answers.

Compare results

Views, clicks, successful submits and submit/view conversion rate appear per revision and variant. Repeating an event for the same impression does not count twice. These are browser events, not bot-filtered unique people or a statistical significance calculation. Website preview does not display or measure visitor popups.

Ask Era

Ask “Show this offer to new mobile visitors after five seconds, with 30% on B.” Era discovers popups.save through the permission-filtered action catalogue. MCP uses era_find / era_run; CLI uses era find / era run. Supply the website, form and targeting. Era acts with the member’s existing capabilities.

Custom storefronts can use Site SDK listPopups, trackPopup, submitPopup and /api/site/v1/<siteId>/popups. The API requires a published site, an allowed origin, enabled modules and rate limits. Website content is public; drafts and analytics remain behind member permissions.