What Webhook Fields Are Available in the Visual Visitor Payload?

What Webhook Fields Are Available in the Visual Visitor Payload?

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

 

  1.  email - Identified professional or personal email address.
  2.   first_name - Visitor's first name.
  3.   last_name - Visitor's last name.
  4.   job_title - Visitor's job title (B2B / +Employee accounts).
  5.  job_level - Seniority level (e.g., Director, Manager, C-Suite).
  6.  company_name - Visitor's employer company name.
  7.   company_domain - Visitor's employer's website domain.
  8. phone - Direct phone number where available


 Session and behavioral fields

 

  1.  page_url - The specific page URL the visitor was on when identified.
  2.   referral_source - How the visitor arrived at your site (e.g., Google, direct, campaign UTM).
  3.  utm_source / utm_medium / utm_campaign - UTM attribution data if the visitor arrived via a tagged URL.
  4.   session_date - Timestamp of the identification event.

 

 Company-level fields (also available on +Employee accounts)

 

  1. company_city / company_state / company_zip
  2.  company_industry 
  3.  company_employee_count
  4.  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.

InfoFor the full payload schema and field definitions, click here.

    • Related Articles

    • Available Webhook Fields

      What fields are available when setting up a webhook? The webhook integration allows you to connect Visual Visitor with other systems. When creating your webhook, the following fields are available for integration. These fields can also serve as ...

    • Why Is My Go High Level Webhook Receiving Empty or Mismatched Fields?

      If your Go High Level (GHL) webhook is receiving data from Visual Visitor but certain fields are blank or missing, the most common cause is that your workflow field mappings do not match the webhook payload being sent by your Visual Visitor account. ...

    • +Person Web ID Webhook Integration

      Integrate our data with any system you like! Webhook Notifications (per user, available to all users) Data Format JSON - (JavaScript Object Notation) is a lightweight data-interchange format. It is easy for humans to read and write. It is easy for ...

    • How to Set Up a Webhook Integration Between Visual Visitor and Go High Level

      You can push your visitor and lead data directly into Go High Level (GHL) using a webhook. This allows new identified visitors to automatically become contacts in your GHL CRM or sub-account pipeline. Step 1 - Get your GHL webhook URL 1. In Go High ...

    • What is an API? A Simple yet Comprehensive Guide to API Types, Benefits, and Best Practices

      Understanding APIs What is an API? An API (Application Programming Interface) is a set of rules and protocols that allows different software applications to communicate with each other. APIs enable developers to access and integrate functionalities ...