06:00 UTC
Adalyser
Selected accounts
Configured job
BigQuery
Destination table
Join marketing, finance, CRM, and product data inside the same warehouse.
Metrics availables
Dimensions availables
Adalyser
3 advertising accounts
Connected
Google Ads
2 advertising accounts
Connected
Google Analytics 4
1 web property
Connected
HubSpot
1 CRM portal
Connected
Select your Google Cloud project and BigQuery dataset. Catchr automatically prepares the destination and maps your data into analytics-ready tables.
Catchr continuously imports new and updated data into BigQuery.
Your warehouse stays fresh automatically, ready for SQL, dbt, BI tools, and AI workloads.
Open the dedicated route for each platform. Its field catalog, reporting grain, historical constraints, and warehouse use cases should be specific to that source.
Answers about available Meta Ads data, reporting cadence, history, table settings, attribution changes, and downstream joins.
Add Adalyser as a source in Catchr, enter your Adalyser username and password, choose BigQuery as the destination, select the fields to export, and authorize the target Google Cloud project and dataset.
Export from 43 metrics and 34 dimensions, including sales value, lead-to-sale conversion rate, cost per lead, channel, product, platform, client, market, campaign status, and broadcast week.
Structure BigQuery tables with Adalyser dimensions such as week start, client, product, channel, platform, and ad group, then analyze metrics including sales value, average sales value, conversion rate, and cost per lead.
Yes. Keep Adalyser and other sources in separate BigQuery tables, then use SQL views or models to join compatible fields such as date, client, product, market, or channel.
Build TV campaign and spot-analysis reports covering sales value, lead-to-sale conversion, cost per lead, traffic-origin sales, and desktop-versus-mobile performance across clients, products, channels, and broadcast weeks.
If your selected schema contains an eligible date field, you can configure that field as the optional date partition for the destination table. Catchr does not configure table clustering or design your downstream analytical models.
Yes. Configure the historical period supported by the source for the initial import, then keep the table updated with recurring exports. The available range is determined by the source API and the settings of your job, not an unlimited-history promise.
Our teams is always here to responds to any question you could have about our data connector.
Connect your accounts, choose the fields then send the configured export to your BigQuery project.
.svg)
.png){kind=logo}
