Spotify Ads Troubleshooting & Debugging

Symptom Library

• Spotify Pixel (spdt) not loading or sp.gif requests absent from Network tab
• Conversion tracking showing zero conversions in Ad Studio reporting
• Audio ad impressions not recording or undercounting
• Audio creative rejected for format, duration, or loudness violations
• Frequency cap behavior not matching expected settings
• Measurement partner (DCM, IAS) data not aligning with Spotify-reported numbers
• Audience segment size too small for targeting (minimum 1,000 users)

Spotify Pixel Debugging

The Spotify Pixel (also called the Spotify Ad Tag) fires requests to pixel.spotify.com. Debug it in DevTools:

1. Open Chrome DevTools > Network tab and filter for pixel.spotify.com or spdt.
2. Navigate to your conversion page and look for a request to https://pixel.spotify.com/v1/sp.gif.
3. Verify the query parameters include your spdt (Spotify Pixel ID) and the correct event type.
4. A 200 response with a 1x1 GIF confirms the pixel is working. A 400 means malformed parameters; a 403 means the pixel ID is not recognized.

// Base pixel initialization
spdt('init', 'YOUR_PIXEL_ID');
spdt('track', 'pageview');

// Conversion event
spdt('track', 'purchase', { value: 29.99, currency: 'USD', order_id: 'ORD-789' });

5. If spdt is not defined appears in the Console, the base script failed to load. Check for Content Security Policy (CSP) headers blocking pixel.spotify.com.

Audio Ad Creative Validation

Spotify has strict audio creative requirements. Rejections typically cite one of these reasons:

Use ffprobe to check your file before uploading:

ffprobe -v quiet -show_format -show_streams your_ad.mp3
# Check: duration, sample_rate, bit_rate, format_name

For companion display banners (shown alongside audio ads), images must be 640x640px JPEG or PNG, under 200KB.

Frequency Cap Behavior

Spotify's frequency capping works differently than display platforms:

• Default cap: 4 impressions per user per day across all audio placements.
• Campaign-level cap: You can set a lower cap (e.g., 2/day), but not higher than the platform default.
• Cross-campaign frequency: Spotify manages global frequency across all advertisers. Your campaign may deliver fewer impressions than expected if users have already been exposed to other ads that session.
• Podcast vs. music inventory: Frequency caps apply separately to music and podcast placements. A user may hear your ad twice on music and twice on podcasts in the same day.

If delivery is below expectations despite available budget, frequency caps are the most common cause. Check Ad Studio > Campaign > Delivery Insights for frequency distribution.

Measurement Partner Integration (DCM, IAS)

Spotify supports third-party measurement through pre-approved partners:

• DCM (Campaign Manager 360): Supply your DCM impression tag as a third-party tracking URL in Ad Studio. Discrepancies under 10% are normal. Spotify counts when audio playback begins; DCM counts when the tag fires.
• IAS (Integral Ad Science): Measures companion display banner viewability and brand safety, not the audio stream itself.
• Nielsen DAR: For demographic verification. Allow 72 hours for data to populate.

If DCM numbers are significantly lower (over 20% gap), check that the DCM tag URL is not being blocked by ad blockers on the companion display.

Impression Counting Methodology

• Audio impressions: Counted when at least 1 second of audio is played. Skipped ads are not counted.
• Video impressions: Counted when 50% of video is in view for at least 2 continuous seconds (MRC standard).
• Companion display: Counted when the banner renders, regardless of audio completion.
• Audio ads have no clickable element during playback. Use companion banner CTR or conversion lift studies for engagement measurement.

Escalation & Communication

• Spotify Ads Support via Ad Studio: Include your campaign ID, date range, and expected vs. actual metrics.
• For measurement partner discrepancies, contact both Spotify and the partner simultaneously with matching date ranges.
• Creative support reviews rejected assets within 1 business day. Include ffprobe output in resubmissions.

Preventive Maintenance

• Weekly pixel validation: check for pixel.spotify.com requests on conversion pages after deployments.
• Pre-validate all audio creatives with ffprobe before uploading to avoid rejection delays.
• Quarterly reconciliation between Ad Studio and measurement partner reporting.