PostHog IS installed on growreach.app — the JS snippet is live in the page HTML
Project API key:phc_N37HpqTgSvLQFxmaU4YAdic0XQMcmYjd6v2SggvNL3R
Region: EU (https://eu.i.posthog.com)
Autocapture: ENABLED (default — not explicitly disabled). PostHog is auto-tracking all pageviews, clicks, form submissions, and session recordings by default.
Persistence: Cookie-based with cross-subdomain support
Defaults date: 2026-01-30 (data likely starts from this date)
What’s NOT Working
MCP OAuth NOT authenticated — hermes -p cro mcp login posthog needs to be run interactively (requires browser). Error: “non-interactive environment and no cached tokens found.”
No custom events tracked — PostHog is running with autocapture only. No explicit posthog.capture() calls for signup, trial_start, email_capture, or other conversion events.
PostHog NOT installed on dashboard.growreach.app — the dashboard is a React SPA on CloudFront/S3. It has BOT9 chat widget but NO PostHog snippet. This means once a user clicks “Start 14-Day Free Trial” and goes to the dashboard, PostHog loses them.
2. Landing Page Technical Stack
Component
Technology
CMS
WordPress (6.9.4) on Hostinger (LiteSpeed, PHP 8.3)
Theme
Custom: grow-reach-wp-theme
Dashboard app
React SPA on CloudFront/S3
Analytics
PostHog (EU), Google Analytics 4 (GT-KVFDZ22F), GTM (GTM-MQDVLQ6P)
Popup/Lead capture
Hustle (WordPress popup plugin) — module ID 2
Chat widget
BOT9 (on dashboard only)
SEO plugin
Rank Math
3. Landing Page Conversion Elements
CTAs Found on Homepage
CTA Text
Location
Handler
Destination
Start 14-Day Free Trial
Header (desktop + mobile)
handleStartTrial()
http://dashboard.growreach.app/start (opens new tab)
Start 14-Day Free Trial
Hero section
handleStartTrial()
Same as above
Start 14-Day Free Trial
Mid-page (large)
handleStartTrial()
Same
Start 14-Day Free Trial
Pricing CTA section (white btn)
handleStartTrial()
Same
Watch Demo
Hero section
handleWatchDemo()
http://dashboard.growreach.app/start (SAME URL — not a demo!)
Schedule a Demo
CTA section
handleWatchDemo()
Same URL (also goes to signup, not demo)
Sign In
Header (desktop + mobile)
handleSignIn()
http://dashboard.growreach.app/start (goes to START page, not login!)
Sign In
Header (desktop)
link href
https://dashboard.growreach.app/login
Critical CTA Issues Found
ALL CTA buttons go to the SAME URL (dashboard.growreach.app/start) — “Watch Demo”, “Schedule a Demo”, “Sign In”, and “Start Free Trial” all point to the signup page. This is deceptive and likely causes confusion/bounce.
HTTP not HTTPS — the JS handlers use http://dashboard.growreach.app/start instead of https://. Browsers may warn or redirect, causing drop-off.
No demo video or content — “Watch Demo” doesn’t show a demo, it goes to signup. Users who wanted to see a demo will likely bounce.
Sign In button inconsistency — handleSignIn() goes to /start (signup), but the <a href> link goes to /login. Two different destinations for “Sign In”.
Email Capture / Lead Capture
Hustle popup installed (module ID 2) with exit-intent trigger, 20% scroll trigger, and time-based trigger
Popup has an email opt-in form
BUT: No email capture visible in the main page flow — only via the popup
No inline email capture form in the hero, features, or pricing sections
Page Structure (from nav anchors)
Hero section (with badge: “Cold Outreach Is Dead”)
Features (#features) — tabbed: Auto-Commenting, Creator Targeting, Keyword Targeting, Analytics & Insights, Boost Post
No email capture in main flow — the only email capture is a popup that may be blocked by adblockers or dismissed. Visitors who aren’t ready to start a trial leave with zero data captured.
Deceptive CTAs — “Watch Demo” and “Schedule a Demo” both go to signup, not a demo. This breaks trust.
HTTP → HTTPS mismatch — CTA handlers use http:// which may cause redirect delays or browser warnings.
No PostHog on dashboard — once a user clicks to start trial, PostHog loses tracking. We can’t measure signup funnel completion or drop-off at the dashboard.
No custom event tracking — only autocapture. We don’t know which CTA was clicked, which section was viewed, or where users drop off.
Medium Priority
Sign In button confusion — two different handlers/destinations for the same action.
No social proof on hero — no testimonials, ratings, user count, or trust badges visible above the fold.
No clear value proposition hierarchy — the badge says “Cold Outreach Is Dead” but the headline and subheadline weren’t captured in our scan (need visual inspection).
Pricing is a separate page (/pricing-page) — sending users to a different page may cause drop-off vs having pricing inline.
Low Priority
12 comparison pages — significant SEO content but may dilute conversion focus.
Free Tools section — good for SEO/traffic but may distract from the primary conversion goal.
5. What I Need From Rahul to Get Fully Operational
Critical (Blocking CRO Work)
#
Item
Why I Need It
How to Provide
1
Complete PostHog OAuth
Need to query analytics, run HogQL, see funnel data, session replays
Run hermes -p cro mcp login posthog interactively in terminal (opens browser for PostHog login)
2
Website access for changes
Need to edit the WordPress landing page (theme files, CTA handlers, add email capture)
SSH/FTP to Hostinger, or WordPress admin credentials, or git repo for the theme
3
Confirm PostHog project ID & org ID
To verify I’m connecting to the right project
Login to PostHog → Project Settings → copy Project ID and Org ID
Fix CTA handlers — change http:// to https://, make “Watch Demo” actually show a demo (video embed or Loom link), make “Sign In” go to /login consistently
Add inline email capture in the hero or below the fold — “Get our LinkedIn engagement playbook” or “Join 500+ founders” as a lead magnet
Add custom PostHog events — posthog.capture('cta_click', {cta_name: 'hero_trial', destination: '/start'}) on each CTA button
Install PostHog on dashboard — track the full signup funnel from landing → dashboard → trial activation
Set up a conversion funnel in PostHog — page_view → cta_click → dashboard_landed → signup_form_started → signup_complete
Run an A/B test on the hero headline and CTA copy once baseline data is available
7. Action Required From Rahul
Run this command in a terminal to authorize PostHog MCP access:
hermes -p cro mcp login posthog
This will open a browser window for you to log into PostHog and authorize the MCP connection. Once complete, I’ll be able to:
Query your analytics data directly
Run HogQL queries for funnel analysis
Access session replays
Manage experiments/feature flags
Triage errors
Until this is done, I’m flying blind — I can see the page structure but not the actual user behavior data.