See where users drop off across web and native previews, then fix the flow with evidence.
Describe the result in chat. The agent installs the integration, wires the app, and checks the connection before you ship.
What the agent sets up
One request covers the app code, provider connection, and working proof.
Adds the PostHog SDK and configures the right client entry points for web and native.
Instruments the product events that answer your question instead of adding a generic event dump.
Sends a real validation event before it calls the connection ready.
Values stay out of the conversation
Private values stay server-side. Stored values are resolved only by server tools. The agent receives the field name, runtime, verification status, and fix-it link, never the stored value.
Public project token used by the PostHog client SDK.
Create or manage this keyA blocker comes with the next move
Contrast probes https://us.i.posthog.com from the server. It classifies a missing key, invalid key or permission, and an unreachable provider separately instead of returning a generic failure.
Each blocked result explains what failed and links to the provider screen where you can fix it. Run verification again and the project moves to Verified only after the provider accepts the probe.
Build the feedback loop with the feature
Ask for onboarding, activation, or retention tracking in the same conversation as the product work. The agent can wire the events while the intent is still clear, then verify that PostHog accepts them.