The Commerce Report

How-to

What to check in a store platform before buying ads

Before you spend on ads, confirm your store platform can do six things: fire one accurate purchase event, send that event server-side, load the product and checkout pages fast on mobile, publish a product feed, respect cookie consent, and export orders with their source. A platform that fails any of these makes every campaign look worse than it is.

1. One purchase event, with the right value

Place a test order. Check the ad platform’s event tool. You should see one purchase, with the order value and currency. Two purchases, or none, is the most common fault and it corrupts every report downstream.

2. A server-side route for that event

Browser tracking misses a share of orders. The platform should send purchases from its server to Meta, Google and TikTok, matched to the browser event so they are not counted twice.

Shopify’s Meta sales channel can do this through the Conversions API. Webflow sites do not run server-side code, so there it takes a marketplace app or middleware.

3. Mobile speed on the pages ads land on

Test a product page and the checkout on a mid-range phone over mobile data, not on your laptop. Heavy themes and stacked apps are the usual cause of a slow page.

4. A product feed

Shopping and catalogue campaigns need a feed with correct prices, availability and identifiers. Confirm the platform publishes one to Google Merchant Center and Meta without a manual upload.

If you sell to the EU or UK, the platform needs a consent banner that actually holds tags back until the visitor agrees, and that passes the choice on to your ad platforms’ tags.

6. Order exports with source data

You should be able to export orders with their landing page and campaign parameters. That is how you check the ad platform’s numbers against your own.

Run it before you commit

Whichever platform is on your shortlist, Shopify , Webflow or another, run these six checks on a test store with a test order before you move the catalogue. An afternoon of checking is cheaper than a quarter of campaigns optimised on bad data.

Over the counter

Which check do stores skip most often?

A test order that proves the purchase event reaches the ad platform with the right value and currency. Bidding, reporting and every ROAS figure downstream are built on that one event.

Do I really need server-side events?

Browser-only tracking loses conversions to ad blockers and privacy settings, and the loss grows with your spend. At small budgets the browser pixel is survivable; at real budgets it quietly misprices every campaign.

Does a consent banner break the tracking?

It should hold tags back until the visitor agrees, and pass that choice on to the ad platforms' tags. That is the point of it. If you sell into the EU or UK, check the platform does both before you migrate.

Can I run the checklist before moving the catalogue?

Yes, and you should. A test store and one test order answer all six checks in an afternoon, which is cheaper than a quarter of campaigns optimised on bad data.

What we read, and when

Checked November 15, 2026. These pages change without notice, so the source wins over anything here.

By Thomas Ho, who runs paid acquisition and conversion tracking for ecommerce and lead-generation businesses.

First published November 15, 2026. Prices and features re-checked November 15, 2026.

Thomas HoPerformance marketing consultant

  • 4+ yearsrunning paid campaigns
  • $100k a monthlargest budget managed
  • 4 ad platformsMeta, Google, TikTok, LinkedIn
  • Server-sideGA4, Tag Manager, conversion APIs
More about the author