06:00 UTC
Chartmogul
Selected accounts
Configured job
Snowflake
Destination table
Join marketing, finance, CRM, and product data inside the same warehouse.
Metrics availables
Dimensions availables
Chartmogul
3 advertising accounts
Connected
Google Ads
2 advertising accounts
Connected
Google Analytics 4
1 web property
Connected
HubSpot
1 CRM portal
Connected
Add the account host, user, and database schema. Use a password for compatible users or a PEM private key for service accounts and stricter policies.
Choose the fields, initial history, partition field, and recurring schedule for the job. Catchr refreshes the configured import window in your PostgreSQL table.
This example summarizes recurring revenue, active customers, churned customers, and churn rate by plan.
Each connector has its own entities, fields, historical limits, and reporting uses. Open a source page for the details that belong to that platform.
Answers about PostgreSQL setup, available source data, schedules, table updates, and SQL use cases.
Add Chartmogul in Sources and connect the existing Snowflake database in Storage. A datastream defines the route, while the job loads the chosen fields into "subscriptions".
Select concrete Chartmogul fields such as ARPA, ARR, ASP, and Day of the month. You can rename the chosen columns, preview the result, and write them to Snowflake tables such as customers, subscriptions, and plans.
Define the first Chartmogul fetch, run frequency, and lookback window in the "subscriptions" job. Each scheduled run replaces data inside the configured period.
Use a supported date field to partition "subscriptions". Recurring Chartmogul runs can then update the selected window instead of adding another copy of the same period.
With Chartmogul data, a Snowflake query can summarize recurring revenue, active customers, churned customers, and churn rate by plan. Model ARPA and ARR in SQL, then expose the result to dashboards, internal tools, or recurring client reports.
Yes. Connect an existing Snowflake database first. The Catchr job creates and populates the destination table you configure inside that 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.
Our teams is always here to responds to any question you could have about our data connector.
Connect your marketing platforms and build a data workflow your entire agency can use.
.svg){kind=logo}
.png){kind=logo}
