Podsights Destination

Podsights measures the effectiveness of podcast advertising. Through integrations with podcast hosting providers, Podsights matches podcast downloads with on-site actions to provide household-level attribution.

This destination is maintained by Podsights. For any issues with the destination, contact the Podsights/Spotify support team.

Getting started

1. From the Segment web app, click Catalog.
2. Search for “Podsights”, select it, and choose the source you’d like to connect.
3. Visit your Podsights dashboard, go to Manage > Pixels, then copy your Pixel ID. This is your Segment API Key.
4. Paste the Pixel ID into the API Key field in your Segment destination settings.

Once you start sending data to the Podsights’ Destination it will take up to 20 minutes to appear in the Podsights pixel debugger.

Page

If you’re not familiar with the Segment Spec, take a look to understand what the Page method does. An example call would look like:

analytics.page()

Segment sends Page events to Podsights as view events.

Podsights needs additional context for attribution, including certain fields inside the context and properties objects. Analytics.js automatically collects these fields, but you must provide them manually when sending events server-side.

Here’s the minimum required structure for a Page call:

{
  "type": "page",
  "context": {
    "ip": "1.2.3.4",
    "userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.100 Safari/537.36"
  },
  "properties": {
    "referrer": "",
    "url": "https://podsights.com/"
  },
  "timestamp": "2019-07-19T23:56:59.716Z",
  "userId": "3212"
}

For page events, Podsights requires a context object that contains a userAgent and an ip field and a properties object that contains a referrer and a url field. As you can see in the page event’s raw JSON payload.

If any of these required fields are missing (especially if you’re sending events server-side), Podsights will return a 400 HTTP error.

Track

If you’re not familiar with the Segment Spec, take a look to understand what the Track method does. An example call would look like:

analytics.track('Order Completed', {
  order_id: '50314b8e9bcf000000000000',
  total: 27.50,
  coupon: 'hasbros',
  currency: 'USD',
});

Track calls will be mapped to Podsights events. Podsights supports the following from the Segment Spec:

• Signed Up as lead
• Product Viewed as product
• Product Added as addtocart
• Checkout Started as checkout
• Order Completed as purchase

Track calls must include:

• a context object with userAgent and ip
• a context.page object with referrer and url

These fields are required whether they’re sent through Analytics.js or server-side. Here’s a minimum working example:

{
  "type": "track",
  "context": {
    "ip": "1.2.3.4",
    "userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.100 Safari/537.36",
    "page": {
      "url": "https://podsights.com/",
      "referrer": ""
    }
  },
  "event": "Test Event Name",
  "userId": "test-user-xip99",
  "timestamp": "2019-04-08T01:19:38.931Z",
  "properties": {}
}

If you’re using Segment server-side, you must send these attributes. Otherwise, Podsights will return a 400 HTTP error.

Server

Podsights doesn’t support server-side events by default. However, you can send server-side events as long as you include all the required context and page fields described in the Page and Track sections on this page.

Engage

You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.

For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it’s been more than 30 days since their last order), Engage sets that value to false.

When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.