Product docs
Understand what each Deplio surface does before you wire up more tracking.
These docs explain where each feature lives, what it is for, and how to get from basic pageviews to custom events, identity, reporting, sharing, and billing without guessing.
Fast setup
Privacy-friendly analytics
Workspace billing
AI-assisted summaries
Rollout guide
What a clean first rollout usually looks like
The first install should be simple and boring. Reliable analytics starts with a narrow rollout and one verified project before deeper customization.
1
Create the workspace that owns billing, projects, and future operators.
2
Create the first project with the correct domain and timezone.
3
Install the default tracking script before adding custom events or complex sharing rules.
4
Verify the first live hit, then move into overview, realtime, sessions, and growth reports.
Embed example
<script defer data-website-id="proj_live_01"
src="https://analytics.your-stack.com/script.js"></script>Use the onboarding script as-is for the first rollout. Add custom events only after the default install is confirmed.
Initial flow
3 steps
Workspace, project, install. The first-time path is intentionally narrow.
Core reports
15+
Overview, realtime, events, sessions, compare, funnels, journeys, retention, UTM, revenue, and more.
Billing unit
Workspace
Plans, usage, and upgrades stay at the workspace level instead of being fragmented by project.
Operator focus
Low drag
The product is optimized for teams that want signal quickly without a heavy analytics stack.
Quick start
From account creation to first verified traffic
The safest rollout is the one that gets to a real tracked visit quickly. Keep the first install close to the default path.
1
Create the workspace
Start with the team or client container that will own projects and billing.
Use a clear name that maps to a real operator group.
Add more members later if you do not need them on day one.
Keep workspace ownership clear before adding projects.
2
Create the first project
Set the domain and timezone before you think about saved reports or sharing.
Choose the domain you actually want to track.
Confirm the timezone before reports are shared externally.
Treat the first project as the production-like install.
3
Install and verify
Use the install screen as the single checklist for the first rollout.
Copy the script from onboarding.
Trigger a real page load on the tracked site.
Verify the first hit before tuning anything else.
Topic guides
Go deeper where teams usually need extra clarity
Use these guides when the team wants more than the first-project setup path.
Getting started
Go from empty workspace to verified tracking without a messy rollout.
How to create a workspace, create the first project, install the script, and verify live traffic in Deplio.
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.
Project onboarding
Make onboarding the single source of truth for install, verify, and first-live checks.
How to configure domains, install the tracker, verify the first hit, and troubleshoot rollout state inside project onboarding.
Use the real domain that will receive traffic, not a temporary preview URL.
Confirm timezone before the team starts reading day-based reports.
Keep allowed-domain logic simple during the first rollout.
Custom events and identity
Go beyond pageviews once the default install is already verified.
How to track button clicks, form completions, pricing actions, and session properties in Deplio after the base install is live.
Track signup, checkout, upgrade, demo-request, or onboarding-complete before lower-value clicks.
Prefer business-readable event names over internal implementation names.
Keep the first event list small enough that the events report stays legible.
Reporting
Read signal faster by using the right report for the right question.
How to use overview, sessions, events, compare, funnels, journeys, and boards in Deplio without getting lost in dashboard noise.
Check top pages, referrers, and countries first.
Open compare when a change needs historical context.
Treat overview as the main starting point, not the final answer.
Audiences and filters
Keep drilldowns narrow enough that the team can actually act on what it sees.
How to use segments, cohorts, and report filters to keep analysis focused without rebuilding the same view every time.
Filter by the dimension most likely to explain the movement first.
Avoid mixing many dimensions unless the comparison truly needs it.
Reset back to the broad view when the narrowed slice stops being helpful.
AI operator
Use AI as a summary layer, not as a replacement for the underlying reports.
How AI-assisted insights in Deplio help small teams interpret traffic, campaigns, and report movement more quickly.
Use AI on overview when traffic direction is unclear.
Use AI on campaign or conversion reports when multiple signals are moving.
Prefer compact insight panels over extra dashboard chrome.
Saved reports and boards
Turn recurring analysis into surfaces the team can reopen without rebuilding context.
How to turn repeat analysis into saved reports, board reviews, and shareable operating surfaces inside Deplio.
Save high-value funnel, UTM, or retention views that come up every review.
Name reports after the decision they support, not just the metric they contain.
Keep the saved library focused on live operator use, not archival clutter.
Sharing and access
Share analytics cleanly without giving every stakeholder the whole workspace.
How to use workspaces, members, public shares, and boards to keep reporting access clean in Deplio.
Use member roles for day-to-day viewers.
Use admin or owner access only where operational control is needed.
Avoid using public shares as a substitute for internal collaboration.
Billing and workspaces
Treat the workspace as the unit that pays, upgrades, and owns usage.
How workspace billing, plans, usage, project limits, checkout, and support work in Deplio.
Check usage and plan headroom before adding many new projects.
Treat billing as an operator concern, not a project-level concern.
Use the workspace screen to understand checkout and billing-cycle state.
Workflow
Organized around operator questions, not dashboard sprawl
Deplio is strongest when teams use each report to answer a clear question instead of treating every screen like a general dashboard.
Onboard once
The first setup path is intentionally step by step.
Workspace setup
Project setup
Install snippet
Verify connection
Read traffic fast
The core surface is built for day-to-day traffic checks and drilldowns.
Overview
Realtime
Sessions
Events
Review and share
Reusable reporting helps teams move from raw data to repeated reviews.
Saved reports
Boards
Shares
Stakeholder handoff
Feature map
What each part of the product does and where to find it
Use this as the shortest answer to “what is this feature for?” before opening a deeper topic guide.
Project onboarding
Set up the project, install the script, and verify the first live hit.
Project domain
Install snippet
Verify tracking
Troubleshoot rollout
Custom events and identity
Track actions beyond pageviews and attach useful properties to sessions.
window.deplio.track()
data-deplio-event
identify()
session properties
Traffic and behavior reports
Read what changed, who did what, and where conversion starts leaking.
Overview
Events
Sessions
Funnels
Growth and audience analysis
Check campaign quality, retention, cohorts, revenue, and attribution.
UTM
Retention
Revenue
Audiences
Saved reviews and shares
Package recurring analysis into reusable views and stakeholder-friendly surfaces.
Saved reports
Boards
Public shares
Access control
Workspace and billing
Manage plan, usage, members, and workspace-level ownership.
Workspace roles
Usage headroom
Checkout
Billing support
Use cases
A better fit for lean teams and active operators
Deplio works best when the team wants a practical analytics product that is quick to set up and easy to reopen every day.
Marketing sites
Useful for launches, pricing pages, lead forms, and campaign reporting.
Landing pages
Campaign traffic
Channel checks
Conversion monitoring
SaaS teams
Useful when the same team is watching activation, conversion, and growth signals.
Signup flow
Retention checks
Behavior paths
Revenue reporting
Agency workspaces
Useful when multiple projects need one operational home.
Client reporting
Shareable links
Board reviews
Team coordination
Founder-led products
Useful when one person is shipping product, campaign, and analytics decisions.
Fast setup
Clear summaries
Low maintenance
Affordable plans
FAQ
Questions teams usually ask before rollout
These answers cover the common questions that come up before the first real project goes live.
Dokumentation
Start with one project, verify tracking, then scale out.
The fastest way to evaluate Deplio is to run the first-project flow end to end and see how quickly the team gets to live data.