Troubleshoot anonymous visitors and missing contact updates

You can find where a contact update stopped by checking what RightMessage knows about the browser, which answer it saved, and where that answer should go. Start with the symptom that matches what you're seeing.

Responses are anonymous even though I've connected my email platform

Follow the visitor's steps with a fictional test contact in a clean browser session. Open Visitor in the RightMessage debugger. Check that the visitor identified themselves and that your email platform found the contact you expected.

Enlarge

Visitor debugger overview showing anonymous identity, browser and location details, visit counts, and the Full profile linkOriginalOriginal

Connecting your email platform doesn't identify every browser. The visitor needs to identify themselves through a configured Email question, form, or email link.

Anonymous responses aren't necessarily a problem. Visitors can answer questions and qualify for behavior-based personalization without giving you an email address.

The contact exists in my email platform, but the browser is anonymous

Check the actual link or form the visitor used. Follow your provider's integration guide, or use a supported form identification method.

A contact record in your email platform doesn't identify a browser by itself. An email link may be missing its identifying parameter. For website forms, the Popup's After a form is submitted trigger may need configuring, or the form may not expose a supported submission event.

For ActiveCampaign, rm_ac must contain the contact identifier. Existing tags or a generic utm_source value don't identify the browser.

For a form redirect, check the URL the visitor actually reaches, not just the redirect template. A literal merge tag or the wrong parameter won't identify the intended contact.

Existing contacts work, but new signups don't

Check that your email platform has accepted the new contact. Then check that the form's contact-creation action has the destination and permissions it needs. Test the whole signup again, not just the thank-you-page URL.

The form may redirect before an external service finishes creating the contact. A lookup can find an existing contact without creating a new one.

RightMessage retries lookups a limited number of times. An external automation can still take too long. See form redirect identification and how to verify an integration change.

An email answer was saved, but the visitor wasn't identified

Open the question's settings and check Identify the visitor, the consent settings, the contact action, and any required provider destination. See identifying contacts with an email question.

An Email question can save an answer without identifying the visitor. Identify the visitor may be off, or the visitor may have left a displayed consent checkbox unchecked.

With Identify the visitor off, a mapped Email answer can still update an existing contact. On an identifying Email question, leaving a displayed consent checkbox unchecked blocks both identification and that answer's sync.

Don't enable Email Watcher to bypass these choices. It excludes RightMessage question inputs so the question's own identity and consent settings apply.

An answer appears in RightMessage but not in my email platform

1. Check whether you tested the draft or published configuration.
2. Check the browser's actual contact identity.
3. Check the recorded answer or segment.
4. Open the question's sync settings and check its destination field, tag, or list.
5. Make sure the destination accepts the mapped value and the integration has permission to update it.
6. Submit a fresh answer as your test contact outside the debugger, which blocks external writes.
7. Open that contact in your email platform and inspect the destination.

RightMessage can capture an answer even when the browser is anonymous, the mapping is missing or incompatible, or the provider rejects the update. The field or tag on the destination contact tells you whether the update arrived. See mapping answers to contact fields and tags.

An older answer doesn't overwrite a changed CRM field

Decide which value is correct before changing anything. If the visitor is providing a new answer, test a new submission rather than repeatedly reloading the page.

When RightMessage syncs saved input answers in the background, it protects populated provider fields from stale answers. A returning browser can still have an older value saved locally.

The profile says Contact not found

Check the exact email or provider ID in the connected account. Make sure you've connected the intended account, audience, or workspace. Then try the identification steps again with a known test contact.

Contact not found means the provider lookup didn't return a contact for that identity. An unavailable integration or an empty custom field is a different issue. Viewing provider data in a visitor profile requires Pro.

The profile says Unable to load integration data

Choose Retry. If it still fails, check the connection and its permissions. Once the provider's Data tab has loaded, Sync now refreshes the data read from your provider. It doesn't resend all historical responses.

Unable to load integration data means the request failed, not that the contact or its fields are empty.

No integration data, No custom fields, and No matching fields are separate messages. Clear any field filter before deciding that no custom fields exist. See the profile data reference.

One device is known, but another is anonymous

Complete an identifying action on the affected device, such as clicking a correctly configured email link. Then check that browser's identity.

RightMessage remembers identity in a browser. A new device, private window, or browser with cleared storage doesn't automatically inherit it. A successful desktop test doesn't tell you whether the phone was identified.

My test browser shows the wrong person

Use a separate clean browser session for each fictional test contact. If you use Email Watcher, check whether it fits the forms on your site.

The browser may remember an earlier identity. Email Watcher can also infer identity from an address entered for someone else. The generic email query parameter isn't a reliable way to switch identities when a subscriber identifier is already saved.

I still need help

Record the project, page, approximate time and timezone, browser, and whether you tested a draft or published version. Include the identification method, question, intended destination, and exact error. Say whether the contact exists in your provider.

Use fictional test contacts when sharing steps to reproduce the problem. Never include API keys, debugger authorization tokens, or private identifying URLs in a public report. For a browser-specific problem, check both that browser's identity and its contact update before calling it fixed.