Send your event data from RudderStack to Podsights.
Podsights is a podcast advertising and attribution platform. It lets you plan your advertising campaigns and measure the effectiveness of your podcasts through audience insights and real-time impression reporting.
Getting started
RudderStack supports sending events to Podsights via the following connection modes:
Connection Mode
Web
Mobile
Server
Device mode
Supported
Cloud mode
-
-
-
Once you have confirmed that the source platform supports sending events to Podsights, follow these steps:
From your RudderStack dashboard, add the source. Then, from the list of destinations, select Podsights.
Assign a name to your destination and click Continue.
Connection settings
To successfully configure Podsights as a destination, you will need to configure the following settings:
Pixel ID: Enter your Podsights Pixel ID. For more information on obtaining your Podsights Pixel ID, refer to the FAQ section below.
Map Rudder events to Podsights Pixel events: Use this setting to map your RudderStack events with standard Podsights Pixel events selected from the dropdown.
You can map multiple Podsights Pixel events to a single RudderStack event and vice versa.
Pass Internal ID: Enable this setting to pass a hashed internal ID in case of alias events. For more information on obtaining the internal ID, refer to the FAQ section below.
Client-side Events Filtering: This setting lets you specify which events should be blocked or allowed to flow through to Podsights. For more information on this setting, refer to the Client-side Events Filtering guide.
Use device mode to send events: As this is a web device mode-only destination, this setting is enabled by default and cannot be disabled.
OneTrust Cookie Categories: This setting lets you associate the OneTrust cookie consent groups to Podsights.
Track
You can use the RudderStack track API to track your user activities and send them to Podsights.
RudderStack supports the following standard Podsights Pixel events:
You can map your RudderStack events to the above Podsights events in the RudderStack dashboard using the Map Rudder events to Podsights Pixel Events setting:
In the above example, RudderStack maps the event Order Completed with the Podsights checkout Pixel event.
By default, RudderStack maps the following events to the Podsights Pixel events:
RudderStack event
Podsights Pixel event name
Signed Up
lead
Product Viewed
product
Product Added
addtocart
Checkout Started
checkout
Order Completed
purchase
RudderStack prioritizes the custom event mappings set in the dashboard over the above standard mappings.
Lead
A sample track call mapped to a lead event is shown below:
The following table lists the mapping between the optional RudderStack event properties and the Podsight attributes:
RudderStack property
Podsights property
properties.value
value
properties.currency
currency
properties.productId
product_id
properties.productName
product_name
properties.productType
product_type
properties.productVendor
product_vendor
Sending multiple product details
If you send the product details as an array in the track event, RudderStack fetches the details from each product item and calls the Podsights product event for each item. For example, consider the following track event:
A sample track call mapped to a addtocart event is shown below:
rudderanalytics.track("Add to Cart",{value:23.2,currency:"USD",productId:"1234000",productName:"goldenTest",productType:"Card",productVendor:"testVendor",});
The following table lists the mapping between the optional RudderStack event properties and the Podsight attributes:
RudderStack property
Podsights property
properties.value
value
properties.currency
currency
properties.productId
product_id
properties.productName
product_name
properties.productType
product_type
properties.productVendor
product_vendor
properties.quantity
quantity
properties.variantId
variant_id
properties.variantName
variant_name
Similar to the Product event, if you send the product details as an array in the track event, RudderStack fetches the details from each product item and calls the Podsights addtocart event for each item.
Check out
A sample track call mapped to a checkout event is shown below:
The following table lists the mapping between the optional RudderStack event properties and the Podsight attributes:
RudderStack property
Podsights property
properties.value
value
properties.currency
currency
properties.quantity
quantity
properties.variantId
variant_id
properties.discountCode
discount_code
properties.lineItems
line_items
If you do not pass the lineItems object, then RudderStack fetches the lineItems from the event’s properties and maps them to Podsight’s line_items field.
Passing multiple product items
If you pass multiple product items as an array, then RudderStack fetches the individual product details and internally builds the lineItems object before passing it on to Podsights via the checkout event, as demonstrated in the following example:
The following table lists the mapping between the optional RudderStack event properties and the Podsight attributes:
RudderStack property
Podsights property
properties.value
value
properties.currency
currency
properties.discountCode
discount_code
properties.lineItems
line_items
properties.orderId
order_id
properties.isNewCustomer
is_new_customer
properties.quantity
quantity
Similar to the Check out event, if you pass multiple product items as an array, then RudderStack fetches the individual product details and internally builds the lineItems object before passing it on to Podsights via the purchase event.
Passing hashed internal ID to Podsights
If Pass Internal ID setting is enabled in the RudderStack dashboard and Alias Events are enabled for your Podsight Pixel, then RudderStack triggers a Podsights alias event capturing the hashed internal user ID along with capturing the track call information.
The Podsights alias event matches the Podsights internal cookie ID with your hashed internal user IDs.
To enable this feature, follow these steps:
Activate Alias Events for your Podsights Pixel from your dashboard:
Then, enable the Pass Internal ID setting in the RudderStack dashboard.
RudderStack automatically calls the Podsights alias event by mapping the following internal RudderStack IDs to Podsights id attribute:
RudderStack attribute
Podsights attribute
userId context.traits.userId context.traits.id
id
Once you enable the Alias event setting, RudderStack automatically passes the alias event along with every other conversion event.
RudderStack uses SHA-256 encryption for hasing your internal userId.
Suppose you send the following track call named testEvent mapped to Podsights’ lead event with the Pass Internal ID enabled:
This site uses cookies to improve your experience while you navigate through the website. Out of
these
cookies, the cookies that are categorized as necessary are stored on your browser as they are as
essential
for the working of basic functionalities of the website. We also use third-party cookies that
help
us
analyze and understand how you use this website. These cookies will be stored in your browser
only
with
your
consent. You also have the option to opt-out of these cookies. But opting out of some of these
cookies
may
have an effect on your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. This
category only includes cookies that ensures basic functionalities and security
features of the website. These cookies do not store any personal information.
This site uses cookies to improve your experience. If you want to
learn more about cookies and why we use them, visit our cookie
policy. We'll assume you're ok with this, but you can opt-out if you wish Cookie Settings.