How to track directory listing to enquiry for Spotify Ads

Architecture

The exact event sequence

Five stages. There is no browser session anywhere in the first three stages. The measurement has to be built at intake, in your own system, or it cannot be built at all. The identifier has to survive all of them.

1. Step 1

   Directory listing viewed

   On the directory's domain. You will never see this event; the directory may report it.

2. Step 2

   Enquiry submitted

   On the directory's form. Still not your property.

3. Step 3

   Lead delivered

   By email or API, usually with the directory named somewhere in the payload.

4. Step 4

   Lead qualified

   Directory lead quality varies enormously between directories and is the whole reason to measure this.

5. Step 5

   Job or deal won

   The only stage with money attached.

Diagnostic sequence

What's specific to Spotify Ads

The funnel logic above is the same wherever you advertise. These are the parts that change because it's Spotify Ads.

1. 1

   Why Spotify has no click identifier

   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.

2. 2

   Import mechanism: the Spotify Pixel

   A JavaScript pixel in the head of every page, plus event snippets for the conversions you care about. Spotify Ad Analytics then attributes site actions back to ad exposure using IP matching and device graphs rather than a click identifier — which is probabilistic by construction. Read Spotify's own current documentation before building; the pixel's capabilities were extended across music and podcast inventory and older guides describe a narrower product.

3. 3

   Deduplication

   The deduplication problem here is not browser-versus-server, it is Spotify-versus-everyone-else. Because attribution is exposure-based and probabilistic, a conversion Spotify claims will frequently also be claimed by Google, Meta and your email tool — all four looking at the same purchase. Summing platform-reported conversions across channels has always been wrong; with an exposure-attributed channel in the mix it is wrong by a much larger margin. Reconcile against your own order count, always.

4. 4

   Window and timing

   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.

5. 5

   The Spotify gotcha

   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.

Source-of-truth validation

How to prove the chain works

One real journey, followed all the way, then a reconciliation. Neither on its own is enough.

• A live Spotify ad clicked, and the identifier confirmed present on the landing URL.
• The same identifier confirmed on the enquiry in your CRM or inbox after a full real journey through every step.
• Job or deal won confirmed arriving at Spotify Ads, verified by a geo holdout or promo-code redemption count, reconciled against your own order records — not the conversion figure in Spotify's dashboard.
• Your crm, with the directory source recorded at intake reconciled against Spotify Ads per record over a fully closed window.
• The same reconciliation repeated 30 days later.

Straight talk

When this doesn't apply to you

Worth checking before you build anything, because two of these are common and both mean the work isn't worth doing.

• If you are not paying for directory placement, tracking this tells you something interesting and changes no decision.
• 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.
• If your cycle from click to job or deal won regularly exceeds the import window, the final event can't drive bidding whatever you build. Optimize toward tagged enquiry count per directory instead and use the later data for budget decisions rather than for bidding.
• If you cannot run a holdout, be honest that Spotify's reported conversions cannot be separated from what other channels also claimed. That is a reason to keep the budget small, not a reason to build a pipeline.