kimo
Open demo
Marketing

Meta Ads + Kimo

Facebook and Instagram spend, reach and actions, deduplicated against your own conversion data.

Auth
OAuth 2.0
Sync
Hourly
Setup
≈ 2 min
Request access

Live demo workspace with fictional data · no signup, no credentials needed

kimo / connectors / metaSyncing
Sync loghourly
  • Succeeded:ads_insights+1,339 rowsnow
  • Succeeded:creatives+2,120 rows2m ago
  • Succeeded:ad_sets+2,177 rows4m ago
  • Succeeded:ads_insights+558 rows6m ago
Rows synced · 30 days
177.6M
Workspaces
17%
Simulated demo data
What you can do

What teams build with Meta Ads

Meta Ads on its own answers half the question. Joined with the rest of your stack in Kimo, it answers the other half.

01

Deduplicated conversions

Compare Meta-reported purchases with your own orders to see the real lift.

Reported vs. actual
02

Creative fatigue

Track CTR and frequency per creative and get told when it is time to refresh.

Frequency > 4
03

Audience performance

Cost per signup by audience and placement, across Facebook and Instagram.

CPA by placement
Objects & tables

Exactly what gets synced

Kimo maps Meta Ads into clean, typed tables with primary keys and incremental cursors, so syncs stay fast and joins just work.

3 tables · 14 fields

ads_insights

Append-only≈ 172,000 rows
FieldTypeNotes
datedateIncremental cursor
ad_ididReferences ad
reachintegerMeasure
impressionsintegerMeasure
spenddecimalMeasure
actionsjsonNested · flattened on demand
Custom fields and extra objects are discovered automatically on each sync. Row counts are illustrative.
Sample model

From raw Meta Ads tables to a certified metric

This model ships with the Marketing demo. Open it to see every join and measure.

Paid campaigns ROI

Ads spend reconciled with Stripe revenue per campaign.

In the demo
  • Google Ads
    campaigns
  • Meta Ads
    ad_insights
  • Stripe
    charges
Model
utm = utm
Measurescostrevenueleads
Ad spend · last 30 days
$377+8.8% wk/wk

Fictional data · hover the chart for daily values

Setup

Connect Meta Ads in 2 min

No engineers, no pipelines to maintain. Kimo asks for the minimum access it needs and tells you exactly what it will read.

  1. 1

    Click “Connect Meta Ads”

    You are redirected to Meta Ads to sign in. Kimo never sees your password.

  2. 2

    Approve read-only scopes

    Kimo requests the narrowest scopes available. You can revoke access at any time.

  3. 3

    Pick ad accounts

    Choose which ad accounts to sync. Add more later without reconnecting.

  4. 4

    First sync and schema mapping

    Kimo backfills history, maps ads_insights and suggests joins with your other sources.

Read-only, encrypted, revocable. Credentials are encrypted with a per-workspace key, never logged, and can be rotated without breaking your models.

Connect Meta Ads
Step 2 of 3 · Kimo demo workspace

Kimo wants read-only access to your Meta Ads account

  • ads_readread
  • read_insightsread
Ad accounts
  • act_10294 · Northwind EU
  • act_10295 · Northwind US
Read-only access
Illustration only · placeholder values, never real secrets
FAQ

Meta Ads questions, answered

By default Kimo syncs Meta Ads hourly. You can change the schedule per table, or trigger a sync manually from the connector page.

Meta Ads · OAuth 2.0 · Hourly

See your Meta Ads data in Kimo in 2 min.

Try it on the live demo workspace first, then connect your own account when you are ready.

Request access