Install on Podia
Two Podia text fields handle the entire install. Website tracking code carries the head script; Conversion tracking code fires the post-purchase event. No code outside Podia's admin.
Podia exposes two separate text fields for tracking integrations, both on the same admin page. The first carries the Rekomi head script for click capture. The second carries the conversion snippet with Liquid placeholders Podia substitutes at purchase time. Once both are in place, attribution works across every Podia product type (course, digital download, coaching, webinar, community) with no per-product configuration.
Install the tracking script
Podia does not expose a <head> slot; it injects this field's contents just before </body> instead. Because Rekomi's loader is async, the footer placement has zero performance impact.
Step 1. In Podia, open Settings > Site Settings > Analytics > Custom code > Website tracking code.
Step 2. Paste the Rekomi head script:
<script>
(function(){
var s=document.createElement('script');
s.src='https://js.rekomi.com/v1/rekomi.js';
s.async=true;
s.dataset.programId='YOUR_PROGRAM_ID';
document.head.appendChild(s);
})();
</script>Your program ID is in Rekomi's dashboard at Settings > Tracking. After saving, the script loads on every public Podia page (storefront, product pages, blog if applicable).
Install the conversion snippet
Right below the Website tracking code field on the same Podia page is a second field: Conversion tracking code. Podia fires this field's contents on every successful purchase, with Liquid placeholders hydrated to real values.
Step 1. In Podia, on the same Analytics page, find the Conversion tracking code field.
Step 2. Paste the convert snippet:
<script>
window.Rekomi && window.Rekomi.convert({
external_event_id: '{{order.id}}',
amount_cents: {{order.total_cents}},
currency: '{{order.currency}}',
customer_email: '{{customer.email}}',
});
</script>Podia's {{order.total_cents}} placeholder is already in cents (not decimal), so no multiplication is needed here. Podia substitutes all four placeholders at render time on the post-purchase page.
Save the field. The install is done.
How attribution works
The Website tracking code field loads rekomi.js on every visitor's first Podia-domain page, setting the first-party referral cookie based on the affiliate's link query string. When the buyer completes any purchase (course enrollment, downloadable buy, coaching session, webinar registration), Podia renders the Conversion tracking code field with hydrated placeholders and the convert event fires. Rekomi matches the cookie to the affiliate slug and credits the commission.
Quirks worth knowing
Podia owns the checkout subdomain. Checkouts happen on checkout.podia.com, not your custom Podia domain. The cookie was set on your Podia storefront before the buyer entered checkout; the conversion fires back on your storefront after checkout completes. The flow works because Podia routes the post-purchase page back to your Podia URL, where the conversion snippet runs.
One snippet covers every product type. Podia's checkout is unified across courses, downloadable products, coaching, webinars, and community memberships. The same Conversion tracking code field fires for all of them; you do not need per-product configuration.
order.total_cents is already in cents. Do not multiply by 100. Podia's Liquid placeholder gives you an integer like 4900 for a $49 purchase. Multiplying gives a 100x commission, which is the most common bug here.
The Custom code section is plan-gated. On some Podia plans (notably the legacy free or starter tiers), the Analytics > Custom code section is hidden. You need at least the Mover plan or equivalent for both Website tracking code and Conversion tracking code fields to appear. If you do not see them in your admin, check your plan.
Rekomi's async loader works in the footer. Podia injects the Website tracking code before </body>, not in <head>. Most analytics scripts work fine in either position; Rekomi specifically uses async loading so footer placement does not delay any first-paint metric.
Refunds
Podia uses Stripe for billing on standard accounts. Refunds fire charge.refunded to Rekomi's Stripe webhook listener and the commission reverses automatically. No additional Podia-side configuration needed in this case.
If your Podia account is on Podia-managed billing (rare; usually for grandfathered legacy accounts), refunds do not flow through your Stripe. Contact Rekomi support if you need a custom refund relay; the standard install assumes Stripe Connect.
Troubleshooting
Click cookie sets but conversion never fires. Confirm both Podia fields are filled in (Website tracking code AND Conversion tracking code). The most common cause of a missing conversion is that only one of the two fields is populated. Both are required.
Amount is 100x off on commissions. You multiplied Podia's order.total_cents Liquid placeholder by 100. Drop the multiplication; Podia already gives you cents.
Conversion fires for a different product than expected. Podia's checkout is unified; the conversion snippet fires on the post-purchase page regardless of which product type was bought. If you sell mixed products (a course and a digital download), use order.id as external_event_id (which is unique per order) so Rekomi treats them as distinct events.
Test purchases do not appear in Rekomi. Podia's test/preview mode does not fire the Conversion tracking code field. Use a real purchase (you can refund it immediately) to verify the install works end to end.
Related
Install on Outseta
Install the Rekomi script on Outseta's host platform so the affiliate cookie is set before sign-up, then rely on the Stripe webhook for conversion attribution.
Install on Teachable
Head snippet for click capture, plus a Liquid block on each Thank You page for the conversion event. Heads up that Teachable's head snippets don't run on the checkout subdomain, so affiliate links need to route through your marketing pages first.