When
Visual Visitor identifies a visitor and sends a webhook notification to your
configured endpoint, the payload contains a JSON object with the visitor's
identification data. Below is an overview of the key fields available in the
current (+Employee / +Person) webhook payload.
Core identification fields
- email - Identified professional or personal email address.
- first_name - Visitor's first name.
- last_name - Visitor's last name.
- job_title - Visitor's job title (B2B / +Employee accounts).
- job_level - Seniority level (e.g., Director, Manager, C-Suite).
- company_name - Visitor's employer company name.
- company_domain - Visitor's employer's website domain.
- phone - Direct phone number where available
Session and behavioral fields
- page_url - The specific page URL the visitor was on when identified.
- referral_source - How the visitor arrived at your site (e.g., Google, direct, campaign UTM).
- utm_source
/ utm_medium / utm_campaign - UTM attribution data if the visitor
arrived via a tagged URL.
- session_date - Timestamp of the identification event.
Company-level fields (also available on
+Employee accounts)
- company_city / company_state /
company_zip
- company_industry
- company_employee_count
- company_revenue
Legacy accounts:
Older Visual Visitor accounts using the legacy script may receive a payload
that includes only company-level fields (company name, domain, city, state)
without person-level fields. Contact Visual Visitor Support if you need to
confirm which payload format your account uses.
For
the full payload schema and field definitions, click here.