Connecting Integrations

Kenzsys becomes useful as soon as data starts flowing in. This page walks you through connecting the four core integrations — CallRail, Google Business Profile, Google Ads, and Clio — in roughly 15 minutes total.

Screenshot coming soon

Before you start

You'll need admin access (or the equivalent) in each external account you're connecting. If your firm uses a marketing agency, ask them which login owns the Google Ads and GBP accounts — that's the account you'll need to authenticate with.

Where to find connections

All integration setup lives under Settings → Integrations. Each provider has its own card showing connection status, last sync time, and a button to connect or reconnect. Once connected, the card flips from "Not connected" to a green "Connected" state and shows the most recent sync.

Empty state by design: Until you connect an integration, the related dashboard widgets show an "Not connected — connect to start syncing" message rather than placeholder numbers. We never show fake data.

1. CallRail

CallRail provides call tracking — the source of most marketing-attributed leads for a typical firm. Connecting it is a webhook setup (no OAuth). See CallRail integration for the step-by-step.

2. Google Business Profile

GBP is an OAuth connection. Click Connect, sign in with the Google account that manages your firm's GBP listing, and grant Kenzsys read-only access. Once connected, profile views, search-query data, and direction requests start flowing within an hour. See Google Business Profile for what data syncs.

3. Google Ads

Google Ads is also OAuth. You'll authenticate with the Google account that has access to your Ads customer ID, then pick which Ads account to link. Spend, clicks, and conversion data sync nightly. See Google Ads.

4. Clio

Clio Manage and Clio Grow both connect via OAuth. Once linked, Kenzsys can follow leads through to matter creation and case status — the data we use to attribute retained clients back to ad spend. See Clio.

Reconnecting or disconnecting

OAuth tokens can expire (especially if someone revokes access in Google or Clio). If a card shows "Reconnect required," click it and re-authenticate — Kenzsys will pick up where it left off without losing any historical data. Disconnecting a provider stops new syncs but keeps the data already pulled in your reports.