Connect website activity to product analytics
A selected analytics provider can load its browser SDK through the website’s provider system. Wildo keeps activation, public configuration and cleanup in one integration path instead of scattering vendor scripts across pages.
You choose the receiving project and the analytics policy; the provider connects the browser to it.
Example — Observe website activity in the selected project
A website uses its configured PostHog project and endpoint. The SDK receives activity according to its configured behavior, while the application remains responsible for choosing which collection is appropriate.
For engineers
Supply the browser integration’s configuration
The PostHog frontend package depends on posthog-js itself, so installing the module brings the SDK into the website’s bundling environment. Select the product-analytics provider, and configure its public project key and endpoint in wildo.saas.config.ts or an environment’s infrastructure file. The website does not author the contribution itself: an installed package’s contribution is discovered. This fragment assumes the deployment supplied publicProjectKey and apiHost:
providerConfigurations: {
posthog: {
[ExternalProvider_ExchangeProtocol_Kind.FRONTEND_SDK]: { apiKey: publicProjectKey, apiHost },
},
},
These are browser-visible settings. They are not private account-management credentials. The provider derives a CSP connection origin from apiHost; configure the actual receiving host rather than adding a guessed vendor-origin list.
Understand what initialization does
The module validates the key, imports the SDK on demand, starts it with every remotely enableable capture feature pinned off, and returns its cleanup behavior:
const { default: posthog } = await import('posthog-js');
posthog.init(apiKey, { ...(typeof apiHost === 'string' ? { api_host: apiHost } : {}), ...POSTHOG_BROWSER_PRIVACY_OPTIONS });
return {
handle: posthog,
deactivate: () => {
posthog.reset(true);
posthog.opt_out_capturing();
},
};
The shared runner isolates activation failures. The website hook activates consent-based providers only for purposes the visitor has granted, and deactivates them when that purpose is withdrawn, when the registry changes, or when a page unmounts before initialization completes. The consent decision itself comes from the website’s consent panel, not from the provider.
Keep separate analytics systems distinct
| Surface | What it does |
|---|---|
| Website PostHog SDK | Loads the selected browser analytics integration |
| Application analytics context | Tracks configured application events and evaluates value moments |
| LLM observability sink | Reports model-call usage/timing under its own content policy |
Wonder Todos supplies its PostHog host under providerConfigurations.posthog.frontend_sdk, but its source deliberately omits the project key. Use that file as a configuration pattern, not proof that live events are reaching a project. Verify the selected destination and collection behavior in the browser before describing the integration as operating.