How to track ad spend across Google, Meta, TikTok and LinkedIn

Tracking ad spend across Google, Meta, TikTok and LinkedIn requires more than adding four platform totals together. The data needs to be aligned to one media plan, one currency, one date range and one taxonomy so the agency can see whether each channel is delivering what was approved.

A dashboard that reports spend without planned spend is useful for accounting, but it is not a pacing system. The operational question is not only 'How much have we spent?' It is 'How much should we have spent by now, against which tactic, and what do we need to change?'

Begin with the media plan, not the APIs

The media plan should define the structure that platform data needs to match. Each plan line should have a market, channel, platform, tactic, audience, dates, budget, KPI and owner.

Before connecting anything, decide the level at which the agency will manage delivery. A single 'Google Ads' line may be adequate for a simple campaign. A larger plan may need brand search, generic search, Performance Max and YouTube represented separately because each line has a different role, budget and success measure. This plan-to-platform mapping is the foundation of reliable spend tracking. Without it, the dashboard shows numbers but cannot explain whether the campaign is following the approved allocation.

Standardise naming across platforms

Google, Meta, TikTok and LinkedIn use different account structures and naming fields. Establish a shared taxonomy that identifies client, market, campaign, objective, audience and tactic consistently.

The taxonomy does not need to make every platform structure identical. It needs enough common identifiers to map each live campaign back to a plan line. Document exceptions rather than relying on one person to remember them. A useful naming convention also improves handover and QA. When a campaign cannot be mapped automatically, the system should flag it for review rather than silently placing the spend in an 'other' bucket.

Align currencies, time zones and date definitions

Cross-platform totals can be wrong even when every individual number is correct. One account may report in US dollars and another in pounds. Platforms may assign spend to different time zones. A client may define its reporting day using a regional finance calendar.

Choose a reporting currency and store both source and converted values where possible. Use a documented exchange-rate method. Standardise the reporting time zone and be clear whether 'today' includes incomplete same-day data. For daily pacing, consistency matters more than false precision. A dashboard refreshed at different times from each platform can create temporary differences that look like genuine movement.

Decide which spend figure counts

Some teams compare media cost only. Others include platform fees, agency commissions, data costs or taxes. The plan and the actuals must use the same definition.

If the approved budget is gross but the API returns net media spend, the campaign will appear behind pace throughout the flight. Separate the components so the team can see media delivery and total financial commitment without mixing them. Document how credits, invalid traffic adjustments and post-campaign platform corrections will be handled. These may be small operational details, but they become important during reconciliation.

Connect platform data securely

Direct OAuth connections reduce the need for CSV exports and shared passwords. Each connection should use the minimum permissions required, remain revocable and have a named owner responsible for resolving authentication failures.

Medusa connects to Google Ads, Meta Ads, TikTok Ads, LinkedIn Ads and DV360, reading platform actuals against the budgets and flighting already held in the plan. An automated connection does not remove the need for QA. The team should confirm account selection, currency, date range and campaign mapping before trusting the dashboard for client reporting.

Compare actual spend with weighted planned spend

Straight-line pacing assumes the same expected spend every day. Use it only when the approved flight is genuinely flat. For launches, retail moments, seasonal demand and learning periods, calculate planned-to-date from the weighted flighting in the media plan - the full formulas are here.

• The core view should show: total budget, planned spend to date, actual spend, variance, variance percentage, remaining budget, remaining days, required daily spend and projected final spend.
• Add outcome metrics where possible. Spend that is 15% ahead with stable CPA is a different situation from spend that is 15% ahead while conversion efficiency deteriorates.

Create a daily operating rhythm

A useful cross-platform dashboard supports a short decision process:

1. Identify lines outside the agreed pacing tolerance.
2. Check data quality and recent platform changes.
3. Diagnose whether the cause is demand, settings, creative, audience, bidding or budget.
4. Decide whether to fix the line, reallocate the budget or accept the difference.
5. Record the decision.

This process is more important than the visual design of the dashboard. Agencies often build impressive reporting views without assigning owners or response times. An alert without an operating rule becomes background noise.

Portfolio visibility for agencies

Client-specific dashboards are necessary, but agency leaders also need a portfolio view. It should show which accounts are materially ahead or behind, the value at risk, the owner and the next action.

This allows senior people to focus on exceptions rather than opening every client workbook. It also reveals repeated operational problems, such as one platform frequently under-delivering or one team consistently mapping budgets incorrectly. Medusa's agency proposition includes one view across client plans, helping teams apply the same pacing method instead of maintaining a different tracker for every account.

Common mistakes to avoid

• Comparing platform totals with a plan that uses a different budget definition.
• Ignoring campaigns that cannot be mapped.
• Using same-day data as though it is final.
• Allowing every planner to create a different threshold.
• Waiting until the monthly report to review delivery - the most expensive mistake of all.

Replace the export ritual

Connect the platforms to Medusa, map campaigns to the approved plan and monitor actual versus planned delivery in one place. The value is not another dashboard; it is knowing which budget needs attention before the campaign window closes.