How should an agency separate client ownership, websites, Sources, validation rules, Destinations, and reporting?

Start by separating the job an agency does for itself from the job it does for clients. The agency's own prospect pipeline belongs in its sales system. Client Leads need a separate operating model in which each Business owns its website capture, Intakes, Sources, validation, Destinations, Deliveries, and reporting.

The short model: one Agency Workspace controls shared access and Google Connections. Client Groups organize related Businesses. Each Business remains the boundary for lead operations and reporting, so client data and decisions never depend on a generic agency-wide bucket.

This separation is not unique to Lucidity. Current first-party documentation from WhatConverts recommends one account per client with profiles beneath it, while CallRail Account Center groups multiple client accounts under one login. Their terms differ. The durable design principle is the same: central agency administration should not erase the client's data boundary.

The ownership hierarchy at a glance

Lucidity's current hierarchy is Workspace to Client Group to Business. Business is the operating, reporting, routing, access, and billing unit. Legacy Location scope is not a current tier. If a branch needs independent access, routing, reporting, or billing, model it as a separate Business.

Layer What it owns Use it for Do not use it for
Agency Workspace Membership scope, branding, and Google Connections Agency-wide administration and shared authorization Combining every client's Leads or reports
Client Group A named grouping of one or more Businesses Organizing related client Businesses and scoped access Replacing the Business reporting or routing boundary
Business Leads, Intakes, Destinations, Tracking Pixel, analytics, primary website, and active GA4 Property Link Operating, reporting, routing, access, and billing Sharing one client's operational records with another
Membership A user's access relationship Workspace, Client Group, or Business access Inferring access from an email domain or agency label

Every Business belongs to exactly one Client Group. A single-client agency engagement still benefits from that explicit grouping because the ownership structure remains stable when a second Business is added later. For a deeper comparison of marketing facts and operational records, see the lead tracking software guide.

Keep Intake, Source, Destination, and Delivery separate

Agencies often receive a form submission, a campaign label, and a CRM handoff in one automation. That does not make them one record. An Intake is the configured entry point that receives a submission. Source is the marketing origin. A Destination is the target that should receive a qualified Lead. A Delivery is one attempt to forward one Lead to one Destination.

Record Question it answers Required boundary
Intake How and in what format did Lucidity receive the submission? One Business
Source Which marketing origin is supported for this Lead? Evidence attached to the Lead
Validation Run Is the Lead qualified, reviewable, blocked, or in error? One Lead under Business rules
Destination Which configured target receives qualified Leads? One Business
Delivery What happened during one forwarding attempt? One Lead and one Destination
Do not silently guess Source: explicit attribution received with the Intake should win. Exact first-party Tracking Pixel evidence can fill missing fields, but ambiguous nearby activity should remain unattributed. GA4 source reports are related traffic context, not proof for a specific Lead.

If the workflow question is which Destination should receive a Lead, use a routing model, not a rep-assignment shortcut. The lead routing software guide explains why selecting a Destination and proving Delivery are separate jobs.

How to onboard one client Business

Complete this sequence for one Business before cloning settings or onboarding the next client. The order keeps ownership and access decisions ahead of live traffic.

  1. Define the Business boundary. Create or confirm the Client Group, then create the Business that owns this client's operational records. Record the primary website and the contacts responsible for approval and handoff.
  2. Assign scoped access. Keep agency operators at the Workspace or Client Group scope they need. Give client users Business access unless broader access is intentional.
  3. Configure Intake and Source handling. Create the Business Intake, document its transport and format, and preserve Source as a distinct field rather than naming the Intake after a campaign.
  4. Set the validation gate. Configure Business rules for contactability and the explicit Validation Outcomes: qualified, review, blocked, and error. Do not claim source-specific rule overrides unless they are actually configured and supported.
  5. Activate approved form capture. Install the Business Tracking Pixel and select only safe forms. Never capture password, payment, Social Security number, or bank forms.
  6. Configure Destinations and test Delivery. Enable only the intended Destinations. Submit a synthetic, non-customer test through the real form and confirm one Lead plus the expected successful Delivery evidence.
  7. Link GA4 traffic context when needed. A Workspace admin owns the Google Connection; the Business owns its active GA4 Property Link. GA4 can follow first-party activation, but missing Delivery evidence should not.
  8. Verify reporting scope and freshness. Keep customer-facing Report Runs Business-scoped. Label when Lucidity facts were generated separately from the latest GA4 traffic context included.

