Identification and cross-device questions

You can personalize for anonymous visitors and use more of what you know once RightMessage identifies them. These answers explain when a browser connects to a contact, what it remembers, and what happens on another device.

Does installing the snippet identify my subscribers?

No. The snippet can recognize a browser and record its activity, but it needs an identification event to connect that browser to a contact. Connecting your email platform doesn't identify everyone on your list either.

An identifying form or Email question, an identifying email link, or a supported provider lookup can make that connection. See how identification works.

Can I personalize before someone subscribes?

Yes. You can use available page visits, referrals, UTM parameters, device information, and answers collected on your site. Those conditions don't need an email list.

To use provider tags, fields, or purchase data, you need the appropriate integration and a contact it can identify.

Why are survey responses anonymous when my email platform is connected?

The connection gives RightMessage access to your platform, but it doesn't tell us who answered. Check whether the browser completed a supported identification event and whether the contact lookup succeeded.

For example, a visitor can answer a team-size question on WorkForge (opens in a new tab) without giving an email. WorkForge can still use that answer to decide what to show them next.

Is creating a contact in my email platform enough?

No. A contact created by your server, an automation service, or another tool isn't automatically connected to the browser viewing your page.

Use an identifying form interaction, a form redirect handoff, or another documented identification method. Then check the browser's identity.

How does an email link identify a subscriber?

The link includes the identifier your connected platform expects. RightMessage reads it and looks up the contact. Some providers add it automatically. Others need you to add a merge tag to the link.

Follow your provider's integration guide. A tracking parameter such as utm_source=email describes the campaign, not the individual subscriber.

What does an ActiveCampaign link need?

It needs the rm_ac parameter with a contact identifier that the integration can look up. A tag name or an invented number won't identify the contact.

Having ActiveCampaign tags doesn't identify an anonymous browser. Use the merge syntax in the ActiveCampaign setup guide, then test with a synthetic contact.

Will a returning subscriber be remembered?

Yes, if that browser was successfully identified and its cookies and site data are still available.

A private window, a different browser profile, cleared site data, or another device can start without that identity. The contact's presence in your email platform doesn't identify the new browser.

What happens on another device?

The second device needs its own identification event. A correctly configured identifying email link can recognize the subscriber there too.

Once both browsers are connected to the contact, their activity can appear in one contact profile. RightMessage doesn't automatically recognize every device the person owns. Cross-domain context doesn't cross devices by itself either.

What happens to answers collected before identification?

RightMessage can keep answers in the same browser and use eligible mapped answers after identification. It doesn't import every anonymous response into your email platform.

The question's mapping, consent, available browser data, contact lookup, and provider acceptance all affect what syncs. Passive synchronization won't replace a populated provider field with a stale saved input answer. A newly submitted answer is a separate, active update.

See visitors, responses, segments, and fields for how these records fit together.

Why do I see an answer but no contact update?

Capturing an answer and syncing it to your provider are separate actions. Check the browser's identity, the question's sync destination, the field type or tag, and the provider's permission to accept the update.

For Email questions, Identify the visitor controls identification, not every mapped-field update. With that setting off, an answer can still sync to a mapped field for an existing contact. When identification is on and a displayed consent checkbox is unchecked, RightMessage keeps the response without identifying the visitor or syncing that answer.

Follow anonymous visitor and missing-update troubleshooting to find where the update stopped.

Can Email Watcher identify visitors from external forms?

Yes. Email Watcher can capture an email without a Popup's After a form is submitted trigger. You'll find this optional setting under General, in Visitor Identification. It starts off.

It captures a valid email when someone leaves a field or presses Enter, which can happen before they submit the form. It ignores RightMessage question inputs so their own consent and identification settings stay in control.

Could Email Watcher identify the wrong person?

Yes. If someone enters a colleague's or gift recipient's address, the watcher can use that address as the visitor's identity. Entering an email doesn't prove ownership or permission to send marketing.

Leave Email Watcher off where visitors are likely to enter another person's address. Use an explicit supported identification method instead. See website form identification.

How do I check my own browser's identity?

Open the RightMessage debugger and inspect Visitor. Check the identity separately from the browser's segments and responses.

If you've forced an identity through debugger impersonation, you're looking at a test state. Check a normal visitor journey to confirm that identification happens without it.

How do I test new and existing subscribers separately?

Use separate clean browser sessions and two synthetic emails, such as jordan@example.com and sam@example.com.

1. For the existing subscriber, check that the provider record exists before following the identifying link or submitting the form.
2. For the new subscriber, complete the steps that create the contact.
3. Check both the provider record and the browser's identity for each person.
4. Submit one mapped answer in each session.
5. Check each answer's destination value in your email platform.

A form can redirect before an asynchronous service finishes creating the contact. Test the new-contact path even if the existing-contact test worked. Verify an integration change covers the full check.

Is an identifying link a secure login?

No. An identifying link supplies information for personalization. It doesn't authenticate the visitor or give them access to private account information. Don't use an email query parameter or provider identifier to protect private content.