On-site
Ranla shows banners and modals on your marketing site. Collect email on the message, or use a link. After a capture, optionally send them to any URL: thank-you, PDF, booking. Same snippet as conversions.
Pricing pages, docs, and blog posts fill with people who have never signed up. Lifecycle email cannot reach them. On-site messages can, without a second install.
Active messages render through the marketing-site tracking script you already paste for conversions. No second tag. No app SDK for the public site.
Put an email field on the banner, or keep a classic button that opens a URL. Page rules decide where it shows.
Optional. After they submit a valid email, send them to a thank-you page, PDF, checklist, or booking link. Leave blank to dismiss and stay put.
Collect email on the banner itself, or call identify after signup in your product. Ranla links the anonymous visitor to a contact and credits messages they saw in the last seven days.
Every message tracks how many people saw it, clicked the CTA, or closed it, before anyone has an address.
Submit on a collect-email message or identify after signup: same stitch on the visitor cookie, same Identified count.
After submit is for an instant page or download. Lifecycle and automations handle the inbox once they are a contact.
Ranla can list, draft, and activate on-site messages from the same window it drafts campaigns in. Brand theme stays under your control.
Home walks you through email, product events, and the marketing-site script. On-site delivery uses that script. Prefer collect-email on high-intent pages, set After submit when you have a destination, and still call identify after signup in your app.
Questions
Banners and modals for anonymous website visitors: people on pricing or docs who have not signed up yet. Collect email on the message, or use a link CTA. They render through the same marketing-site tracking snippet used for conversions.
Yes. With Collect email, set After submit to any URL: thank-you page, PDF, checklist, or booking link. After a valid submit, the browser goes there. Leave it blank to dismiss only. Capture also fires on_site.email_captured so an automation can email the asset.
Yes. Create separate messages with different path prefixes, copy, and After submit URLs (for example pricing vs blog). You can also delay show until exit intent, scroll, or a timer.
No. Active messages use the /t.js snippet from Home → Workspace setup. You can still call identify after signup in your product so in-app converts stitch the same way.
Yes. Ranla can list, draft, and activate banners and modals the same way it drafts campaigns. Brand colors live in one account theme.