Overview · Analytics

What is marketing analytics, and how do you build it in Metabase?

Marketing analytics turns ad spend, traffic, search, product activation, and email signals into shared metrics about how you acquire and keep customers — and what that costs. In Metabase, build it by syncing daily aggregates of those signals into a SQL database, modeling clean ad-performance, traffic, product-event, and email layers, and shipping dashboards that put acquisition next to the revenue data everyone already trusts.

TL;DR — Use four adjacent models: ad performance by campaign and day; traffic rollups by channel and landing page; product event rollups with a stable user ID; and email engagement by campaign. Keep raw click and event streams in the source tools — the warehouse gets aggregates, entities, and history.

What does marketing analytics measure?

  • What does a customer cost, per channel and blended?
  • Which campaigns return their spend — and under whose attribution?
  • Where does the funnel leak between visit, signup, and purchase?
  • Is organic search visibility growing, and on which queries?
  • Which acquisition channels send users who activate and stay?
  • Is the email program engaging people or burning the list?
  • How does spend pace against plan, before the month ends?

Which tools feed marketing analytics?

ToolBest forGetting data into Metabase
Google Ads Spend, clicks, and conversions by campaign; ROAS by campaign and channel Google Ads API (GAQL), pipeline, or Google Ads MCP server for exploration
Meta Ads Spend and conversions by campaign objective; ROAS by campaign and ad set Meta Marketing API (Insights), pipeline, or Meta Ads MCP server for exploration
LinkedIn Ads Spend and leads by campaign group; Cost per lead by audience and campaign LinkedIn Marketing API (adAnalytics), pipeline, or LinkedIn Campaign Manager MCP for exploration
TikTok Ads Spend and conversions by campaign; Video view-through rates by creative TikTok Business API, pipeline, or TikTok Ads MCP (Pipeboard) for exploration
Google Analytics 4 Sessions and conversions by channel; Landing-page conversion rates GA4 Data API, pipeline, or Google Analytics MCP server for exploration
Google Tag Manager Tag inventory and ownership by container; Publish cadence and version history Tag Manager API v2, pipeline, or GTM MCP server (Stape) for exploration
Google Search Console Organic clicks and impressions trend; Top queries by clicks and position Search Console API, pipeline, or Search Console MCP (hosted) for exploration
Google AdSense Estimated earnings trend by site; Page RPM and impression RPM by site AdSense Management API v2, pipeline, or AdSense MCP server (community) for exploration
Plausible Analytics Visitors and pageviews trend; Traffic sources and campaign mix Plausible Stats API v2, pipeline, or Plausible MCP (community) for exploration
Amplitude Activation funnel by acquisition channel; Weekly retention cohorts Amplitude Export API, pipeline, or Amplitude MCP for exploration
PostHog Activation funnel by signup source; Retention cohorts by feature usage PostHog batch exports, pipeline, or PostHog MCP for exploration
Mixpanel Signup-to-activation funnel; Retention curves by acquisition cohort Mixpanel Raw Event Export API, pipeline, or Mixpanel MCP for exploration
AppsFlyer Installs by media source and campaign; Cost per install and ROAS by network AppsFlyer Pull API, pipeline, or AppsFlyer MCP for exploration
Mailchimp Campaign opens, clicks, and unsubscribes; List growth and churn by audience Mailchimp Marketing API, pipeline, or Mailchimp MCP server (community) for exploration
ActiveCampaign Campaign opens and clicks by list; Automation completion and drop-off ActiveCampaign API v3, pipeline, or ActiveCampaign Remote MCP for exploration
SendGrid Delivered, bounced, and blocked trend; Open and click rates by category SendGrid v3 API, pipeline, or SendGrid MCP server (community) for exploration
Postmark Delivery, bounce, and spam-complaint trend; Open and click rates by message stream Postmark REST API, pipeline, or Postmark MCP server for exploration
Resend Delivery and bounce rates by domain; Broadcast open and click performance Resend API, pipeline, or Resend MCP server for exploration
Microsoft Advertising Spend, clicks, and conversions by campaign; ROAS by campaign and network Microsoft Advertising Reporting API, pipeline, or Microsoft Advertising MCP server for exploration
Pinterest Ads Spend, impressions, and conversions by campaign; ROAS by campaign and objective Pinterest API v5 (Reports), pipeline, or Pinterest Ads MCP server for exploration
Reddit Ads Spend, impressions, and conversions by campaign; Cost per conversion by community targeting Reddit Ads API v3, pipeline, or Pipeboard Reddit Ads MCP for exploration
Snapchat Ads Spend, impressions, and swipe-ups by campaign; Cost per swipe-up and CPM trends Snapchat Marketing API, pipeline, or Pipeboard Snap Ads MCP for exploration
Adjust Installs by network and campaign; Cost per install and ROAS by network Adjust Report Service API, pipeline, or Adjust MCP for exploration
Customer.io Campaign and broadcast engagement; Journey performance and conversion Customer.io App API, pipeline, or Customer.io MCP server for exploration
Braze Campaign and Canvas engagement; Deliverability by channel Braze REST API (Export), pipeline, or Braze MCP server for exploration
Iterable Campaign engagement by message channel; Journey entry, conversion, and drop-off Iterable API (Export), pipeline, or Iterable MCP server for exploration
beehiiv Open and click performance by post; Subscriber growth and churn beehiiv API v2, pipeline, or beehiiv MCP server for exploration
Kit Broadcast open and click performance; Subscriber growth by form and tag Kit API v4, pipeline, or Kit MCP server for exploration
Segment Event volume by source over time; Warehouse sync health and duration Segment Public API, pipeline, or Segment MCP server for exploration
RudderStack Event volume by source over time; Delivery success by destination RudderStack warehouse destinations, pipeline, or RudderStack MCP server for exploration
Hightouch Sync success rate by destination; Rows added, changed, and removed per sync Hightouch REST API, pipeline, or Hightouch MCP server for exploration
Matomo Sessions and conversions by channel; Top pages and entry pages Matomo Reporting API, pipeline, or Matomo McpServer plugin for exploration
HubSpotLeads, deals, CAC joinsAPI, connector, or HubSpot MCP
StripeRevenue for ROAS and LTV joinsAPI, connector, or Stripe MCP

