Skip to main content

​
Start with a standard client rollout

Use the same basic rollout shape each time:
  1. Define the client’s ICP and what traffic should count as valuable.
  2. Install the right pixel on the right domain.
  3. Suppress known noise early.
  4. Save one focused view or segment.
  5. Route the data into one agreed destination.
  6. Review the output on a regular cadence.

​
Decide what you are actually delivering

Best when the client wants visibility first and is not ready for heavy workflow changes.
Best when the client has a team that can act on named visitors quickly.
Best when the client wants better audience quality and campaign follow-up.
Best when you already own the client’s routing and downstream systems.

​
Good client workflows

  • a weekly identified visitor report
  • a Slack feed for high-intent traffic
  • CRM routing for qualified visitors
  • a filtered export for client outreach
  • a paid-traffic review workflow for agencies running ads
  • a branded client experience when included in your agency agreement

​
Confirm account separation and ownership

Use an explicit organization and API-key ownership model for each client. Pixel names, attribution labels, and saved views organize data; they are not substitutes for access controls. Before rollout, confirm who can log in, which data they can see, who sees billing, who owns each integration account, and who handles offboarding. Verify these controls with the intended client role before sharing access.

​
What to standardize internally

  • naming conventions for pixels and segments
  • who approves suppression rules
  • which destination is primary
  • what the client sees in reports
  • what counts as a successful month or trial

​
What to avoid

  • building a different operating model for every client
  • routing raw traffic without qualification
  • promising a workflow that the client will not actually use

​
Good companion guides