Integrations

Connect GrowDeck to your analytics and communication tools.

Last updated: May 2025

GA4 AnalyticsPRO

Overview

Connect Google Analytics 4 to track the traffic impact of GrowDeck-generated pages. After connecting, the GA4 tab in each site shows sessions, users, and engagement metrics.

How to connect

  1. Navigate to Dashboard → Integrations
  2. Click “Connect GA4”
  3. Authenticate with your Google account
  4. Select your GA4 property
  5. GrowDeck stores the property ID and fetches data on demand

What’s tracked

  • Sessions from GrowDeck-generated pages
  • Organic search sessions for the whole site
  • Top landing pages from search
  • Keyword-driven traffic trends

Data freshness

GA4 data is fetched when you open the GA4 tab. Data has a 24–48 hour delay from Google’s side — this is a GA4 limitation.

Data delay
GA4 data has a 24–48 hour processing delay on Google's side. Real-time data is not available.

Slack DigestPRO

Overview

Receive a weekly Slack summary of search performance, new pages, and opportunities.

How to connect

  1. Navigate to Dashboard → Integrations
  2. Click “Connect Slack”
  3. Authorize GrowDeck to post to a channel
  4. Select the channel for digests

What’s in the digest

  • New pages deployed this week
  • Keyword ranking changes
  • Top opportunities waiting to be generated
  • Content decay alerts (pages losing traffic)

Frequency

Weekly, sent every Monday morning. Configurable in site settings.

The Slack digest is sent every Monday. If you miss a week, you can manually trigger a digest from Dashboard → Integrations.

GitHub Audit

Overview

Connect a GitHub repository to audit your codebase alongside your SEO strategy. The GitHub tab shows which features are documented in your site’s content and which aren’t.

How to connect

  1. Navigate to Dashboard → Integrations
  2. Click “Connect GitHub”
  3. Authenticate with GitHub (OAuth)
  4. Select the repository to audit

What the audit checks

  • Public-facing features mentioned in README and code
  • Whether each feature has a corresponding landing page
  • Docs coverage gaps

Use case

If your product has 20 features and only 8 have dedicated pages, the GitHub audit surfaces the missing 12 as content opportunities.