Why send events to Podscribe?

For Podscribe to run attribution on your audio campaigns, we need to ingest your on-site or in-app data.

This lets us match the IP addresses of say your website visitors, to all the listeners who heard your audio ads, to measure how many visitors had been exposed. Here’s how our attribution works in more detail.

How to send events to Podscribe?

How to confirm everything is set up correctly?

Attribution can only be reliable if the events being sent to Podscribe are correct. This is critical to check at the start!

<aside> 👆 A login is required for this step. If you do not have one, please request your Agency or Publisher complete this step for you.

</aside>

To confirm all is correct with the integration, head to your Tag Setup tab (formerly called the Tag Debug tab) to check:

  1. The right events are coming in. Are all of the events you want to track in the Tag Setup tab? Eg. if you want to track purchases, there should be purchases in the tag debug tab.

    Screen Shot 2024-05-01 at 3.21.55 PM.png

  2. The events, specifically purchases, have all expected data points. Eg for purchases, check to see if the Order ID, order value, hashed emails, and discount codes have correct values. For leads and signups, check to see if hashed emails are coming in, if you’re expecting them.

  3. The right number of events have come in. After two days have passed, check that the number of purchases (or leads, or signups) on Podscribe is the same as the number of purchases on the brand's backend. Waiting for two days ensures that there's one full day of events that have come in. The discrepancy (if any) should be no more than 10%. Note that the Tag Debug tab's timezone is UTC. To see events by day on Podscribe, you can hover your mouse over the line chart, or download a chart of events by day from the top right of the line graph.

<aside> ☝ QUICK TIP: You can see immediately if the tag on your site is working (at least firing) by searching for “Podscribe” in the Network tab under Inspect Element. Quick demo.

</aside>