Datapipe
Start free

Paid marketing · USE CASE

Review campaign pacing before changing ad spend.

Compare Facebook Ads spend with the budget plan your team keeps in Google Sheets, then add tagged GA4 engagement to decide what to investigate before changing a campaign.

Data sources
Assistant
Destination
Try it with your data Free with up to 3 data sources · No credit card
A WORKED EXAMPLE

Which campaigns need a budget-pacing review?

CampaignPacing gapEngagement
Prospect+$40025%
Brand−$20070%

Nov 1–10, 2026 · USD · Matching America/New_York reporting dates

Prospect is $400 above the plan’s even-pacing checkpoint, with 25% of matched GA4 sessions engaged. Review the spending plan and tagged journey first; the figures do not establish profitability.

WHERE THE RESULT GOES

Google Sheets

Export each data source report to Google Sheets, then add your analysis or checklist to the review Sheet.

Example use case

Ask. Follow up.
Take the next step.

✦ AI assistantSample use case
Facebook AdsGoogle AnalyticsGoogle Sheets
YOU

  1. 01
    Nov 1–10 · Verified campaign-to-UTM mapping$400 above checkpoint

    Next

  2. 02
    Same account, currency and complete reporting days$200 below checkpoint

    Next

Nov 1–10, 2026 · USD · Matching America/New_York reporting dates

01 · CONNECT YOUR DATA

Your tools. One place to ask.

3 of 3 Free data sources
No credit card · Daily refresh

DatapipeYour project
Your AI assistantor a report in Sheets / Data Studio
  1. Create your free workspace

    Sign up with your company email. Your first project opens on Data sources.

  2. Add the data sources

    Choose the accounts for this use case. Authorize access and select the property or site.

  3. Bring your question

    Connect your project to a supported AI assistant, or build your source reports.

Create a free account →
Setup steps & what you need

Email/password signups confirm their email first. Use Google signup with a company account if you prefer.

  • Facebook Ads: Authorize Facebook Ads and explicitly select one ad account. Meta permissions and current availability apply. Setup guide ↗
  • Google Analytics: Authorize Google Analytics and select the GA4 property for the same website. Setup guide ↗
  • Google Sheets: Authorize Google Sheets with an account that can open the file, then paste the spreadsheet link and select the intended tab and columns. Setup guide ↗

Free includes 3 data sources across the workspace. One account/property added to one project counts as one. Extra properties or the same account in another project use another slot.

02 · ASK A USEFUL QUESTION

Start with a prompt.
Follow the evidence.

Copy these in order into your connected assistant.
Each builds on the answer before it.

01

Read the budget plan and confirm its assumptions

Read the full prompt
Use only this Datapipe project’s authorized data. Discover the connected accounts, datasets and compatible fields first. Confirm dates, timezones, currencies and data coverage. Keep missing or unmatched rows visible; never substitute sample data. Compare the sources explicitly and explain every match. Do not change source records or send messages.

Read the connected input Google Sheet and discover its actual tab/headers. Identify the agreed budget period, ad-account ID, campaign ID, budget amount/currency, reporting timezone and pacing basis. Ask for a mapping when headers differ. Require one plan per account/campaign/period; keep duplicates, overlapping periods, missing or zero budgets and mixed currencies visible. Confirm whether the plan is even daily, flighted or deliberately front-loaded. Read the team’s verified mapping to GA4 manual campaign ID and source/medium. A Sheet receiving an ad export is not the independent budget plan for this question.
02

Calculate the campaign pacing checkpoint

Read the full prompt
Read Facebook Ads campaign-level date, account_id, account_currency, campaign_id, campaign_name and spend for the complete days from the matched budget-period start through the latest agreed complete day. Show actual coverage and the ad-account reporting timezone. Aggregate daily campaign spend once, without mixing campaign totals with ad/ad-set or placement breakdowns. Match to one budget row by account ID, campaign ID and period; compare currency before calculating. For a confirmed even daily plan only, compute checkpoint = budget amount × elapsed complete calendar days ÷ period calendar days, and gap = spend − checkpoint. Keep the budget once per campaign, not once per daily row. Do not label this checkpoint a platform spend limit or a prediction.
03

