ClientView
  • 👋Welcome to ClientView
  • 🎙️Our Story
  • ⚡Book Setup Call
  • Getting Started
    • Tracking Workflow
    • Boost Client Performance
    • Configure Agency
      • Invite Team
      • Create Offers
      • Categories + Alerts
    • Start Tracking
      • How it works
      • Connect GoHighLevel
        • How to use CRM sources
      • Setup UTM Tracking
        • Static Sources (Hard code)
      • Connect Ad Platforms
      • Adding Clients
  • Features
    • Filtering
    • Client Notes
    • Tasks & Notifications
    • Offers
    • Categories
    • Active Status
  • Billing
    • Pricing Tiers
  • Support
    • Support
  • Company
    • Founding Team
    • 🤝Partnerships
Powered by GitBook
On this page
  • How do we gather data from GoHighLevel?
  • Setting up the webhooks
  • Create Workflows
  1. Getting Started
  2. Start Tracking

Connect GoHighLevel

GoHighLevel Only

PreviousHow it worksNextHow to use CRM sources

Last updated 11 months ago

CRM sources are a collection of all 5 event hooks for a single client. You do not need to have all 5 hooks setup. For example, if you wish you can only setup the leads hook to know when Facebook to GHL integration breaks.

How do we gather data from GoHighLevel?

ClientView uses 5 unique WebHooks (Not 5 unique hooks per client). This is because with just 5 hooks ClientView is able to receive the events and categorize them by client using the name and account ID sent with it.

This means you only have to setup once and push the snapshot update, then all of your clients CRM data will become trackable inside of ClientView.

These are called CRM Datasources:

CRM sources can be found in the Webhooks tab.

After setting up WebHooks - An event or test event will need to be fired in the GHL sub-account before the sub-account becomes available as a data source.

CRM sources are assigned to clients to unify their Advertising results with CRM results

Setting up the webhooks

Create Workflows

Below are examples on how you can set these up:

  1. Leads Workflow

Trigger can be from "Facebook form submit", a tag or pipeline step.

Action: Webhook (Post) - Paste the leads webhook URL


  1. Booked Call Workflow

Trigger can be from appointment created on individual calendars , a tag or pipeline step.

Action: Webhook (Post) - Paste the booked call webhook URL


  1. Show Workflow

Trigger can be from pipeline step or tag or "Call answered" trigger

Action: Webhook (Post) - Paste the show webhook URL


  1. No-Show Workflow

Trigger can be from pipeline step or tag or "Call Failed / No Pickup" trigger

Action: Webhook (Post) - Paste the no-show webhook URL


  1. Sold Workflow

Trigger can be from pipeline step or tag

Action: Webhook (Post) - Paste the sale webhook URL

The sale value of a contact must be assigned before moving contact to "Sold" in order to track sales value.

CRM sources will start to populate in your ClientView account. CRM sources will be labeled after the GHL sub-account that sent them. Assign the corresponding CRM source to Clients when adding.

Navigate to here you will see your available hooks.

Once these triggers/workflows are installed in your client snapshot,

Webhooks
push the update to all clients
Page cover image