The form-capture step should include a real-page test, not only a configuration check. Lucidity's form tracking software comparison explains the difference between detecting forms, tracking interactions, and creating a routable Lead.

Apply validation per Business

Validation should protect contactability without turning one weak field into an automatic rejection. In Lucidity, automatic Delivery waits for a Validation Run. Qualified Leads can move forward, ambiguous evidence can go to review, strong blockers can stop Delivery, and provider or infrastructure failure remains distinguishable as error.

Keep the current implementation boundary explicit. Business default validation configuration is supported. Source, campaign, and Destination-specific overrides are model-ready concepts, not a safe promise for current agency onboarding. The lead qualification software guide covers the broader choice between rules, validation evidence, and intent scoring.

Design permissions for handoff and offboarding

Access should follow the smallest stable scope. Agency operators who administer many clients may need Workspace or Client Group access. A client stakeholder who works in one Business usually does not. Review Membership whenever a person changes role, a client adds a partner, or the agency engagement ends.

Person Likely scope Review trigger
Agency platform administrator Workspace Role change or departure
Agency team for one customer family Client Group Business added or contract scope changed
Client operator Business Handoff, department change, or departure
Reporting-only stakeholder Business with only the required capability Report ownership or recipient change

Vendor labels are not portable permissions. WhatConverts documents one Account as a client or business container, and CallRail documents separate plans, products, billing, and users for accounts inside Account Center. Treat those as examples of their current models, verified August 7, 2026, not as a universal mapping to Lucidity Membership.

Report at the Business grain

An agency can use rollups to monitor its portfolio, but a customer-facing report should still name the Business, Report Period, metric definitions, and Data Freshness. Lucidity facts answer how many Leads were received, how validation resolved, and what happened to Deliveries. GA4 supplies traffic context and may lag or revise.

Do not claim ROI unless a defined revenue or closed-won value source and attribution method exist. A report can truthfully show source, qualification, and Delivery without implying revenue that the workflow does not record. Use the marketing agency client reporting guide for the reporting layers, or compare presentation and data-source coverage in the agency reporting tools guide.

Two freshness labels: state when the Lucidity Lead and Delivery facts were generated, then state the latest GA4 reporting date included. One timestamp must not imply that both systems are equally current.

A client-safe offboarding checklist

Offboarding should stop new activity without discarding the audit trail or affecting other clients. Treat these as operational checks, since retention, exports, and credential ownership depend on the client agreement.

  1. Stop this Business's capture. Disable its Intake or provider forwarding, ignore its form-capture rules, and remove the Tracking Pixel when site activity should stop.
  2. Disable this Business's Destinations. Stop new Delivery attempts before changing connector credentials or ownership.
  3. Remove Business reporting recipients. Turn off subscriptions or recipients that should not receive another report.
  4. Remove the GA4 Property Link. Do not disable a shared Workspace Google Connection while another Business still depends on it.
  5. Revoke or remap Membership. Verify both browser and API access. Do not broaden legacy scoped access during migration.
  6. Preserve agreed audit history. Retain or export Leads, Validation Runs, Deliveries, and Report Runs according to the client's policy. Do not promise deletion or archival without a verified product workflow.
Avoid the workspace-wide switch: Routing Pause applies to the entire Workspace. It continues receiving and validating Leads while stopping Deliveries, so it is not a safe way to offboard one client Business.

The agency operating-model scorecard

Before the client goes live, answer each statement with yes and attach the evidence. A missing answer is an onboarding task, not a reporting footnote.

  • Every Business belongs to the intended Client Group.
  • Membership grants only the access each agency or client user needs.
  • The Intake and marketing Source are named and stored separately.
  • Only approved forms are captured by the Business Tracking Pixel.
  • Validation Outcomes are explicit before automatic Delivery.
  • Each enabled Destination is intentional and has a verified test Delivery.
  • The Business has the correct GA4 Property Link when traffic context is in scope.
  • Reports state Business scope, Report Period, denominators, and both freshness states.
  • The offboarding owner knows how to stop capture without affecting another Business.

Map one client workflow before scaling the agency

See how Lucidity separates each Business's forms, validation, Destinations, Delivery evidence, permissions, and reporting inside one Agency Workspace.

Request a multi-client workflow demo