What shared data models should you build?

Build clean models on top of raw source tables so each dashboard uses the same definitions.

  • ad_performance_daily — one row per campaign per day per channel, with spend, impressions, clicks, conversions, and conversion value
  • campaigns — one row per campaign, with objective, channel, and status
  • traffic_rollups — daily sessions, engaged sessions, and key events by channel, source, and landing page
  • gsc_performance_daily — organic clicks, impressions, CTR, and position by query and page
  • users — one row per product user, with signup date, activation date, and acquisition channel
  • event_rollups — daily product event counts and unique users
  • email_campaign_stats — one row per campaign send, with delivered, clicks, bounces, and unsubscribes
  • leads and customers — the funnel's bottom, with UTM attribution and acquired-at timestamps
  • budgets — planned spend by channel and month, for pacing

Which marketing metrics matter most?

How do you connect tools to Metabase?

  1. MCP + CLI — use MCP for a scoped, summarized live export, then mb upload csv for quick analysis.
  2. Warehouse-backed pipeline — sync daily stats, rollups, and entities with APIs or connectors for durable dashboards.
  3. Modeled layer — map each source into the shared ad-performance, traffic, product, and email models while preserving source-specific extension tables.

Which dashboards should you build first?

Common mistakes

Trying to warehouse raw click and event streams. → Storage costs explode and queries crawl. Sync daily aggregates and entities; keep raw streams in the source tools or GA4's BigQuery export.
Summing platform-reported conversions. → Each platform attributes under its own model — the same purchase can show up three times. Count conversions once, from your own data.
Optimizing cost metrics without quality metrics. → CPL falls fastest when lead quality collapses. Pair every cost metric with a downstream conversion or activation metric.
Letting UTM taxonomy drift. → UTMs are the join keys for the whole model. Publish a convention, validate it in the pipeline, and fix violations at the source.
Measuring marketing in isolation from product and revenue. → The interesting questions — CAC vs. LTV, channels that send users who stay — live in the joins. Land everything in one warehouse.

