For your audio campaigns to truly shine, understanding their impact through precise attribution is key. Podscribe's pixel-based attribution intricately matches conversions from your website or app visitors' IP addresses with those of listeners exposed to your audio ads.
This process demystifies the journey from ad exposure to site visitation or app engagement. Dive deeper into our methodology here to grasp how Podscribe can elevate your campaign insights.
Setup Steps
Podscribe can track app installs and in-app events.
Perfect for mobile apps, Podscribe seamlessly integrates with leading MMPs like Appsflyer & Adjust. Activating Podscribe in your MMP dashboard is straightforward, letting you to send app install and in-app event data directly to Podscribe for attribution.
Podscribe has integrations with:
To enable Podscribe on your MMP:
- Get your advertiser ID and user ID from Podscribe. Here’s our full guide to finding your advertiser and user ID.
- Search integration partner Podscribe on your MMP.
- Add your advertiser and user ID, if applicable. For example, here’s where you would type them in on Appsflyer:
- Then select which events you want to send Podscribe, and get started!
- Inform adops@podscribe.com when the integration is set up on the MMP side.
How to confirm everything is set up correctly?
Ensuring that your setup is correct from the start is pivotal for reliable attribution. Attribution can only be reliable if the events being sent to Podscribe are correct. This is critical to check before campaigns start!
Here’s how to confirm all is correct with the integration.
Does Podscribe send data back to MMPs like Adjust to let the MMP do attribution?
Not directly, but there’s a workaround. Our integration with MMPs is a one-way street. MMPs (like Adjust) send install data from all sources into Podscribe, and we identify which installs can be attributed to podcasts. In theory, MMPs could also do podcast attribution, but in practice they can’t because they lack the necessary privacy agreements with publishers or access to exposed IPs.
However, many advertisers rely on MMPs to compare attribution results from different channels. In such cases, clients often set up an API integration between Podscribe and their MMP to unify Podscribe results with their other reporting.
Here's a link to our API documentation and how to generate an API key.
Questions?
What pages can I use certain event tags on?
You can use the “signup”, “lead”, or “purchase” events on any page you’d like. For example, if you wanted to measure how many exposed listeners visited a Sign-up page, you could fire the “signup” event on page view. Then, once they completed the form, you could fire the Lead event, passing us the hashed email. We recommend placing the “visit” tag on all pages.
Can I use custom event names? I want to create and track other events besides installs, view, signups, leads, and purchases.
Yes! If the primary 5 events are not adequate, we can track custom, additional events. We can also support re-naming the standard event names on our dashboard to names you're more familiar with, such as "Account Creation". To do so, you would simply change the name of the action in your javascript tag from "purchase" or "view" to the custom event name you'd like:
Instead of loading the script bundle, can we call a 1x1 image pixel, or pass events server-side, or in batch?
Yes - please see this guide.
How do I know which advertiser to pick? There are many that pop up with the name of the advertiser.
Podscribe regularly removes duplicate advertisers, but here are some steps that you can take to ensure you're selecting the right advertiser.
- Look up the different advertisers with the same name on Podscribe.
- Check all of the advertisers one by one. If the logo and website are correct, then that advertiser is likely the correct one.
Select the name displayed on the advertiser page as the advertiser’s name when creating your campaign:
If you can’t find the advertiser you’re looking for, feel free to reach out to adops@podscribe.com.
What is the Content Security Policy (CSP) for the Podscribe web tag?
Content-Security-Policy:
default-src
self
script-src
d34r8q7sht0t9k.cloudfront.net
connect-src
verifi.podscribe.com
pixel.tapad.com
ipv4.podscribe.comHow to integrate using a Shopify Custom Pixel, instead of the Shopify app, for Shopify stores?
See here for general info on Shopify Custom Pixels, and below for the Podscribe code.
Be sure to replace YOUR_USER_ID and YOUR_ADVERTISER_ID with your IDs.
(function (w, d) {
var id = 'podscribe-capture',
n = 'script';
var e = d.createElement(n);
e.type = 'text/javascript';
e.id = id;
e.async = true;
e.src = 'https://d34r8q7sht0t9k.cloudfront.net/tag.js';
var s = d.getElementsByTagName(n)[0];
s.parentNode.insertBefore(e, s);
e.onload = onLoad;
})(window, document);
function onLoad() {
podscribe('init', { user_id: YOUR_USER_ID, advertiser: YOUR_ADVERTISER_ID });
analytics.subscribe("page_viewed", (event) => {
window.podscribe('view', { source: "shopify-custom" });
});
analytics.subscribe("product_viewed", (event) => {
window.podscribe('ViewContent', { source: "shopify-custom" });
});
analytics.subscribe("search_submitted", (event) => {
window.podscribe('Search', { source: "shopify-custom" });
});
analytics.subscribe("product_added_to_cart", (event) => {
window.podscribe('AddToCart', {
currency: event.data?.cartLine?.merchandise?.productVariant?.price?.currencyCode,
value: event.data?.cartLine?.merchandise?.productVariant?.price.amount,
source: "shopify-custom"
});
});
analytics.subscribe("payment_info_submitted", (event) => {
window.podscribe('AddPaymentInfo', {source: "shopify-custom"});
});
analytics.subscribe("checkout_started", (event) => {
window.podscribe('InitiateCheckout', {source: "shopify-custom"});
});
analytics.subscribe("checkout_completed", (event) => {
try {
const allDiscountCodes = event.data?.checkout?.discountApplications?.map(
(discount) => {
if (discount.type === "DISCOUNT_CODE") {
return discount.title;
}
}
);
discountCode = allDiscountCodes ? allDiscountCodes.filter(Boolean).join(", ") : undefined;
} catch (e) {
console.log(e);
}
window.podscribe('purchase', {
value: event.data?.checkout.totalPrice?.amount,
currency: event.data?.checkout.totalPrice?.currencyCode,
order_number: event.data?.checkout?.order?.id,
hashed_email: event.data?.checkout.email,
num_items_purchased: event.data?.checkout.lineItems?.length,
source: "shopify-custom",
discount_code: discountCode
});
});
}I have a new client! What's the fastest way to get javascript pixels to send them?
It is to generate them from the Tag Setup tab:
How important is it to include a hashed email in the pixel? If we do not, what would we lose out on?
Sending us hashed emails lets us find 10-20% more attributed conversions, so it is certainly helpful to have! Here’s further detail on the part that hashed emails play in attribution. If you send us raw emails, we hash them as they come in and only store the hashed ones.
What mobile device partners (MMPs) does Podscribe work with?
Podscribe works with all major MMPs including: Adjust, Appsflyer, Kochava, Singular, and Segment.
What client data & PII does Podscribe collect as part of its measurement methodology, and how?
The only PII Podscribe collects from advertisers are IP addresses. Podscribe never collects real names, addresses, billing details, raw emails, or any medical info. Podscribe only collects & relies upon anonymous digital identifiers, specifically:
- IP address
- User agent
- Device cookie ID
- Page URL
- IDFA or GAID for in-app events
- MD5 or SHA256 hashed email
- timestamp
- Purchase Metadata: Order ID, Amount, Discount Code, Product Name, etc
When the pixel on a brand’s site fires, it sends a request to our AWS servers located in the US. We receive incoming requests and store them in an encrypted format in our Kafka system, which is located in a private VPC. These requests have a Time-to-Live (TTL) of 7 days. We store the complete requests securely for a limited period because we are unable to process all the necessary data quickly enough to maintain a live HTTP connection.
If we receive raw emails (not hashed), we hash them upon receipt, and discard any other PII (other than IP address) in case anything was accidentally shared.
We then store the data in AWS data centers in the US, specifically US-east-1 and US-west-1, encrypting sensitive data. The data is destroyed in 5 years, or if no longer commercially useful, or if deletion is requeste
How can I pass my attribution results back to my MMP?
At the moment, this isn't possible. MMPs like Adjust and Appsflyer send Podscribe raw event data for attribution, but the results stay within Podscribe and aren't sent back. As a workaround, you can use the Individual Conversions CSV export or API to access your attributed conversion data.
Powered by