A loaded script is not a completed integration. Verify browser collection, server usage, account identity and payment evidence as separate steps; none requires adding GA4.
Keep public and server credentials separate
The browser snippet uses the site key supplied by your own GOD installation screen. A server write-only ingest key belongs only in the server environment. Do not copy the Grow or Die marketing site's key, put an ingest key into client JavaScript, or paste credentials into logs. Use an explicitly designated test site for synthetic checks.
Load the browser snippet once, with the site's correct allowed origin. A 403 collection response needs an origin/key investigation, not a blanket allow-all setting. Inspect the collection request's status without copying authorization headers into tickets.
Reuse one server telemetry instance
import { GrowOrDie } from "@grow-or-die/sdk";
const ingestKey = process.env.GROW_OR_DIE_KEY;
if (!ingestKey) throw new Error("Missing server ingest key");
const telemetry = new GrowOrDie({ ingestKey });
// Only after your application has verified these identities:
await telemetry.identify({
accountId: "account_example",
userId: "user_example",
visitorId: "visitor_example",
identifiers: { stripe: "cus_example" },
});Those IDs are placeholders, not records to send to production. Wrap the model client using the provider-specific OpenAI streaming recipe or Anthropic cache recipe. Attach the real opaque account context around your application's existing call. Do not manufacture a billed model call just to make a dashboard non-empty.
The acceptance checklist
- Browser: one genuine page visit reaches the intended test site; duplicate scripts do not double count.
- Server: the wrapper preserves the provider response and stream behavior.
- Usage: the final provider-reported token categories and model identity are observed; missing usage remains unknown.
- Identity: a verified account links to the intended visitor and payer; conflicting links are rejected or surfaced.
- Revenue: a verified payment source supplies the fact; an SDK event is not proof of a payment.
- Privacy: prompts, generated answers, emails and credentials are absent from analytics metadata.
- Shutdown: flush bounded telemetry at the appropriate lifecycle boundary; delivery failures are observable without hiding the application's own result.
What should appear first?
A browser visit can appear before model cost or revenue. A server cost can appear without a visitor link. This is expected partial evidence, not a reason to invent joins. First verify each input, then the relationship between them. GA4 and PostHog may enrich acquisition, but GOD's browser and server SDK are the native collection path.
Estimate the expected economics with the margin calculator while waiting for real evidence. Keep test traffic separate from production growth reports.
Why is AI cost blank after installing both SDKs?
Installation only loads the code. AI cost needs an accepted server usage event with a supported model, complete billable usage and a trusted price. Customer contribution also needs matching payer identity, revenue and reporting coverage. Check the first missing piece; reinstalling the browser snippet will not fill a missing server event.
- Browser visits, no AI usage
- In your backend, confirm the deployed application uses the wrapped client for an existing model call, the server key belongs to the intended GOD site, and a stream is consumed through its final usage. Check telemetry delivery and flush at the lifecycle boundary. Follow the OpenAI or Claude recipe; a page visit cannot validate server collection.
- Tokens present, cost unavailable
- Check the exact returned model, service tier, token categories and usage completeness. An unsupported price or interrupted stream must remain unknown. Use the model pricing rules; do not substitute zero or a cheaper model's rate.
- Cost present, customer contribution missing
- Verify the payment connection, payer-to-account link, currency and selected period. Cost may exist without a payment or visitor link. Use the identity recipe and account reconciliation example to separate missing identity from missing revenue.
- Collection returns 401 or 403
- Inspect the rejected request without exposing credentials. Check key type, website scope and, for browser collection, the allowed origin. Keep server keys out of the browser and never solve an origin error by allowing every website.
Check the website selected in GOD and the reporting period before comparing results. An accepted telemetry request is not yet proof of priced usage or a successful revenue join; no fixed arrival time is guaranteed.
What this evidence can and cannot prove
The checklist verifies individual collection boundaries, not a complete customer lifecycle, causal acquisition or audited profit. A green health endpoint alone does not prove an SDK event was accepted and linked correctly.
Primary references
After the SDK is live, measure cost and visibility.
- AI cost per user — Confirm the user denominator once usage events arrive.
- AI visibility — See whether AI finds the product after traffic is connected.
- Grow or Die pricing — Starter $20 and Growth $99 per website after a 7-day trial.