Home > Destinations > MySQL > PostHog

Connect PostHog to MySQL

Connect PostHog to MySQL and export selected accounts, metrics, and dimensions to your MySQL project.

Configure the historical window, destination table, and recurring schedule without maintaining a PostHog API pipeline.

Used by the world's leading companies

Export PostHog data to MySQL

Catchr handles extraction, normalization, and loading automatically.

Centralize

Centralize PostHog data in MySQL

Bring all your PostHog data into your warehouse and make it available for analytics, machine learning, and internal applications.

Data freshness

Keep your MySQL tables up to date

Automatically sync new data from PostHog so every dashboard, model, and report works with fresh information.

Analysis

Unify PostHog with the rest of your business data

Join marketing, finance, CRM, and product data inside the same warehouse.

PostHog metrics and dimensions available in MySQL

Access 1 metrics and 41 dimensions from PostHog connectors including Records, Event Name, Event Time, UTM Campaign, UTM Source, UTM Medium, Current Url, Pathname, Referrer, Country Code, City, Device Type, Browser and many more...

1

Metrics availables

41

Dimensions availables

Connect PostHog to MySQL in minutes

Move your data from PostHog to MySQL with a simple setup. Once connected, Catchr handles the ingestion automatically so your warehouse stays up to date without manual work.

Step one

Connect your PostHog account

Authenticate your PostHog account securely in Catchr. No custom scripts, API maintenance, or engineering work required.

Client A · Connected sources
5 sources ready
PostHog 3 advertising accounts Connected
Google Ads 2 advertising accounts Connected
Google Analytics 4 1 web property Connected
HubSpot 1 CRM portal Connected
Step two

Choose the MySQL destination

Connect your existing MySQL database with its host, port, username, password, and database name. Then create the datastream that defines where the selected source data should go.

Destination / MySQL Required fields
Host Required
analytics-db.internal
Username Required
catchr_writer
Password Required
••••••••••••
Database Required
marketing_reporting
Step three

Keep your MySQL tables updated

Choose the fields, initial history, partition field, and recurring schedule for the job. Catchr refreshes the configured import window in your MySQL table.

Export job / MySQL Example
Database Destination
marketing_reporting
Table Per job
google_ads_campaigns
Recurring schedule Choose a cadence
Every 6 hours
Daily · 06:00
Weekly · Mon
Export readySelected fields · configured history
Every 6 hours

PostHog.sql
BigQuery SQL
30-day window
Illustrative SQL — adapt it to the fields and schema selected in your export. Standard SQL

Connect more table to your PostHog data

Open the dedicated route for each platform. Its field catalog, reporting grain, historical constraints, and warehouse use cases should be specific to that source.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Before you schedule the job.

Answers about MySQL setup, available source data, schedules, table updates, and SQL use cases.

Does my MySQL database need to exist before I connect it?

Yes. Connect an existing MySQL database first. The Catchr job creates and populates the destination table you configure inside that database.

Can I load several marketing sources into the same MySQL database?

Yes. Create a separate datastream and job for each source, write each export to its own table, then combine the data downstream with SQL, views, or your BI tool.

Still have a question ? 

Our teams is always here to responds to any question you could have about our data connector. 

Your next MySQL reporting table should not start with five exports.

Connect your accounts, choose the fields, then schedule the data your team needs in MySQL.

14 days free-trial
No credit-card required
100+ sources