Add engagement and prepare the next decision

Read the full prompt
Use the Sheet’s confirmed campaign-to-UTM mapping to read GA4 sessionManualCampaignId and sessionSourceMedium with sessions and engagedSessions for compatible complete dates. Confirm the GA4 property timezone alongside the ad-account timezone; retain incompatible windows, partial coverage, untagged traffic and ambiguous/reused UTM IDs separately. Aggregate GA4 before matching it once per campaign/period. Calculate engagement as total engagedSessions ÷ total sessions, leaving zero-session rates unavailable; do not average daily rates. Return campaign IDs, plan, spend, checkpoint, gap, GA4 sessions/engaged sessions, mapping evidence and one concrete next investigation. Ask the owner to confirm planned launch timing and inspect landing-page/business outcomes before a budget decision. Prepare the list in this conversation; do not change a campaign, move budget or infer profit, ROI or causality from engagement.
Need to connect your assistant?Claude guide ↗ChatGPT guide ↗

03 · USE WHAT YOU FIND

Add website engagement, then prepare the review.

  1. 01

    Read the agreed budget and campaign mapping.

  2. 02

    Compare spend with the same complete days.

  3. 03

    Add website engagement, then prepare the review.

Check the result at your next review.

Record the agreed investigation and any later approved budget or landing-page change. Recheck pacing against the current agreed plan at the next complete-day cutoff, and compare source-specific website outcomes over compatible periods. Keep a changed budget plan version with the review so a new target does not look like a performance improvement.

Implementation tips for this use case

Read compatible GA4 sessionManualCampaignId and sessionSourceMedium with sessions and engagedSessions. Use the verified mapping from the Sheet, not a similar campaign name. Confirm compatible property/account timezones and date coverage; keep unmatched or reused UTM IDs separate. Aggregate each source before matching once to the plan. Calculate engagedSessions ÷ sessions from the totals, then prepare a review list for the account owner and copy approved notes to a separate review tab.

WHEN YOU NEED MORE CONTEXT

Go a little deeper.

The method and reporting checks
behind this example.

How to compare budget pacing with tagged website engagement

  1. Read the agreed budget and campaign mapping.

    Add the Facebook Ads account, the GA4 property for the website and the input budget Sheet to one project. Discover the Sheet’s actual tab and headers. Confirm one plan row per ad account, campaign ID and budget period, with amount, currency, timezone and pacing basis. The example also stores the verified GA4 manual campaign ID and source/medium. These are team-maintained planning inputs, rather than an output export.

  2. Compare spend with the same complete days.

    Read Facebook Ads at campaign level with date, account_id, account_currency, campaign_id, campaign_name and spend. Sum the daily rows for the complete review window. Use the same account currency and reporting calendar as the plan. For an explicitly even daily plan, calculate checkpoint = period budget × elapsed complete calendar days ÷ total calendar days. A front-loaded launch or different campaign flight needs its agreed schedule instead.

  3. Add website engagement, then prepare the review.

    Read compatible GA4 sessionManualCampaignId and sessionSourceMedium with sessions and engagedSessions. Use the verified mapping from the Sheet, not a similar campaign name. Confirm compatible property/account timezones and date coverage; keep unmatched or reused UTM IDs separate. Aggregate each source before matching once to the plan. Calculate engagedSessions ÷ sessions from the totals, then prepare a review list for the account owner and copy approved notes to a separate review tab.

See the complete example report
EXAMPLE REPORT

Which campaigns need a budget-pacing review?

Nov 1–10, 2026 · USD · Matching America/New_York reporting dates

Which campaigns need a budget-pacing review?
CampaignPacing gapEngagement
Prospect+$40025%
Brand−$20070%
WHAT TO LOOK ATProspect is $400 above the plan’s even-pacing checkpoint, with 25% of matched GA4 sessions engaged. Review the spending plan and tagged journey first; the figures do not establish profitability.

Add website engagement, then prepare the review.

