Google Shopping, Meta ads and CRO for online stores

Where it leaks. Shopping and Performance Max ads are built from the Merchant Center feed, not from ad copy. Google says shoppers usually notice only the first 70 or fewer characters of a product title, so a title that opens with the brand name and a style code hides what the product is, and promotional text in titles or watermarks on images isn’t allowed.

What we change. Titles lead with what the product is and what sets each variant apart, such as size, color or material, every relevant attribute is filled, and custom labels group products by margin so budgets can follow profit. Performance Max gets campaign-level negative keywords and a weekly read of its search terms report, both available since 2025.

Where it leaks. Google checks the feed against the page. If the price or availability doesn’t match, the product can be disapproved, and too many mismatches stop Google’s automatic corrections. Pages that hold back the shipping cost and the return window until the cart push the most common checkout objection to the last step.

What we change. Product structured data and the feed come from the same source, so price, sale price and stock match. The first screen shows the price, the shipping cost or free shipping threshold, a delivery estimate and the return window, and the same shipping and return settings go into Merchant Center so Google can show them alongside the product.

Where it leaks. In Baymard Institute’s research, extra costs such as shipping, tax and fees are the top reason US shoppers abandon a checkout, named by 40% of those who left for reasons other than browsing, ahead of slow delivery and being made to create an account. Google’s Shopping policies also treat a total price that leaves out fees, or a subscription that hides its billing interval, as misrepresentation.

What we change. Guest checkout, the full cost shown before the payment step, delivery dates in the cart, and for subscriptions, the terms stated before card details are asked for, with express consent and an easy way to cancel, as federal law requires.

Where it leaks. Retargeting and brand campaigns take credit for orders from customers who would have come back anyway, and a blended ROAS can’t tell a new customer from a returning one. A store that can’t see the difference keeps paying to win back people it already has.

What we change. New and returning customers are reported separately. Google’s new customer acquisition goal can bid higher for first-time buyers, Meta campaigns put existing and new customers in separate ad sets, and catalog ads cross-sell the products people buy after their first order.

Where it leaks. GA4 merges purchases that share a transaction ID, so a fixed or empty ID undercounts orders. Meta counts a pixel purchase and a Conversions API purchase as two unless their event ID and event name match, and Meta’s catalog ads depend on pixel events carrying product IDs that match the catalog. ROAS also ignores product cost, shipping, payment fees, discounts and returns.

What we change. Purchases are checked against the store’s own order export: a unique transaction ID in GA4, matching event IDs for the pixel and the Conversions API, enhanced conversions for Google Ads, and cart data with cost of goods from Merchant Center so Google Ads can report gross profit. Each product group gets a break-even ROAS from its contribution margin.

Where it leaks. The same feed decides whether products show in Google’s free listings on Search, Images and the Shopping tab, and collection pages often carry no text that matches how people search. Reviews sit under federal rules too: the FTC bars presenting the reviews on your site as most or all of them while suppressing others for their rating.

What we change. Collection pages written around the terms shoppers use, product structured data that matches the feed, and a review request after every delivered order, with reviews shown whatever their rating, apart from the kinds the FTC lets you exclude, such as abusive or unrelated ones.