Datapipe
Start free

Finance · USE CASE

Bring traffic, payments and targets into one review.

Compare GA4 traffic, Stripe paid-payment amounts and your targets in Google Sheets without turning traffic into guessed revenue attribution.

Google AnalyticsStripeGoogle Sheets
Try it with your data Free with up to 3 data sources · No credit card
A WORKED EXAMPLE

Is traffic growth keeping pace with our payment target?

MeasureObservedSheet target
Stripe paid amount · USD$5,400$6,000
GA4 sessions12,00010,000

Oct 2026 · USD payment target · Independent website totals

The paid-payment total is at 90% of the target while sessions are 20% above their target. Review the two signals separately before deciding why.

EXAMPLE WORKFLOW

Ask. Follow up.
Take the next step.

✦ AI assistantSample workflow
Google AnalyticsStripeGoogle Sheets
YOU

  1. 01
    Stripe Paid rows + October target Sheet$600 below target

    Next

  2. 02
    GA4 + October target Sheet20% above target

    Next

Oct 2026 · USD payment target · Independent website totals1 / 3

01 · CONNECT YOUR DATA

Your tools. One place to ask.

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

Google AnalyticsStripeGoogle Sheets
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.

  • Google Analytics: Authorize Google Analytics and select the GA4 property for the same website. Setup guide ↗
  • Stripe: Authorize the intended Stripe account using its supported sign-in or dedicated read-key setup. 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 business targets

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 selected Google Sheet tab and discover its actual headers. Identify period, metric, target amount, currency and definition. Confirm that the payment target is gross Stripe paid amount, not net revenue, profit or bank payouts. Flag missing or ambiguous target rows.
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.

Recheck the October payment total and target. Put the gap in the review sheet. 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

Put the change into practice

Read the full prompt
Update the matched October review row. Use real returned records and verified current values, not the example identifiers or wording. Show the exact proposed change. Prepare the supported action for review in Datapipe; after approval there, apply only the approved change and re-read the source record to verify it. If configured write access or a field is missing, explain what is needed instead of claiming success.
Need to connect your assistant?Claude guide ↗ChatGPT guide ↗

03 · USE WHAT YOU FIND

Calculate attainment and prepare the next review.

  1. 01

    Read the target definitions from Sheets.

  2. 02

    Read compatible actuals independently.

  3. 03

    Calculate attainment and prepare the next review.

Check the result at your next review.

Refresh the review using the same target definitions and complete periods. Recheck current payment states and use appropriate accounting or settlement reports for net revenue and cash questions.

Implementation tips for this use case

Match each target to one compatible period-level actual. Retain missing targets, zero targets and mixed currencies. Stripe’s mapped Paid amount is not net of partial refunds or fees, recognized revenue, or a payout balance.

WHEN YOU NEED MORE CONTEXT

Go a little deeper.

The method and reporting checks
behind this example.

How to compare period-level traffic and payment targets

  1. Read the target definitions from Sheets.

    Connect the spreadsheet and discover the intended tab’s headers. Require period, metric definition, amount and currency where relevant. Avoid adding a monthly target once for every daily actual row.

  2. Read compatible actuals independently.

    Read GA4 sessions for the complete period and Stripe Card payments with date, amount, currency and status. For this example, sum rows marked Paid in one currency and label that gross paid-amount definition.

  3. Calculate attainment and prepare the next review.

    Match each target to one compatible period-level actual. Retain missing targets, zero targets and mixed currencies. Stripe’s mapped Paid amount is not net of partial refunds or fees, recognized revenue, or a payout balance.

See the complete example report
EXAMPLE REPORTFictional sample data

Is traffic growth keeping pace with our payment target?

Oct 2026 · USD payment target · Independent website totals

Is traffic growth keeping pace with our payment target? · fictional sample data
MeasureObservedSheet target
Stripe paid amount · USD$5,400$6,000
GA4 sessions12,00010,000
WHAT TO LOOK ATThe paid-payment total is at 90% of the target while sessions are 20% above their target. Review the two signals separately before deciding why.

Calculate attainment and prepare the next review.

Illustrative report output · no live query or source change

Stripe rows marked Paid sum to $5,400 in USD against the Sheet’s $6,000 paid-amount target: 90% attainment. This is a gross paid-payment view, not net revenue, profit or bank settlement. GA4 reports 12,000 sessions against a target of 10,000. More sessions alongside a payment shortfall does not establish which channel or page caused it.

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

Connect the spreadsheet and discover the intended tab’s headers. Require period, metric definition, amount and currency where relevant. Avoid adding a monthly target once for every daily actual row. Read GA4 sessions for the complete period and Stripe Card payments with date, amount, currency and status. For this example, sum rows marked Paid in one currency and label that gross paid-amount definition. Match each target to one compatible period-level actual. Retain missing targets, zero targets and mixed currencies. Stripe’s mapped Paid amount is not net of partial refunds or fees, recognized revenue, or a payout balance.

Actuals and targets use the same period, unit and payment definition. A target is counted once at the matched period/metric grain. Paid amount is not labelled net revenue, profit or settled cash.

  • Actuals and targets use the same period, unit and payment definition.
  • A target is counted once at the matched period/metric grain.
  • Paid amount is not labelled net revenue, profit or settled cash.
  • Access to the intended Google Analytics account or property.
  • Access to the intended Stripe account or property.
  • Access to the intended Google Sheets account or property.
  • Actuals and targets use the same period, unit and payment definition.

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 ↗Stripe charge fields and status ↗Report starting points ↗

A FEW USEFUL ANSWERS

Before you start.

Is the Stripe paid amount the same as net revenue?

No. This example uses the gross amount on rows marked Paid. Partial refunds, fees, tax, revenue recognition and settlement require suitable additional data and definitions.

Does this tell me which traffic channel caused the payments?

No. The traffic and payment totals are independent scorecards. Channel-to-payment attribution needs consent-aware tracking, compatible identifiers and a validated method.

YOUR NEXT STEP

Try it with your own data.

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

Start free →