Podscribe

Send server-side conversion events to Podscribe for podcast advertising attribution and measurement. Zeotap delivers events via the Podscribe S2S (server-to-server) API, enabling accurate campaign measurement without relying on client-side tracking.

Prerequisites

A Podscribe advertiser account
Your Advertiser ID (found at the top of the Tag Setup page in the Podscribe dashboard)
Conversion event data with IP addresses and user agent strings for attribution matching

Authentication

Podscribe uses an Advertiser ID for authentication.

Log in to the Podscribe dashboard
Navigate to Tag Setup
Copy your Advertiser ID from the top of the page
In Zeotap, paste the Advertiser ID when creating the destination

No OAuth flow or API key is required — the Advertiser ID is used to associate events with your account.

Configuration

Field	Type	Required	Description
Source	Text	No	An optional label identifying the data source (e.g., `zeotap`). Defaults to `zeotap` if not set.

Target Settings

Field	Type	Required	Description
Event Action	Select	Yes	The default conversion action type for events. Options: `view`, `purchase`, `signup`, `lead`, `custom`.
Custom Action Name	Text	No	The custom action name when Event Action is set to `custom`. Example: `add_to_cart`.

Supported Operations

Sync Modes

Mode	Supported
Insert	Yes
Update	—
Upsert	—
Mirror	—

Audience Sync Modes

Mode	Supported
Add	—
Remove	—
Mirror	—
Upsert	—

Features

Feature	Supported
Field Mapping	Yes
Schema Introspection	No

Required Mapping Fields

Field	Description
`ip`	User’s IP address (IPv4 or IPv6). Required for Podscribe’s attribution matching.
`user_agent`	User’s browser or device user agent string.

Default Destination Fields

Event Identification

Field	Type	Description
`ip`	string	User’s IPv4 or IPv6 address.
`user_agent`	string	User’s browser or device user agent string.
`timestamp`	timestamp	Event timestamp in milliseconds since epoch.
`action`	string	Conversion action type (`view`, `purchase`, `signup`, `lead`, or custom).

Event Context

Field	Type	Description
`event_url`	string	Full URL of the page where the event occurred.
`referrer_url`	string	Referrer URL for the event page.

Identity Matching

Field	Type	Description
`hashed_email`	string	SHA-256 hashed email address for identity matching.
`ip6`	string	User’s IPv6 address. Sending both IPv4 and IPv6 improves match rates.
`device_id`	string	Persistent device identifier.
`idfa`	string	iOS Identifier for Advertisers.
`gaid`	string	Google Advertising ID (Android).

Purchase Event Fields

Field	Type	Description
`order_number`	string	Unique order identifier for purchase events.
`value`	number	Monetary value of the conversion event.
`currency`	string	ISO 4217 currency code (e.g., `USD`, `EUR`).
`discount_code`	string	Coupon or promo code used in the transaction.

How It Works

Zeotap reads rows from your model query and applies field mapping to transform your data into Podscribe’s S2S event format.

Event delivery: Each row is sent as an individual GET request to https://verifi.podscribe.com/tag with all fields encoded as query parameters. Podscribe does not support POST requests or batch endpoints for S2S events.

IP address matching: Podscribe uses IP addresses as the primary signal for podcast ad attribution. For best results, send both IPv4 (ip) and IPv6 (ip6) addresses when available. Sending only one IP type may reduce directly matched conversions by approximately 50%.

Source labeling: Events include a source parameter (defaults to zeotap) so you can distinguish Zeotap-originated events in the Podscribe dashboard.

Action types: Set the default event action in target settings. To send different action types within a single sync, map the action field and provide the value per row.

Rate Limits

Podscribe does not publish specific rate limits for the S2S endpoint. Zeotap sends events sequentially with automatic retries on transient errors.

Best Practices

Send both IP versions: Map both ip (IPv4) and ip6 (IPv6) fields when available to maximize attribution match rates
Include timestamps: Always map the timestamp field so Podscribe can accurately attribute conversions to the correct podcast ad exposure window
Hash emails before sending: The hashed_email field expects a SHA-256 hash — hash email addresses in your model query before mapping
Use event URLs: Including event_url and referrer_url provides additional context for Podscribe’s attribution model
Tag purchase events completely: For purchase actions, include order_number, value, currency, and discount_code for comprehensive revenue attribution

Troubleshooting

Events not appearing in Podscribe dashboard

Verify your Advertiser ID is correct. Navigate to Tag Setup in the Podscribe dashboard and confirm the ID matches what you configured in Zeotap. Events may take several minutes to appear.

Low attribution match rates

Podscribe relies on IP addresses for matching. If match rates are lower than expected, ensure you are sending both IPv4 and IPv6 addresses. Sending only one IP type can reduce direct matches by up to 50%.

Missing conversion values

For purchase events, ensure the value field contains a numeric value and currency contains a valid ISO 4217 code (e.g., USD). Both fields must be mapped for revenue to appear in Podscribe reports.

Invalid Advertiser ID error during connection test

The Advertiser ID is case-sensitive. Copy it directly from the Tag Setup page in the Podscribe dashboard. Do not add extra spaces or modify the ID.

Timestamp format issues

Podscribe expects timestamps in milliseconds since epoch. If your data uses seconds or ISO 8601 format, transform it in your model query before mapping.

Events sent but not attributed to campaigns

Attribution requires that the user was previously exposed to a podcast ad tracked by Podscribe. Events for users without prior ad exposure will be recorded but not attributed. This is expected behavior.