Project onboarding
Make onboarding the single source of truth for install, verify, and first-live checks.
The onboarding surface works best when the team uses it as a guided rollout checklist instead of scattering setup across multiple pages.
Install flow
Domain checks
Verify state
Rollout troubleshooting
ドキュメント
How to configure domains, install the tracker, verify the first hit, and troubleshoot rollout state inside project onboarding.
Primary job
Get one clean live install
Do not widen the rollout until the first project is clearly verified.
Where to look
Setup pulse
The top of onboarding should tell the operator what is done and what is next.
Failure pattern
Domain mismatch
Most first-install confusion comes from the script loading on the wrong domain or environment.
1
Set the real project context first
Domain, timezone, and allowed-domain expectations should be correct before you install anything.
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.
2
Install the default tracker before adding extras
The cleanest rollout is the default script plus one real visit, not a fully customized instrumentation pass.
Copy the tracker snippet directly from onboarding.
Install it on one production-like surface first.
Hold custom events until the default pageview flow is visible.
3
Verify with a real visit and real checks
Use verify as an operator checklist, not just a button press inside the product.
Open the tracked site yourself to create a fresh real visit.
Check that the request is sent from the intended domain and environment.
If verify stalls, inspect domain mismatch, cached pages, or disabled local tracking.
__保護中_0__
How to configure domains, install the tracker, verify the first hit, and troubleshoot rollout state inside project onboarding.