Skip to main content
Decide what success means before adding analytics. A visit, sign-in, saved record, and paid purchase represent different steps in a user’s journey.

​
Choose a short event list

For a request portal, useful events might be: Use clear definitions. Do not record a successful save just because the user clicked Submit. Count completion after the server confirms the write, and avoid sending the same event again on refresh.

​
Implement a provider deliberately

Ask Fabricate to add the analytics provider you choose using that provider’s current documentation. Supply only configuration intended for browser use. Keep private provider keys in server-side environment secrets. Generated integration code still needs verification. Check the browser request, the provider’s received event, and the correct project or property. A script loading is not evidence that events are arriving.

​
Test identity and attribution

Use a test journey from a tagged link through sign-in and the main action. Confirm the original source survives login. Keep test traffic separate when the provider supports it and compare equivalent date ranges and time zones. For payments, use a verified payment-provider event and the actual amount and currency. A checkout opening or redirecting to a success page is not proof of paid revenue.

​
Respect user data

Collect only fields needed for the decision you are making. Do not send passwords, API keys, message contents, or private customer records as event properties. Configure consent and retention for your audience and use case. Start with one useful funnel and review its failures before adding more dashboards. See Test your app for end-to-end validation.