Collecting Visitor Information
Configure how and when to collect visitor names and emails.
FOMOchat can collect visitor contact information to generate leads.
Collection Modes
None
- Visitors can chat without providing info
- Maximum engagement, minimum friction
- Best for awareness-focused widgets
Ask (Optional)
- Prompt visitors for info but don't require it
- Good balance of leads and engagement
- Visitors can skip and still participate
Require
- Visitors must provide info to join the chat
- Maximum lead capture
- May reduce total engagement
💡 Key Insight: "Ask" mode typically generates more quality leads than "Require" because engaged visitors provide info willingly, while forced collection creates friction.
What to Collect
Name Only
- Personalizes the experience
- Low friction
- Good for casual engagement
Email Only
- Enables follow-up
- Moderate friction
- Best for lead generation
Name and Email
- Full contact info
- Higher friction
- Best for sales-focused widgets
When Collection Happens
Visitors are prompted to provide info when they:
- Click to open the chat
- Try to send their first message
- After viewing for a set time (configurable)
💡 Pro Tip: Collect email only if you'll actually follow up. Asking for info you won't use just adds friction without benefit.
Configuring Collection
- Open your FOMOchat editor
- Find the Visitor Settings section
- Choose collection mode for Name and Email
- Save changes
Viewing Collected Information
Visitor data appears in your Analytics:
- Go to Analytics for your FOMOchat
- View the Visitors section
- Click any visitor to see details
- Export data if needed
Privacy Considerations
- Display a privacy notice in your widget
- Link to your privacy policy
- Comply with GDPR/CCPA if applicable
- Only collect what you need
Best Practices
- Match friction to value — High-value offers can require more info
- Be transparent — Tell visitors why you need their info
- Follow up promptly — Engage leads while they're warm
- Test both modes — See what works for your audience
Was this article helpful?
Your feedback helps us improve our documentation.