How to reconcile Spotify Ads against your store's order table
This is the check we run first on every account, written out so you can run it without us. It takes about thirty minutes and needs two numbers: what Spotify says it produced, and what your store's order table actually shows. The gap between them is the only honest measure of whether your tracking works — and if it comes back small, you do not need us.
Free30 minutesNo obligation
Specific to Spotify × Ecommerce Orders
Spotify Ads vs your orders: no join, so count codes instead
Spotify has no click identifier for most impressions; it credits a site visit within 30 days of exposure by default using IP and device matching. No order in your table can be tied to an ad, so compare promo-code and vanity-URL orders as a floor, and test the pixel's figure with a geo holdout rather than per order.
There is nothing to join on. An order in your table carries no trace of a Spotify impression, and the pixel's purchase count is Spotify's inference from household IP and device signals, not a record of specific orders. What your order table can provide is the deterministic part: orders that used a Spotify-only promo code or arrived through a vanity URL read out in the ad. Use one code per campaign so the counts stay separable.
The default 30-day exposure window means an order can be credited to someone who heard an ad weeks earlier and would have bought anyway. A household sharing one IP address can link a buyer to an exposure on a different person's device. Neither is a fault; it is how exposure attribution works. Check which window your Ad Analytics reporting uses and whether it dates conversions by exposure or by the visit.
Expect Spotify's attributed purchases to sit well above your promo-code orders, and neither figure to match per order. That is normal. Breakage looks different: a pixel purchase count above your total online orders in the markets you targeted, or a sudden drop to zero after a site change. The most common disagreement is treating the pixel figure as a count of orders, when only the code redemptions are.
Spotify × Ecommerce Orders · what breaks
Why Spotify and your store's order table disagree
- 01
Refunds never subtracted
The most common cause and the easiest to check. Sum refunds for the same period — if the platform figure is roughly your gross and your own figure is net, that difference is the whole gap.
- 02
Purchase event firing on page refresh
A confirmation page that re-fires on reload counts one order several times. Compare distinct order IDs against total conversions.
- 03
Point-of-sale orders in the same table
If you have a physical shop, counter sales sit in the same order table and will be counted as advertising conversions unless the channel is filtered.
- 04
Post-purchase upsells arriving late
If the conversion fires at checkout and an upsell adds revenue afterwards, the platform is under-reporting by the upsell take rate.
Spotify × Ecommerce Orders · the fix
What you get from this — Spotify × Ecommerce Orders
A number instead of a suspicion
The likely cause, narrowed
A basis for deciding
Spotify × Ecommerce Orders · architecture
What each side is actually counting — Spotify × Ecommerce Orders
- 1
What Spotify counts
The pixel installed sitewide and firing on the events you care about, plus a defensible way to size what the pixel cannot see. Spotify needs no click identifier because it is not matching one; it is matching exposure to visit.
- 2
How Spotify attributes it
This is the part that makes Spotify different from every other platform on this site. An audio ad played while someone is driving, running or washing up has no click surface at all, and the listener is not looking at a screen. There is no equivalent of gclid or fbclid to capture, because for most impressions there was never a click to identify. Spotify's own documentation is explicit that the pixel fires on a site visit within the attribution window whether or not the listener clicked. Anyone selling you click-based Spotify attribution has not read how the platform works.
- 3
The window it uses
Spotify attributes a site visit within 30 days of ad exposure by default. Confirm the window your reporting is actually set to before comparing it with anything, because a 30-day exposure window and a 7-day click window are not comparable measurements of the same thing.
- 4
What your store's order table counts
Paid orders with their totals, found in Shopify Admin → Orders, WooCommerce → Orders, or a direct query against the orders table.
- 5
The filter that makes them comparable
Financial status is paid, and the sales channel is online rather than point of sale.
Spotify × Ecommerce Orders · events
Reading the gap — Spotify × Ecommerce Orders
| What you see | What it usually means |
|---|---|
| 15%+ platform higher | Usually the wrong event entirely — the platform is claiming more than you took. usually refunds, duplicate firing, or a second channel bleeding into the same conversion action. |
| 20%+ platform lower | Usually structural — the platform is seeing fewer orders than you actually took. usually consent, ad blocking, or an identifier that never reached the order. |
Spotify × Ecommerce Orders · diagnose
Diagnostic order
- 01
Confirm both numbers cover the same period and channel
- 02
Refunds never subtracted
The most common cause and the easiest to check. Sum refunds for the same period — if the platform figure is roughly your gross and your own figure is net, that difference is the whole gap.
- 03
Purchase event firing on page refresh
A confirmation page that re-fires on reload counts one order several times. Compare distinct order IDs against total conversions.
- 04
Point-of-sale orders in the same table
If you have a physical shop, counter sales sit in the same order table and will be counted as advertising conversions unless the channel is filtered.
- 05
Read a geo holdout or promo-code redemption count, reconciled against your own order records — not the conversion figure in Spotify's dashboard
The honest position on audio is that a meaningful share of its effect is not attributable at all and never will be. Someone hears your ad in the car, remembers the name, and searches for you two days later on a different device — that conversion belongs to Spotify and will be recorded as organic search. The correct way to size audio is a geo holdout or a promo code, not a pixel. Say that before anyone sets a target, because the pixel will systematically under-report the channel and over-report Google.
Spotify × Ecommerce Orders · prove
How to know you did it right — Spotify × Ecommerce Orders
Source of truth
your store's order table — orders for a fully closed month
Spotify × Ecommerce Orders · free audit
What we check in the free audit
- Confirm both numbers cover the same period and channel
- Refunds never subtracted
- Purchase event firing on page refresh
- Point-of-sale orders in the same table
- Read a geo holdout or promo-code redemption count, reconciled against your own order records — not the conversion figure in Spotify's dashboard
Checked against
your store's order table — orders for a fully closed month
Free30 minutesNo obligation
Spotify × Ecommerce Orders · when not to buy
When the answer is that you do not need us — Spotify × Ecommerce Orders
- If almost all of your orders come from a channel with no click behind it, no tracking work will reach them — and knowing that is worth more than a build.
- If you are running audio as a small test and expect a pixel to prove it worked, do not build this yet. Run a geo holdout instead: it costs nothing to implement, it measures the thing you actually want to know, and it is the only method that survives scrutiny on an exposure-attributed channel.
Spotify × Ecommerce Orders · what we deliver
The method, step by step — Spotify × Ecommerce Orders
Pull what Spotify reports
A geo holdout or promo-code redemption count, reconciled against your own order records — not the conversion figure in spotify's dashboard.
Pull what your store's order table shows
Export orders for a fully closed calendar month, filtered to paid and online. Count them, and sum the total after discounts and before shipping and tax.
Filter both to the same thing
Financial status is paid, and the sales channel is online rather than point of sale.
Compare per record, not on totals
FAQ
Spotify × Ecommerce Orders questions, answered
Only through promo codes and vanity URLs. Anything else is Spotify's probabilistic estimate, not a property of the order.
The codes are a floor and the pixel figure is an estimate. A geo holdout comparing sales in exposed and unexposed markets is the only method that settles it.
Because you should know the size of the problem before anyone quotes you for it. If the gap is small, you have saved yourself a purchase. If it is large, you now know what you are buying rather than taking our word for it.
No. Both numbers come from systems you already own and neither leaves them. There is no tool to sign up for and nothing to upload.
Then compare totals for a closed period and treat the result as directional rather than exact. A geo holdout or promo-code redemption count, reconciled against your own order records — not the conversion figure in spotify's dashboard is still the right place to read the platform's side.
Under five percent is working. Five to fifteen usually means reversals are missing. Above twenty is normally the wrong event being counted, not a broken tag — which is why debugging tags first wastes so much time.
Then fix the filter before drawing any conclusion. Financial status is paid, and the sales channel is online rather than point of sale. A mismatch in scope produces a gap that looks like a tracking fault and is not one.
Book the free thirty-minute call and bring both numbers. We will tell you which of the causes above it is, and whether it is something you can fix yourself — which it sometimes is.
More on Spotify × Ecommerce Orders
- Google Ads × Ecommerce OrdersHow to reconcile Google Ads against your store's order table
- Meta × Ecommerce OrdersHow to reconcile Meta Ads against your store's order table
- TikTok × Ecommerce OrdersHow to reconcile TikTok Ads against your store's order table
RELATED GUIDES
Systems of record beside ecommerce orders, and the funnels it settles
- Spotify × Enrolment SystemHow to reconcile Spotify Ads against your application or enrolment system
- Spotify × POS SystemHow to reconcile Spotify Ads against your point-of-sale system
- Spotify · Referral → closed saleHow to track referral to closed sale for Spotify Ads
- Spotify · Quiz → segmented offerHow to track quiz completion to segmented offer for Spotify Ads
- Spotify · Animal sheltersSpotify Ads conversion tracking for animal shelters and rescues
- Spotify · FirearmsSpotify Ads conversion tracking for firearms retailers
- Spotify × Booking SystemHow to reconcile Spotify Ads against your booking or reservation system
- Spotify × Appointment SystemHow to reconcile Spotify Ads against your practice or scheduling system
Free · 30 min
Found a gap between Spotify and your store's order table?
WhatsAppFree30 minutesNo obligation
