Browser tracking · implemented, consent required
The JavaScript tracker supports explicit events, declarative click goals, bounded goal properties and opt-in pageviews for mapped history/hash routes. It creates no identifier or tracking request before permission. GPC and withdrawal stop collection.
An installation event, verified payment and attributed payment are three different checks. A loaded script does not prove any of the other two. Real framework/browser acceptance is still required for the site you install on.
Stripe customer analytics · provider-dependent
The application can store encrypted, account/mode-bound restricted credentials and verify raw signed webhooks. Payment Intents are reconciled against authoritative provider state. Selected-product scope uses Checkout or invoice evidence; refunds reuse the verified parent payment’s scope.
No Stripe connection is configured by browsing this preview. Real restricted-key permissions, webhook delivery, test/live mode and the approved product catalog must be checked before collection. Manual credentials are not Stripe Connect OAuth.
Google Search Console · provider-dependent
An authorized import/reporting adapter exists for selected property data. Missing authorization means unavailable, not zero search traffic. Search query observations are not exact person-level payment attribution.
Do not infer a live Google grant, keyword revenue guarantee or complete historical coverage from the existence of the reporting module.
Resend · transactional email, separate setup
Verification, password-reset and viewer invitations use a configured transactional transport. Provider acceptance is not confirmed delivery. Sender verification, credentials and hosted acceptance remain prerequisites.
Automated notification delivery has its own opt-in. An owner-only non-billable launch can use email without enabling paid SaaS billing or public registration.
Developer and assistant access
Scoped read tokens and documented project APIs are implemented. Reports-only access excludes visitor-level detail; tokens can be revoked. The public setup prompt explains the actual available surfaces and does not grant access.
Remote MCP/OAuth remains unmounted pending runtime and real-client acceptance. There is no working public CLI, mobile app, native SDK package or one-click connection to every publishing platform.
Other providers and platforms
Paddle, Lemon Squeezy, Polar, advertising-cost connectors, GitHub analytics and social-mention integrations are not available. Use the generic installation guide only where you control the site code and its consent mechanism; a generic script recipe is not a certified platform integration.