Podscribe
What Is Podscribe?
Podscribe is a podcast attribution and analytics platform that enables advertisers and publishers to measure the performance of their podcast ad campaigns. It provides tools to track conversions and listener engagement, offering insights into how podcast ads drive user actions. Podscribe supports server-side integrations, making it possible to send event data directly for attribution and reporting.
Product Type: Analytics
Integration Type: Starter Kit
Event Source Type: Web & Mobile
Event Scope: Page & Conversion Events
Capabilities
- Sends server-side purchase and view events to Podscribe for attribution tracking
- Captures user agent, IP address, referrer, and page URL to support identity resolution and attribution
- Optionally hashes and sends user email (SHA-256) for identity matching
- Sends device identifiers (IDFA or GAID) when available to support mobile attribution
Considerations
- All server-side events must be sent via GET, with parameters in the query string. Podscribe does not support POST requests for these conversions.
- Podscribe recommends sending both IPv4 and IPv6 addresses for each event when using server-side (S2S) or batch integrations.
- If only one IP type (either IPv4 or IPv6) is sent:
- Podscribe may need to rely on modeling rather than direct matching.
- This can reduce the number of directly matched conversions by up to 50%.
- If only one IP type (either IPv4 or IPv6) is sent:
- Podscribe may use modeled attribution if direct signals (like both IP types, email, or device ID) are missing. The integration should aim to include as many identifiers as possible for optimal attribution accuracy.
Starter Kit Setup Guide
1. Gather Credentials
- Collect your Advertiser ID
- You can find your Advertiser ID in the Podscribe platform at the top of your pixel page. For more details, see here.
2. Add a Podscribe Integration
From the integration library, add a Podscribe integration. Then, fill out the Connection Parameters:
| Connection Parameter | Description |
|---|---|
ADVERTISER_ID | Unique ID assigned by Podscribe to identify the advertiser sending events for attribution tracking. |
3. Configure Event Mapping
- MetaRouter provides all of the event mappings that Podscribe integrations typically require. You may add custom events, parameters or mappings in accordance with Podscribe’s API documentation. Please see below for details on event mapping.
4. Deploy to Pipeline
- In the Pipelines tab, add your Podscribe integration.
- Select the correct integration revision
- Click Add Integration to finalize deployment.
Event Mappings
Global
Global mappings will be applied to all events. If your parameter names do not match the Expected Inputs provided, you will need to overwrite the Inputs provided with your own.
| Output Key | Description | Expected Input |
|---|---|---|
advertiser Required | String: Your Podscribe-issued advertiser ID | Enrichment – staticString: $$ADVERTISER_ID$$ |
user_agent Required | String: The end user’s user agent | context.userAgent |
ip Required | String: The end user’s IP address | context.ip |
timestamp Required | Integer (ms since epoch): Timestamp of when the event occurred | input.originalTimestamp or input.sentAt |
event_url Required | String: Full URL of the page where the event occurred | context.page.url |
device_id | String: A persistent device identifier, if available | anonymousId |
referrer_url | String: Referrer URL of the page where the event occurred | context.page.referrer |
hashed_email | String (SHA-256): Hashed email address for identity resolution | traits.email or context.traits.email |
source | String: Source identifier, e.g., "server" | Enrichment – staticString: server |
| (none) | String: Outputs idfa or gaid based on device type | Expression – Sets idfa if iOS, gaid if Android |
Event Specific
Page
| Output Key | Description | Expected Input |
|---|---|---|
action Required | String: The name of the event action (value: "view") | Enrichment – staticString: view |
Order Completed
| Output Key | Description | Expected Input |
|---|---|---|
action Required | String: The name of the event action (value: "purchase") | Enrichment – staticString: purchase |
order_number | String: Unique identifier for the order | properties.order_id |
currency | String: Currency used in the transaction (e.g., USD) | properties.currency |
value | Float: Total value of the transaction | Expression – sum of product.price * quantity |
discount_code | String: Any coupon or promo code applied | properties.coupon |
Default
| Output Key | Description | Expected Input |
|---|---|---|
action Required | String: The name of the event action (e.g., "view", "purchase") | input.event or staticString per event |
Required & Recommended Identifiers
These identifiers must be mapped to Podscribe in order for successful user matching to occur. Without these IDs, any events sent to Podscribe may not be accurately reflected in reporting. For your convenience, required and recommended IDs are mapped as Global parameters to ensure they are added to every event.
| Attribute | Example | Sync Injector Required? |
|---|---|---|
| ip Required | 192.168.1.1, 2607:f8b0:4005:805::200e | No |
| user_agent Required | Mozilla/5.0 (iPhone; CPU iPhone OS 15_0 like Mac OS X)… | No |
| device_id | 123456abcde | No |
| hashed_email | b58996c504c5638798eb6b511e6f49af... | No |
| idfa | AEBE52E7-03EE-455A-B3C4-E57283966239 | No |
| gaid | 38400000-8cf0-11bd-b23e-10b96e40000d | No |
Integration Validation
- Follow the steps in this guide to validate your implementation: Checking if an Advertiser Integration is Correct
Additional Podscribe Documentation
Updated 10 days ago