Google Ads and Shopify, judged on profit, not just ROAS.
A 4x return on a thin-margin product still loses money. Patricia joins ad spend to Shopify orders and margin so you see POAS by product, cut the SKUs that bleed, and scale the ones that actually pay.

@Pati Fernbrook's store is running a 3.8 blended ROAS on Google. That's fine, right? Where can we push harder?
Fine on average, but the average hides two very different products. I joined Google Ads spend to Shopify's actual orders and margin, so this is POAS, profit on ad spend, not just ROAS:
- The linen tote: 4.1 ROAS but a 22% margin, so POAS is about 0.9. It's selling volume at a loss once you count cost of goods.
- The leather weekender: 3.4 ROAS but a 61% margin, so POAS is about 2.1, and 44% of its buyers are new customers, not repeat.
- In PMax, the feed is spending most on the tote because it converts cheaply, exactly the wrong SKU to favor.

So stop feeding the tote and push the weekender. Draft it.
Queued for your approval, nothing changed yet. Draft: exclude the low-POAS tote and its variants from the Shopping and PMax feed so spend stops chasing it, and lift budget on the campaigns and asset groups driving the high-margin weekender, which is also bringing new customers.
I've left the tote live on the store, this only changes what the ads promote. Say go and I apply the feed exclusion and the budget shift.
1 + 1 > 2
What Google Ads and Shopify do together.
Each is useful alone. Joined, they answer the question neither can on its own.
See ROAS and POAS by product and collection, not just blended
She joins Google Ads spend to Shopify orders and margin so each product and collection shows its real profit on ad spend, not a blended ROAS that hides the thin-margin SKUs quietly losing money.
Split new-versus-returning customer revenue from your paid spend
She reads which orders came from new customers versus repeat buyers in Shopify against the Google Ads spend, so you can judge campaigns on the new-customer revenue they bring, not just total sales that lean on your existing base.
Find which SKUs the Shopping and PMax feed is over-spending on
She lines up feed and asset-group spend against per-product margin, so you can see when PMax is favoring a cheap-converting but unprofitable product and steer the feed toward the SKUs that actually pay.
Pause the money-losing products and scale the profitable ones
Once POAS by product is clear she drafts excluding the loss-making SKUs from the feed and lifting budget on the high-margin winners, and applies it on your approval, so spend follows profit, not click volume.
Report ad spend against real store revenue and margin in one place
Weekly performance with Google Ads spend, Shopify revenue, and margin side by side in your agency's format, so an ecommerce client sees profit and units, not two dashboards that never reconcile.
How it works
Google Ads and Shopify, connected in minutes.
Add Patricia to Slack
She joins your workspace like any teammate. Two minutes, no engineering.
Connect Google Ads and Shopify
One OAuth click each, per client. She gets only the access you approve, and you can disconnect anytime.
Ask
Mention @Pati with the question. She reads both on her own; anything that changes the feed, a budget, or the store waits for your yes.
Say it like you'd say it
Things to ask her.
Fernbrook's store runs a 3.8 blended ROAS, but what's the POAS by product once margin is in?
Which SKUs are selling at a loss on ads once cost of goods is counted?
How much new-customer revenue is our Google spend actually bringing, versus repeat buyers?
Which products is PMax over-spending on relative to their margin?
Exclude the loss-making products from the feed and scale the winners, for my approval
More combinations
Other pairs that work like this.
The stack rarely stops at two. These combinations pull the same trick.
FAQ
Google Ads + Shopify, answered.
What does connecting Google Ads and Shopify together let Patricia do?
She joins Google Ads spend with Shopify's real orders and margin: ROAS and POAS by product and collection, new-versus-returning customer revenue, which SKUs the Shopping and PMax feed over-spends on, and where to cut and scale. Neither tool answers that on its own.
Why POAS and not just ROAS?
Because ROAS ignores margin. A product can return 4x on ad spend and still lose money once cost of goods is counted, while a high-margin product at a lower ROAS is the profitable one to scale. POAS, profit on ad spend, is what tells the two apart.
Does she change the feed, budgets, or the store on her own?
No. Reading both and reporting run on their own. Excluding a product from the feed, shifting budget, or any edit to the Shopify store waits for your explicit yes in Slack.
Do I need both connected?
For the joined, profit-level view, yes: Google Ads for the spend and feed, Shopify for the orders and margin. Each also works on its own.
Does this work across all our client stores?
Yes. Connect each client's Google Ads and Shopify, and every client's spend, orders, and customers stay walled off from the rest.
What does it cost?
Nothing extra. Every integration is included, on every plan.
One of 1,000+ integrations. Browse the full directory
Or one at a time
See each on its own.
Every tool has its own page with the full picture of what Patricia does there.
Everybody deserves a Patricia.
She handles the mess. You keep the clients. See what changes in your first week.
Pick a time that works for you. You get a live walkthrough of Patricia on real agency work, and every question answered.