Integrations

Analytics

Terms

FAQ

What is marketing analytics?
Marketing analytics is the practice of turning acquisition and lifecycle signals — ad spend, traffic, search visibility, signups, product activation, and email engagement — into governed, shareable business metrics. Where platform dashboards answer "how is this campaign doing?", marketing analytics answers "what does a customer cost, which channels send users who stay, and where does the funnel leak?" In Metabase, you build it by syncing daily stats from tools like Google Ads, GA4, and Amplitude into a SQL warehouse and modeling shared metrics on top.
What is the difference between marketing analytics and the reports inside my marketing tools?
Platform reports are single-channel and self-graded: each tool reports its own conversions under its own attribution model, in its own UI. Marketing analytics is cross-channel and governed: one warehouse model where ROAS, CAC, and funnel conversion use definitions you wrote down, joined to CRM and revenue data the platforms never see. You keep the platform UIs for campaign operations and use Metabase for the questions that span channels.
Which metrics should a marketing dashboard track?
Start with acquisition economics: ROAS, customer acquisition cost, cost per lead, and cost per click. Add funnel health — click-through rate, landing-page conversion rate, and conversion rate — then organic clicks and impressions for the unpaid side, and activation rate to connect marketing to product outcomes.
Which tools feed marketing analytics in Metabase?
Any tool whose data you can land in a SQL database. This cluster covers 32 guides: paid media (Google Ads, Meta Ads, LinkedIn Ads, TikTok Ads, Microsoft Advertising, Pinterest Ads, Reddit Ads, Snapchat Ads), web analytics (GA4, Google Tag Manager, Search Console, AdSense, Plausible, Matomo), product analytics and attribution (Amplitude, PostHog, Mixpanel, AppsFlyer, Adjust), lifecycle messaging (Customer.io, Braze, Iterable), customer data platforms (Segment, RudderStack, Hightouch), and email and newsletters (Mailchimp, ActiveCampaign, SendGrid, Postmark, Resend, beehiiv, Kit). See the category overview for connection routes.
How do I handle attribution across channels?
Pragmatically: pick one convention, write it down, and stop expecting platforms to agree. Platform-reported conversions are fine for optimizing inside a channel; for cross-channel truth, count conversions once from your own database or CRM and attribute them with a consistent rule (first-touch, last-touch, or position-based from UTM history). Report the platform and warehouse views side by side rather than forcing them to reconcile — the gap itself is informative.
What data do I need to get started?
Three tables cover the first dashboard: ad_performance_daily (channel, campaign, date, spend, clicks, conversions), traffic_rollups (channel, landing page, date, sessions, key events), and a customers or leads table with an acquisition channel. That is enough for paid channel performance, funnel, and CAC reporting. Add search, product, and email tables as the questions arrive.
Can I build marketing dashboards without a data warehouse?
For a first pass, yes: pull a summarized export through a tool's MCP server and load it with the Metabase CLI (mb upload csv) — each upload becomes a queryable table and model. That works for spot-checks and one-off analyses. Move to a database-backed sync once dashboards need scheduled refreshes, history for trends, and definitions people can trust; every integration guide documents both routes.
How does marketing analytics relate to e-commerce analytics?
They share a border at revenue attribution. E-commerce analytics starts from orders, products, and carts in platforms like Shopify; marketing analytics starts from spend and traffic. The join — UTM-tagged orders next to campaign spend — is where ROAS stops being platform-reported and starts being real. If you run an online store, build both on the same warehouse.