Podscribe Ad Destination
Set up the Podscribe destination in Ours Privacy: enter your advertiser ID, configure the fields Podscribe requires for attribution on your account, and start sending conversion events.
Podscribe is a podcast advertising attribution platform. Use this page to connect Podscribe as a destination and send conversion events from your existing Ours Privacy event stream.
Step 1: Add the destination and enter your Advertiser ID
- Open the Destinations section and add Podscribe.
- In the destination settings, enter your Advertiser ID — found in your Podscribe account under Pixel Configuration. It's typically a lowercase version of your brand name (e.g.,
bananacorp), not a UUID. - Click Save.
Step 2: Configure the fields Podscribe requires for attribution
Podscribe defines what they need on each event to attribute conversions on your account. By default, Ours Privacy modifies several fields on outbound events to support HIPAA-aligned workflows — depending on what Podscribe asks you to send, you may need to adjust those defaults.
Important: Contact your Podscribe representative to confirm exactly which fields they require for attribution before changing any defaults. Sending personally identifiable data, such as the visitor's real IP address, typically requires appropriate legal agreements with Podscribe (such as a Business Associate Agreement or equivalent) — confirm with your legal and compliance teams first.
IP Address
Ours Privacy modifies the IP address on outbound events by default. If Podscribe requires the real IP address for attribution on your account, adjust the IP Address field's modification in the Podscribe default mapping accordingly.
Action
The action field on each allowed event may be hashed by default. If Podscribe requires the original event name (e.g., view, signup, lead, purchase, or a custom value) to attribute the event, adjust the Action field's modification on each allowed event accordingly.
Step 3: Allow events
Open Allowed Events in the destination settings and select the events you want to send to Podscribe. Customize per-event mappings here if you need anything beyond the defaults — the in-app mapping UI documents every available field.
Note: Make sure the actions you plan to send (e.g.,
signup,purchase) are also enabled inside the Podscribe dashboard.
Step 4: Validate
- Trigger a few test events from your site or app.
- Check the Podscribe dashboard to confirm the events are arriving and attributing as expected.
- If events arrive but do not attribute, contact your Podscribe representative to confirm which fields they require for attribution on your account, then adjust the corresponding mapping modifications in Step 2.
FAQs
What happens if I don't map a field?
Unmapped fields fall back to the value you set (if any) or are omitted from the outbound event.
Can I send custom events?
Yes. Add the event to Allowed Events and configure its mapping. Confirm with your Podscribe representative which action names and fields they expect for the custom events to attribute on your account.
How is this guide?