If you use Google Tag Manager (GTM), see below for a step-by-step guide installing and configuring the Google Tag Manager Template.

☝

If you want to configure GTM manually without a template use this guide.

Setup Steps for the Google Tag Manager using Podscribe Template

You can add the template to your Google Workspace here or search for the Podscribe Template in the Gallery.

Step 1. Add a new tag using the Podscribe Template.

Select Add a new tag

Name your tag, for instance “ViewTag” or “Purchase”

Next, click in the tag configuration section of the page.

Select the Podscribe Template from the Custom section. If you do not see the template see next step.

To add the template select “discover more tag types from the Community Template Gallery” and search for Podscribe template)

Once template has been added and you can select it, enter your Advertiser ID, User ID, and what type of event this tag is for(view, purchase, signup, lead).

Ensure you replace any Macros with your own website variables.

☝

Here are the required fields you’ll need to fill out:

advertiser

user_id

event_type

Select the type of event or variable you want to track with this Podscribe pixel. Values accepted are purchase, view, signup, or lead.

Lastly, select the trigger section and select a trigger that you want. (for view tag you can use “All Pages”)

Step 2. Submit and publish the tag:

Once set up, you’ll need to publish the new tags on your website by clicking Submit, then Publish.

The screen will tell you that the latest version is live when done correctly:

To check if it’s firing correctly, visit the Network tab on your website. In the screenshot below, you can see that the view tag is firing on Podscribe’s home page:

Step 3. Tracking purchases:

The setup for the purchase tag is similar to the steps above. We recommend setting the purchase tag to fire on the post-checkout page rather than on any button.

The purchase action includes macros that send information like the order value and number. You’ll need to replace these macros with your site’s variables from GTM. If you’re unsure of your site’s macros, you can check other pixels on your site to identify them. These are likely data layer variables.

Thats it!

Additional information about our Template

Under Fields tab, you can view all fields that will be available when creating a tag from this template in the next step.

You can go into more_fields to add custom fields.

For questions, please email adops@podscribe.com.

Other Questions?

Can I use custom event while using the template? I want to create and track other events besides installs, views, signups, leads, and purchases.

Yes! You can create custom event values (e.g., "customView") and assign them to your custom tags. Here’s how:

Open the template and go to the code section.

Duplicate the existing action that best matches your custom one. For example, I duplicated the "view" tag and renamed it "customview". Be sure to update the name consistently throughout the script.

Go to the fields section and add a new dropdown option that links to your new custom event (e.g., "customview").

Now you can create a new tag with the "customView" event, and it will trigger your custom action ("customview") when fired.

The customView events will come into Podscribe as seen below:

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.

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.com

How 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

Sending Events via Google Tag Manager (GTM) by Template (Recommended)

Setup Steps for the Google Tag Manager using Podscribe Template

Step 1. Add a new tag using the Podscribe Template.

Step 2. Submit and publish the tag:

Step 3. Tracking purchases:

Additional information about our Template