Datapipe
Start free

Paid marketing · USE CASE

Follow paid traffic beyond the ad report.

Compare Facebook Ads, tagged GA4 traffic and Shopify order context before deciding what needs a campaign or checkout investigation.

Facebook AdsGoogle AnalyticsShopify
Try it with your data Free with up to 3 data sources · No credit card
A WORKED EXAMPLE

Why do Facebook ad clicks look stronger than purchases?

ReviewObserved resultContext
Prospecting campaign$1,500 spend8 GA4 purchases
Store order check126 paid ordersAll channels

Oct 5–Nov 1, 2026 · USD ad account · Native attribution

Investigate the prospecting journey first. Keep the store-wide order check separate from campaign attribution.

EXAMPLE WORKFLOW

Ask. Follow up.
Take the next step.

✦ AI assistantSample workflow
Facebook AdsGoogle AnalyticsShopify
YOU

  1. 01
    Confirmed campaign UTM mappingInvestigate first

    Next

  2. 02
    Shopify · Same creation-date windowSeparate context

    Next

Oct 5–Nov 1, 2026 · USD ad account · Native attribution1 / 3

01 · CONNECT YOUR DATA

Your tools. One place to ask.

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

Facebook AdsGoogle AnalyticsShopify
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 workflow. 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 ↗
  • Shopify: Enter your shop, authorize it, and add that store to the project. 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 campaign’s native results

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 chosen Facebook Ads campaign’s spend, clicks and attributed purchases. Show currency, report level, dates and attribution settings. Compare within the selected ad account and preserve missing metrics; do not infer profitability from CPC.
02

Follow up across your data sources

Read the full prompt
Use only this Datapipe project’s authorized data sources. Discover the connected accounts, datasets, and fields first. If the right account or required data is missing, ask me rather than substituting sample data. Show the actual dates, filters, coverage, and any partial results.

Check the landing journey and store records. Should we change the budget yet? Read the actual current records behind the shortlist. Show which source supports each observation, distinguish causes from hypotheses, and propose one specific next step.
03

Use the result

Read the full prompt
Prepare the paid-journey investigation. Use the actual returned evidence and retain source dates, attribution and grain. Prepare a concise, usable result in this conversation with owners or unanswered checks where needed.
Need to connect your assistant?Claude guide ↗ChatGPT guide ↗

03 · USE WHAT YOU FIND

Use Shopify as independent store context.

  1. 01

    Keep the ad account’s attribution visible.

  2. 02

    Inspect the tagged GA4 journey.

  3. 03

    Use Shopify as independent store context.

Check the result at your next review.

After the tracking or page review, compare the same source-specific measures over complete periods. Record any campaign or checkout changes and avoid treating a before/after difference as proof of causality.

Implementation tips for this use case

Read order creation dates, payment/cancellation states and explicit currency. Check the selected period covers the intended orders. Store-wide paid orders are not campaign-attributed purchases or proof of a tracking error.

WHEN YOU NEED MORE CONTEXT

Go a little deeper.

The method and reporting checks
behind this example.

How to investigate paid traffic and purchase reporting differences

  1. Keep the ad account’s attribution visible.

    Read Facebook Ads spend, clicks and attributed purchases at campaign grain, preserving account currency and attribution settings. Meta permissions and current availability apply.

  2. Inspect the tagged GA4 journey.

    Use a confirmed campaign-ID or UTM mapping, compatible session reports and purchase events. Align dates/timezones and retain consent, tagging and attribution differences as investigation context.

  3. Use Shopify as independent store context.

    Read order creation dates, payment/cancellation states and explicit currency. Check the selected period covers the intended orders. Store-wide paid orders are not campaign-attributed purchases or proof of a tracking error.

See the complete example report
EXAMPLE REPORTFictional sample data

Why do Facebook ad clicks look stronger than purchases?

Oct 5–Nov 1, 2026 · USD ad account · Native attribution

Why do Facebook ad clicks look stronger than purchases? · fictional sample data
ReviewObserved resultContext
Prospecting campaign$1,500 spend8 GA4 purchases
Store order check126 paid ordersAll channels
WHAT TO LOOK ATInvestigate the prospecting journey first. Keep the store-wide order check separate from campaign attribution.

Use Shopify as independent store context.

Illustrative report output · no live query or source change

Facebook Ads reports $1,500 spend, 1,000 clicks and 24 attributed purchases. The matched GA4 view shows 720 sessions and 8 purchase events under its reporting scope. Shopify returns 126 paid, non-cancelled orders across all channels. That gives the store review context, not a count of orders caused by this campaign.

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

Read Facebook Ads spend, clicks and attributed purchases at campaign grain, preserving account currency and attribution settings. Meta permissions and current availability apply. Use a confirmed campaign-ID or UTM mapping, compatible session reports and purchase events. Align dates/timezones and retain consent, tagging and attribution differences as investigation context. Read order creation dates, payment/cancellation states and explicit currency. Check the selected period covers the intended orders. Store-wide paid orders are not campaign-attributed purchases or proof of a tracking error.

Meta attribution settings and GA4 reporting scopes stay visible. The campaign/UTM mapping is confirmed rather than guessed from a name. Store-wide Shopify orders are not counted as campaign-attributed sales.

  • Meta attribution settings and GA4 reporting scopes stay visible.
  • The campaign/UTM mapping is confirmed rather than guessed from a name.
  • Store-wide Shopify orders are not counted as campaign-attributed sales.
  • Access to the intended Facebook Ads account or property.
  • Access to the intended Google Analytics account or property.
  • Access to the intended Shopify account or property.
  • Meta attribution settings and GA4 reporting scopes stay visible.

For blended reports, align dates, normalized URLs, and reporting grain. Query-level search rows must not duplicate page-level sessions. This is an illustrative workflow; live accounts and destinations need their own setup.

Google Analytics campaign and traffic-source scopes ↗GA4 ecommerce events ↗Shopify inventory states ↗Report starting points ↗

A FEW USEFUL ANSWERS

Before you start.

Should Meta and GA4 show the same purchase total?

Not necessarily. Attribution windows, view-through credit, identity, consent, event setup and reporting scope differ. Validate those definitions before diagnosing the gap.

Can Datapipe automatically tell which Shopify orders came from each ad?

This example compares the returned source reports. Order-level attribution needs compatible transaction identifiers and a validated matching method; it is not inferred from store totals.

YOUR NEXT STEP

Try it with your own data.

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

Start free →