Setup, approvals, and privacy questions

You can start with one page and a small setup your team can review. These answers cover the access you'll need, who should approve changes, and what to check about the data you collect.

Who should build and look after a client setup?

Agree with your client on who builds, reviews, publishes, and maintains it. The person building needs project access. The reviewer should check the visitor paths, the content shown when nothing matches, and any updates sent to connected tools.

For WorkForge (opens in a new tab), one person could build a team-planning quiz while the site owner reviews its wording and data use. Choose someone to repeat those checks after a website redesign or integration change.

Use collaborator invitations, not shared passwords. Access to the editor doesn't replace the client's approval to publish.

What information and access do we need?

You'll need the page, audience, next step or offer, approved wording, and the action you'd like to measure. You'll also need access to the project and permission to install its JavaScript snippet on your site. Identify who can install it and who manages your email platform or CRM.

Give each person only the access they need. Enter provider credentials through the secure integration screen, not in a document, screenshot, or AI prompt.

Plan to test an anonymous visitor, an identified contact if you're using contact data, and someone who doesn't match your targeting. Getting started walks through setup.

Can we start with just one page?

Yes. Choose one real page, one useful audience difference, and one next step. You don't need to personalize the whole website first.

Before requesting approval, agree on the page, targeting, original content for unmatched visitors, data used, and conversion you want to measure. Choose who reviews, publishes, and maintains it. Decide how you'll measure whether it helps without promising a conversion increase.

What if another team approves scripts or DNS changes?

Get that approval before installing RightMessage. Give the website owner your project's snippet and explain where you want it installed. The normal JavaScript setup adds a script to your existing site. Domains in Website & install isn't a DNS configuration tool.

Complete any required security or privacy review before deploying. Don't bypass your website's security controls to make a demo load.

Can someone help us set up without taking over our marketing?

Ask RightMessage or your implementation partner about help with a specific setup. Agree on the deliverables, access, review, handover, and support after launch. One-off setup and ongoing campaign management are different services.

Confirm current availability, fees, and delivery dates for your engagement. Prices or timelines in older demos aren't current guarantees.

Why does RightMessage say it's waiting for my first pageview?

Either the project hasn't received the expected activity or the status check isn't available. Check that the correct project's live snippet is installed and can run, then visit that page.

A staging or development snippet intentionally records no analytics. Privacy controls, script blocking, or a website installation you haven't published can also explain missing activity. Project settings > Website & install shows the code and your installation status. See the project settings reference.

Once data arrives, check your targeting and any form updates in your email platform separately.

Can caching or JavaScript optimization affect widgets?

Yes. A cached page can keep an older installation, and script-delay or optimization settings can change when the snippet runs. Ask the website owner to inspect the page and loaded script before changing those settings.

After an installation change, clear the relevant site cache and try the page again. Don't disable unrelated protections across your whole site.

What should I do if the snippet is installed twice?

Keep one intended project snippet per page. Check both your website's code injection and your tag manager, then ask the installation owner to remove any accidental duplicate and test again.

Check what the browser actually loads first. A second saved copy in a configuration screen doesn't necessarily mean the script runs twice. Don't remove the only working installation by mistake.

Why does my survey appear in a private window but not my regular browser?

The browsers can have different remembered answers, identities, targeting matches, and dismissal states. Compare those before assuming it's a cache problem.

Check the widget's audience rules and how it handles returning visitors. Testing your changes shows how to compare those visitor states.

Can privacy extensions or disabled JavaScript stop RightMessage?

Yes. Browser shields and extensions can block the snippet or its requests. Test with the privacy tools your visitors use.

With the standard JavaScript installation, a browser that can't run the script won't receive its widgets or page changes. Keep useful original content on your site and test it without the script. Different extensions and search crawlers can behave differently.

What customer data does RightMessage use?

It depends on what you set up. The snippet can record page activity and visitor context. Questions and forms collect the answers and contact details you ask for. Identification can connect the browser to a contact, and configured integrations can read or update supported contact data. When RightMessage reads a contact for the browser, it sends only their email and the fields, tags, and lists your project uses. To stop guessed contact IDs in links from identifying anyone, turn on secure email links.

AI-assisted generation uses the business context in AI context. Other AI tasks can use data relevant to what you've asked them to do. Review the workflow and applicable privacy terms rather than assuming every AI action uses only public information.

Document what you'll collect, where it goes, and any approval or consent your use requires. Don't collect sensitive information you don't need. Configuring RightMessage doesn't provide legal approval for a data-processing practice.

The export in Project settings > Privacy & data contains your AI context, audience breakdown and voice-of-customer answers as JSON, not a full account backup. Reset analytics destructively resets reporting. It doesn't confirm that every copy in every connected system has been erased. See data controls, or contact support with privacy questions about your setup.

Can RightMessage wait for cookie consent?

Yes. Turn on Wait for consent before tracking in Project settings > Privacy & data, under Cookie consent, and publish. Until the visitor accepts cookies, RightMessage stores nothing in the browser, runs no tests and sends no stats. Visitors in a test see Control until then. It also waits to look up the visitor's contact in your email platform, including from an email link, once you've published after October 30, 2026. Form submissions, webhooks and email steps still run.

Consent comes from a TCF v2.2 banner, Google Consent Mode, the RM.push(['consent', …]) command, or the decision RightMessage remembered from an earlier page. RightMessage doesn't read the browser's Global Privacy Control signal by itself, so pass it on through your banner if you honor it.

For any other banner, call RM.push(['consent', 'grant']) or RM.push(['consent', 'deny']) from it. If you use RightMessage Edge, update to @rightmessage/cloudflare or @rightmessage/next 0.3.0 or later and redeploy before you turn this on. Older Workers stop personalizing the site until they're redeployed. See use RightMessage with a cookie banner.

Ready to set up? Follow getting started. If you've installed the snippet and it isn't working, use setup troubleshooting.