Should we add custom events before the first rollout?

Usually no. The safest path is to get the default install live first, then add custom events where they are actually justified.

What if verify still shows no traffic?

Check that the snippet is loading on the intended domain and that the visit is happening against the configured project domain.

Getting started

This guide covers the shortest reliable path to first data so teams do not over-configure the product before tracking is even live.

Workspace first

Project install flow

Verify first hit

Low setup friction

Documentation

How to create a workspace, create the first project, install the script, and verify live traffic in Deplio.

Primary outcome

First verified hit

The setup is only done when the first real visit is visible in the app.

Recommended scope

One project first

Start with one real domain before copying settings across many projects.

Best practice

Default snippet

Keep the first install close to the default tracking script.

Start with the workspace

Use the workspace as the operational home for billing, projects, and team ownership.

Choose a clear workspace name that maps to a real team or client.

Avoid adding complexity before the first project exists.

Keep workspace ownership clear before inviting more operators.

Create the first project

Set the basics before you touch saved reports or growth analysis.

Use the real domain you want to monitor.

Confirm the timezone before external reporting starts.

Treat the first project as the production-like rollout.

Install and verify

Use the setup screen as the source of truth for the first install.

Copy the script from onboarding.

Trigger a real page load on the target site.

Verify the hit before tuning filters, shares, or report libraries.

__PROTÉGÉ_0__

How to create a workspace, create the first project, install the script, and verify live traffic in Deplio.