Skip to main content

​
Analytics & Tracking for Intelliprint Docs

This page outlines how to instrument the Intelliprint documentation site so you can measure:
  • How developers discover and use the docs
  • Which guides and use cases drive sign-ups and sales
  • Where to focus future SEO and content investments
Note: Some configuration happens in the Mintlify docs.json file, and some in external tools (Google Analytics, Search Console, etc.).

​
1. Google Analytics 4 (GA4)

Intelliprint docs are already wired with a GA4 placeholder ID in docs.json: 
"analytics": {
  "googleAnalytics": {
    "id": "G-XXXXXXXXXX"
  }
}

​
1.1 Create a GA4 Property

  1. Go to https://analytics.google.com.
  2. Create a new GA4 property for docs.intelliprint.net.
  3. Copy the measurement ID (looks like G-XXXXXXX).

​
1.2 Wire GA4 into the Docs

  1. Replace G-XXXXXXXXXX in docs.json with your real GA4 measurement ID.
  2. Deploy the updated docs (Mintlify will inject the GA4 tag automatically).
Once deployed, you should see page views from your own visits in the GA4 real-time view.

​
2. Google Search Console

Search Console gives you query-level insight into how the docs perform in organic search.

​
2.1 Verify the Property

  1. Go to https://search.google.com/search-console.
  2. Add a domain property for intelliprint.net (recommended) or a URL-prefix property for https://docs.intelliprint.net.
  3. Verify ownership via DNS or your existing site verification method.

​
2.2 Filter for Docs Traffic

Once data is flowing:
  • Use the Performance report and filter by page containing /docs or your docs host.
  • Track queries like:
    • “hybrid mail api”
    • “uk postal mail api”
    • “send letters via api”
    • “digital mailroom”
Use this data to refine titles, descriptions, and new use-case pages.

​
3. Funnel & Conversion Tracking

To connect docs usage to revenue, define simple funnels:
  • Landing on docs → signup / dashboard visit
  • Landing on use-case page → contact / pricing

​
3.1 Identify Key Conversion Events

Examples:
  • docs_to_dashboard_click – when a user clicks the Dashboard CTA from docs.
  • docs_signup_complete – when a new account is created (with referrer containing docs).
  • docs_contact_support – mailto or form submission from docs.
These events will typically be tracked in your main app or marketing site, but can be analysed with:
  • GA4 event reports
  • UTM parameters if you send traffic between properties
In GA4, build explorations or dashboards for:
  • Top landing pages on docs by organic traffic.
  • Path analysis from docs pages to signup or dashboard.
  • Conversions by landing page – which guides/use cases generate the most downstream sign-ups.

​
4. Using the Data for SEO & Docs Improvements

On a regular cadence (e.g. monthly or quarterly):
  • Review Search Console queries and ensure the most common ones have strong landing pages.
  • Identify guides with high impressions but low CTR and experiment with better titles/meta descriptions.
  • Identify guides with high engagement but low conversions and improve CTAs (link to pricing, dashboard, or contact).
  • Identify gaps where search queries don’t have a clear home and consider adding new guides or use cases.

​
5. Next Steps

Hybrid Mail via API

See how the main hybrid mail use case is positioned for SEO and conversions

Bulk Campaigns from CRM / CSV

Review high-intent campaign content that should perform well in search

Overview & Concepts

Core concepts page that will attract long-tail developer queries

API Guides Index

Hub page for internal linking and navigation