The Sheet assigns $3,000 across 30 calendar days. After 10 complete days, its even-pacing checkpoint is $1,000; Facebook Ads spend is $1,400. The mapped GA4 report has 600 sessions and 150 engaged sessions: 25%. The Sheet’s $1,500 monthly plan gives a $500 checkpoint after 10 days. Facebook Ads spend is $300, while the mapped GA4 report has 350 sessions and 245 engaged sessions: 70%.

Try the example with sample CSVs

Fictional rows matching the example above. Attach these files to your assistant for a sample analysis.

Data method, reporting checks & sources

Add the Facebook Ads account, the GA4 property for the website and the input budget Sheet to one project. Discover the Sheet’s actual tab and headers. Confirm one plan row per ad account, campaign ID and budget period, with amount, currency, timezone and pacing basis. The example also stores the verified GA4 manual campaign ID and source/medium. These are team-maintained planning inputs, rather than an output export. Read Facebook Ads at campaign level with date, account_id, account_currency, campaign_id, campaign_name and spend. Sum the daily rows for the complete review window. Use the same account currency and reporting calendar as the plan. For an explicitly even daily plan, calculate checkpoint = period budget × elapsed complete calendar days ÷ total calendar days. A front-loaded launch or different campaign flight needs its agreed schedule instead. Read compatible GA4 sessionManualCampaignId and sessionSourceMedium with sessions and engagedSessions. Use the verified mapping from the Sheet, not a similar campaign name. Confirm compatible property/account timezones and date coverage; keep unmatched or reused UTM IDs separate. Aggregate each source before matching once to the plan. Calculate engagedSessions ÷ sessions from the totals, then prepare a review list for the account owner and copy approved notes to a separate review tab.

Campaign IDs, ad account, budget period and currencies match; the budget is counted once after daily spend is aggregated. Even pacing is an agreed planning assumption. Campaign flight dates, planned bursts and partial days change the comparison. GA4 manual campaign IDs come from confirmed UTM tagging; reused IDs or similar names are not an automatic match. Engagement uses compatible session totals and does not establish revenue, profit or a reason to change spend.

  • Campaign IDs, ad account, budget period and currencies match; the budget is counted once after daily spend is aggregated.
  • Even pacing is an agreed planning assumption. Campaign flight dates, planned bursts and partial days change the comparison.
  • GA4 manual campaign IDs come from confirmed UTM tagging; reused IDs or similar names are not an automatic match.
  • Engagement uses compatible session totals and does not establish revenue, profit or a reason to change spend.
  • Access to the intended Facebook Ads account or property.
  • Access to the intended Google Analytics account or property.
  • Access to the intended Google Sheets account or property.
  • Campaign IDs, ad account, budget period and currencies match; the budget is counted once after daily spend is aggregated.

For blended reports, align dates, normalized URLs, and reporting grain. Query-level search rows must not duplicate page-level sessions.

Meta’s official Ads Insights fields ↗GA4 session dimensions and engagement metrics ↗Google campaign URL parameters and utm_id ↗Report starting points ↗

A FEW USEFUL ANSWERS

Before you start.

Why do I need three data sources?

Facebook Ads supplies actual spend. The input Sheet supplies the independently agreed budget, pacing assumptions and campaign mapping. GA4 supplies tagged website engagement. Each answers a different part of the review.

Does being ahead of even pace mean I should reduce the budget?

Check the agreed schedule first. A launch can intentionally spend more early in the period. Use the gap to choose an investigation, then include business outcomes and the account owner in the decision.

Can I match Meta campaign IDs directly to GA4 campaign IDs?

Only when your actual tagging establishes that relationship. GA4 sessionManualCampaignId comes from utm_id. The example’s Sheet explicitly maps each advertising campaign to that value and source/medium. Untagged visits and reused IDs stay outside an unambiguous campaign comparison.

Does the GA4 engagement rate show which campaign is profitable?

No. It describes the share of sessions meeting GA4’s engagement definition. Evaluate relevant business events, attribution and commercial evidence separately before deciding whether campaign spend is worthwhile.

YOUR NEXT STEP

Try it with your own data.

Start free with up to 3 data sources. No credit card.

Start free →