Spotify (Podsights)
Validate and optimize your podcast advertising by measuring podcast impressions.
Last updated
Validate and optimize your podcast advertising by measuring podcast impressions.
Last updated
Freshpaint can send Events to your Spotify (Podsights) account for a specified Pixel ID.
Supports HIPAA mode
Refer to this destination as Podsights in the Integrations object
Connection Modes:
Web
Mobile
Server
To set up the Podsights integration, follow these steps:
Go to the Spotify (Podsights) configuration page in Freshpaint and click "Configure" for Pixel ID.
In Spotify (Podsights) Dashboard -> Manage -> Your Pixels, find your Pixel ID. Copy this value into your Podsights configuration.
Each event sent to the Spotify (Podsidghts) Track API is categorized as a specific Spotify (Podsights) Event, derived from either the Freshpaint Event Definition name or a Destination Transformation.
Below are the event names supported by Spotify (Podsights).
There are optional parameters (such as value) for each event below, described at its linked page.
Below is the full list of what Freshpaint sends to the Spotify (Podsights) API (beyond Pixel ID) for a Track call:
anonymousId
$device_id
When Identify has not been called prior, an anonymous ID is sent.
One or the other of distinct_id or $device_id is required.
channel
Always sends "server".
context.ip
$ip
Non-hashed public IP address of the browser.
context.
page.
url
$current_url
Page url when event happened. Path redacted in HIPAA mode, including any Query params.
context.
page.
referrer
$referrer
Page referrer.
context.
user_agent
$user_agent
User agent from the user’s device.
event
< freshpaint event name >
Event Definition name.
properties.
<any>
< any custom prop name >
Relevant properties for each track event type are listed here, such as value.
replay
Always sends true.
timestamp
time
Timestamp that the event took place.
type
Always sends "track".
userId
distinct_id
User ID (set by Identify).
Hashed if HIPAA mode.
One or the other of distinct_id or $device_id is required.
Below is the full list of what Freshpaint sends to the Spotify (Podsights) API (beyond Pixel ID) for a Page call:
anonymousId
distinct_id
When Identify has not been called prior, an anonymous ID is sent.
One or the other of distinct_id or $device_id is required.
channel
Always sends "server".
context.ip
$ip
Non-hashed public IP address of the browser.
context.
user_agent
$user_agent
User agent from the user’s device.
properties.
referrer
$referrer
Page referrer.
properties.
url
$current_url
Page url when event happened. Path redacted in HIPAA mode, including any Query params.
properties.
<any>
< any custom prop name >
Any custom property.
replay
Always sends true.
timestamp
time
Timestamp that the event took place.
type
Always sends "page".
userId
distinct_id
User ID (set by Identify).
Hashed if HIPAA mode.
One or the other of distinct_id or $device_id is required.
You can use the Freshpaint Event Tester to quickly verify events from Freshpaint are received properly by Spotify (Podsights). To do so, follow these steps:
In the Spotify (Podsights) Dashboard, navigate to Manage -> Pixels , then select your Pixel ID
Go to the Spotify (Podsights) configuration page in Freshpaint and click "Test Event"
Choose a Podsights-enabled event
Enter required values for $current_url, $ip, and $user_agent, preserving the distinct_id, token, time values. Here are some test values to use:
Click "Test Event"
In the Spotify (Podsights) dashboard, look for event activity (the Debugger view is useful as well, with details on Event Name, Domain, Referrer):
