# Podscribe (Actions) Destination

## Destination Info

* Accepts [Page](/docs/segment/connections/spec/page), [Alias](/docs/segment/connections/spec/alias), [Group](/docs/segment/connections/spec/group), [Identify](/docs/segment/connections/spec/identify), [Track](/docs/segment/connections/spec/track) calls.
* Refer to it as **Podscribe (Actions)** in the [Integrations object.](/docs/segment/guides/filtering-data/#filtering-with-the-integrations-object)
* This integration is **partner owned.** Please reach out to the partner's support for any issues.

[Podscribe](https://podscribe.com/) measures the effectiveness of podcast advertising. Through integrations with podcast hosting providers, matches downloads with on-site actions, providing advertisers household-level attribution.

## Getting started

1. From the Segment web app, navigate to **Connections > Catalog**.
2. Search for "Podscribe", select it, and choose which of your sources to connect the destination to.

Once you start sending data to the Podscribe's Destination it will take up to 20 minutes to appear in the Podscribe postbacks page.

## Destination Settings

| Field      | Description                     | Required | Type   |
| ---------- | ------------------------------- | -------- | ------ |
| Advertiser | Podscribe advertiser lookup key | Yes      | string |
| User ID    | Podscribe user ID               | No       | string |

## Available Presets

Podscribe (Actions) has the following presets

| Preset Name           | Trigger                                            | Default Action |
| --------------------- | -------------------------------------------------- | -------------- |
| Order Completed Calls | Event type = "track" and event = "Order Completed" | Track          |
| Page Calls            | Event type = "page"                                | Page           |
| Signed Up Calls       | Event type = "track" and event = "Signed Up"       | Track          |

## Available Actions

Build your own Mappings. Combine supported [triggers](/docs/segment/connections/destinations/actions/#components-of-a-destination-action) with the following Podscribe-supported actions:

> \[!NOTE]
>
> Individual destination instances have support a maximum of 50 mappings.

* [Page](#page-1)
* [Track](#track-5)

### Page

Register page view in Podscribe

Page is a **Cloud** action. The default Trigger is `type = "page"`

| Field           | Description                                     | Required | Type   |
| --------------- | ----------------------------------------------- | -------- | ------ |
| Anonymous ID    | The anonymous ID associated with the user       | No       | STRING |
| Timestamp       | The timestamp of the event                      | Yes      | STRING |
| Page Referrer   | The page referrer                               | No       | STRING |
| Page URL        | The page URL                                    | No       | STRING |
| User IP address | The IP address of the device sending the event. | Yes      | STRING |
| Segment Library | The library sending the event.                  | No       | OBJECT |
| User Agent      | The user agent of the device sending the event. | No       | STRING |

### Track

Send user events to Podscribe

Track is a **Cloud** action. The default Trigger is `type = "track"`

| Field                | Description                                     | Required | Type   |
| -------------------- | ----------------------------------------------- | -------- | ------ |
| Anonymous ID         | The anonymous ID associated with the user       | No       | STRING |
| Timestamp            | The timestamp of the event                      | Yes      | STRING |
| Page Referrer        | The page referrer                               | No       | STRING |
| Page URL             | The page URL                                    | No       | STRING |
| User IP address      | The IP address of the device sending the event. | Yes      | STRING |
| Segment Library      | The library sending the event.                  | No       | OBJECT |
| User Agent           | The user agent of the device sending the event. | No       | STRING |
| Email address        | Email address of the user                       | No       | STRING |
| Event properties     | Properties to send with the event               | No       | OBJECT |
| Podscribe event type | Podscribe type of event to send                 | Yes      | STRING |

## Page

If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/segment/connections/spec/page/) does. An example call would look like:

```js
analytics.page();
```

Page calls will be sent to Podscribe as a View event.

Podscribe is an attribution platform, and as such, Podscribe needs more context about the visitor than just a User ID. Analytics.js [automatically collects context fields](/docs/segment/connections/spec/common/#context-fields-automatically-collected). Podscribe requires certain context fields and properties for Page calls. Below is an example of a raw JSON payload that contains the minimum requirements.

```js
{
  "type": "page",
  "context": {
    "ip": "111.111.111.111",
    "userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko Chrome/118.0.0.0 Safari/537.36"
  },
  "properties": {
    "referrer": "",
    "url": "https://url.com"
  },
  "timestamp": "2023-11-05T01:00:00.000Z",
  "userId": "3212"
}
```

For Page events Podscribe requires:

* A `context` object that contains a `userAgent` and an `ip` field
* A `properties` object that contains a `referrer` and a `url` field

You'll see these in the Page event's raw JSON payload above.

The `context` and `properties` objects are required, along with the fields in them. If you're using Segment server-side you must send these attributes.

## Track

If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/segment/connections/spec/track/) does. An example call would look like:

```js
analytics.track("Order Completed", {
  order_id: "50314b8e9bcf000000000000",
  total: 27.5,
  coupon: "hasbros",
  currency: "USD",
});
```

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

* [Signed Up](/docs/segment/connections/spec/b2b-saas/#signed-up) as `signup`
* [Order Completed](/docs/segment/connections/spec/ecommerce/v2/#order-completed) as `purchase`

For Track events, Podscribe requires:

* A `context` object that contains a `userAgent`
* An `ip` Podscribe also requires a `page` object that contains a `referrer` and a `url` field

Analytics.js [automatically collects context fields](/docs/segment/connections/spec/common/#context-fields-automatically-collected). Podscribe requires certain context fields for Track calls. Below is an example of a raw JSON payload that contains the minimum requirements.

```js
{
  "type": "track",
  "context": {
    "ip": "1.2.3.4",
    "userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko Chrome/118.0.0.0 Safari/537.36"
    "page": {
      "url": "https://url.com",
      "referrer": ""
    }
  },
  "event": "Test Event Name",
  "userId": "test-user-xip99",
  "timestamp": "2023-11-05T01:00:00.000Z",
  "properties": {}
}
```

## Engage

You can send computed traits and audiences generated using [Engage](/docs/segment/engage) to this destination as a **user property**. To learn more about Engage, schedule a [demo](https://segment.com/contact/demo).

For user-property destinations, an [identify](/docs/segment/connections/spec/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.

> \[!NOTE]
>
> Real-time audience syncs to Podscribe (Actions)  may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.

## Settings

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

| Field      | Description                     | Required | Type   |
| ---------- | ------------------------------- | -------- | ------ |
| Advertiser | Podscribe advertiser lookup key | Yes      | string |
| User ID    | Podscribe user ID               | No       | string |