Exactly which objects and columns are available depends on your account and how the integration is configured. If something described here isn't in your workspace, or you want an object enabled, reach out to us.
Google Ads
Google Ads syncs six daily performance objects.
Cost in every Google Ads object is stored in millionths of the account currency. Divide by one million to get spend in your currency.
Campaign performance report
google_ads_campaign_performance_report: one row per campaign per day, with campaign name, status, and channel type (Search, Demand Gen). The only Google object that carries the campaign name.
- Key columns: campaign name, date, channel type, status, impressions, clicks, cost, conversions, conversion value, CTR, average CPC
- Use it for: spend, results, cost per conversion, and ROAS by campaign over time; brand versus non-brand and region comparisons using your campaign naming
Campaign stats
google_ads_campaign_stats: one row per campaign per day per device per network.
- Key columns: campaign id, date, device, network type, impressions, clicks, cost, conversions, view-through conversions, viewable impressions
- Use it for: mobile versus desktop; Search versus YouTube and other networks; conversions that followed a view without a click; viewability
- Watch for: same spend as the campaign report, cut by device and network, so don't add the two together
Ad group stats
google_ads_ad_group_stats: one row per ad group per day per device per network.
- Key columns: ad group id, campaign id, date, device, network type, impressions, clicks, cost, conversions, cost per conversion
- Use it for: which ad groups take the spend and which return the conversions; ad groups with many impressions and few clicks
- Watch for: carries the ad group id, not the name; the name needs a lookup object that may not be connected in your account
Ad performance report
google_ads_ad_performance_report: one row per ad per day, with the ad's landing page URL and tracking suffixes. Ad text is not included.
- Key columns: ad id, ad group id, campaign id, date, final URL, mobile final URL, URL suffixes, impressions, clicks, cost, conversions
- Use it for: which landing pages get clicks and which get conversions; whether tracking parameters are consistent across ads
Ad stats
google_ads_ad_stats: one row per ad per day per device per network, with the video and viewability metrics the ad report lacks.
- Key columns: ad id, date, device, network type, impressions, clicks, cost, conversions, cost per conversion, view-through conversions, video views
- Use it for: video ad views and cost per view on YouTube; device split per ad; ROAS per ad
Keyword stats
google_ads_keyword_stats: one row per bid keyword per day per device per network.
- Key columns: keyword id, ad group id, campaign id, date, device, impressions, clicks, cost, conversions, conversion value
- Use it for: which keywords take spend and which return conversions; keywords with cost and no conversions over a long window; keywords that convert efficiently within the traffic they got
- Watch for: carries the keyword id, not the text or match type; those need a lookup object that may not be connected in your account
LinkedIn Ads
LinkedIn Ads syncs a large set of objects across seven groups. Targeting values and audience breakdowns arrive as LinkedIn ids; the lookup objects (Urn Names, Organizations) translate them into words.
Account
Ad Accounts, Ad Account Users: one row per ad account and one per user with access.
- Key columns: account id, account name, currency, status, user role
- Use it for: which accounts are in the data and in which currency. Reference only
Structure
Campaign Groups, Campaigns, Creatives: your account structure as configured now.
- Key columns: campaign name, campaign group, status, objective type, format, cost type, bid, daily and total budget, run schedule, audience expansion enabled, creative id, creative status
- Use it for: what is live, paused, or finished; budgets and bids side by side; objectives, so you compare like with like; who each campaign targets and excludes
Performance by structure
By Account, Campaign Group, Campaign, Campaign and Creative, Creative: daily performance at each level, with around a hundred columns because every engagement and conversion type is reported separately.
- Key columns: date, campaign or creative id, impressions, clicks, cost, landing page clicks, lead form opens, lead form submissions, external website conversions, post-click and post-view conversions, video views, video completions, reactions, comments, shares, follows, approximate reach
- Use it for: spend, CPC, CTR, and cost per lead by campaign or creative over time; creative comparison inside a campaign; the video funnel; how much of the conversion count is post-view rather than post-click
- Watch for: all five levels are the same spend, so use one level at a time
Performance by audience
The same metrics cut by who saw the ad, across attributes like company, company size, country, industry, job function, job title, region, and seniority (with combined campaign and creative cuts too).
- Key columns: date, the audience value, campaign id where present, impressions, clicks, cost, landing page clicks, engagement counts, approximate reach
- Use it for: which titles, seniorities, functions, industries, and company sizes your ads actually reached versus who you targeted; which companies engaged, for account-based reporting; country and region split
- Watch for: fewer metrics than the structure analytics, and LinkedIn hides small rows, so these won't sum to the campaign total
Conversions and leads
Conversions, Lead Forms, Lead Responses: the conversion actions defined in the account with their attribution windows; each Lead Gen Form and its questions; one row per submitted lead.
- Key columns: conversion name, type, post-click and post-view attribution windows; form name and status; lead response id, submitted time, campaign and creative id if present, answers if present (email, name, company, job title)
- Use it for: what "conversion" means in each campaign before comparing cost per conversion; leads by campaign, creative, form, and day; lead quality by matching leads to your CRM on email or company
Audiences and lookups
Ad Segments, Dmp Segments, Organizations, Organization Lookups, Urn Names: your matched audiences with size and status, plus the reference tables that turn LinkedIn ids into names.
- Key columns: segment name, type, status, audience size; organization name, industry, staff count range; URN, name
- Use it for: which audiences exist and how large they are
- Watch for: the lookups do nothing on their own, but every targeting and audience view depends on them for its names
Company page, organic
Org Follower, Page, and Share Statistics: your LinkedIn page metrics, not your ads.
- Key columns: date, organization id, total followers, organic and paid follower gains, page views, unique visitors, share impressions, clicks, and engagement
- Use it for: follower growth alongside paid campaign periods; organic post engagement against the sponsored version of the same post
Meta Ads
Twelve objects across four groups.
Daily performance
Four objects sharing the fb_ads_basic_ prefix: fb_ads_basic_campaign, fb_ads_basic_ad_set, fb_ads_basic_ad, and fb_ads_basic_all_levels. One row per day per campaign, ad set, or ad, with names filled in; all-levels carries all three on one row.
- Key columns: date, campaign name, ad set name, ad name, impressions, reach, frequency, clicks, link clicks, spend, CPC, CPM, CTR, actions and cost per action type where enabled
- Use it for: spend, reach, and clicks by campaign, ad set, and ad over time; frequency as the first sign of creative fatigue; CPC trend by ad; cost per result
- Watch for: same spend at four grains, so use one at a time
Configuration history
fb_ads_campaign_history, fb_ads_ad_set_history, fb_ads_ad_history, and fb_ads_creative_history: settings at each level as a change log, one new row every time something is edited.
- Key columns: campaign objective, status, budgets, bid strategy; ad set optimisation goal and full targeting (locations, age, gender, interests, custom audiences in and out, placements); ad creative id; creative title, body, CTA, link URL, URL tags; updated time
- Use it for: the current setup of everything; what changed and when, and how spend moved after each change; targeting overlap between ad sets; creative text next to creative performance
- Watch for: for current state, take the latest row per id
Audiences
fb_ads_custom_audience_history and fb_ads_ad_set_custom_audience: one row per version of each custom audience, plus the link from each ad set to the audiences it includes or excludes.
- Key columns: audience name, subtype (website, customer list, lookalike), rule, retention days, approximate size range, data source, lookalike origin and ratio, delivery and operation status, ad set id
- Use it for: which audiences exist, how they are defined, and how large; which ad sets use or exclude each one; audiences gone stale or too small to deliver; two audiences that are the same list under two names
Demographics
fb_ads_demographics_age_and_gender and fb_ads_demographics_region: daily performance per ad cut by age band and gender, and separately by region.
- Key columns: date, ad id, age, gender, region, impressions, reach, frequency, clicks, link clicks, spend, CPC, CTR
- Use it for: which age bands, genders, and regions take the spend and which return the clicks; whether a wide age range is really spending on one band; frequency by segment
- Watch for: reach does not add up across dates
Working With This Data in Petavue
You don't query these objects directly. Ask Sage in plain language, and it works out which objects and columns to use. A few things worth keeping in mind help you get accurate answers:
- Use one grain at a time. Where a platform reports the same spend at several levels (Google's campaign report versus campaign stats, LinkedIn's five analytics levels, Meta's four daily-performance objects), pick one. Adding them together double-counts.
- Some names need a lookup. Google ad group and keyword names, and LinkedIn's audience values, arrive as ids that depend on a lookup object for their text. If a name is missing, that's usually why.
- Audience rows don't sum to the total. Platforms hide small audience segments, so a breakdown by job title or region won't add up to the campaign's overall numbers.
- Confirm what a conversion means before comparing. Each platform and campaign can define conversions differently. Ask Sage what's behind a conversion count before comparing cost per conversion across campaigns or platforms.
Getting Help
If you have questions, want an object enabled, or want to share feedback, reach out to us directly at support@petavue.com. We're available and responsive, and your input matters.