How to unify Meta and TikTok Ads into a single BigQuery table

Why a consolidated table is still missing

With the analysis done and the history loaded, one piece is left to close the loop: a consolidated table. When building a report across all of Meta and TikTok, loading each table separately is inefficient. Better to have a single one that unifies analogous columns, metrics and dimensions, so consumption always comes from there.

Claude, create a consolidated table that unifies every analogous dimension and metric between TikTok and Meta.

What Claude builds

Claude analyzes how to consolidate: it writes and runs all the SQL the process needs, with a couple of realizations along the way about how to map each field. These queries used to be pulled by hand, one at a time; now Claude resolves them.

The result is a BigQuery view: a SQL query that consolidates the data by always pulling from the source tables, so it comes from the source of truth. You can query the view directly, without splitting between Meta and TikTok, and Claude explains how it mapped each field and which ambiguities are left to fine-tune.

What you have at the end of the series

A consolidated ad data source with history, refreshed in real time, and connected to Claude so you can keep building views and working the data. That view plugs into any system: a report, an agent, alerts, or even a web app with dashboards (the channel has a series showing exactly that).

The foundation is always the same: data consolidated in a warehouse, refreshed in the most efficient way with Detrics transfers, so you always operate from a single source of truth.