Install on Podia

Podia's Website tracking code field carries the Rekomi loader for click capture; sales record through your connected Stripe account and attribute by the lead you capture at signup, with a server-to-server relay as the fallback.

Podia exposes a custom-code field on its Analytics page that carries the Rekomi loader for click capture. The sale itself records through your own Stripe account: connect the same Stripe account to Podia and to Rekomi, then capture a lead at signup so the sale attributes by email match. Schools that cannot inject code, or that do not bill through their own Stripe, use the server-to-server relay instead. Once in place, this covers 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 > Analytics > Third-party code > Website tracking code.

Step 2. Paste the Rekomi loader:

<script async src="https://api.rekomi.com/api/v1/r/loader.js" data-program-id="YOUR_PROGRAM_ID"></script>

Copy the snippet with your program ID already filled in from Setup > Install in Rekomi. After saving, the loader runs on your public Podia pages (storefront, product pages, blog if applicable) and captures the affiliate click.

Record the conversion

The loader above only captures the affiliate click, and a click alone does not attribute a sale. There is no conversion snippet to paste in Podia's second custom-code field either: the browser convert() call that older setups used for sales was removed, and today convert() records leads, which is exactly what the working path below uses.

Stripe-billed Podia (recommended). Podia checkouts run through a Stripe account you connect to Podia. Connect that same Stripe account to Rekomi (Setup > Connect payment gateway, at /dashboard/setup/connect-sales) and sales, refunds, and cancellations record automatically. One scope note: the Stripe rail records subscription and invoice events, so products that bill as real Stripe subscriptions (memberships, payment plans) always land; a product Podia charges as a bare one-time card payment generates no Stripe invoice and may not. Place a test order for each product type and check the Sales page; anything that doesn't appear needs the S2S relay below, or a lead-based campaign instead. Crediting the affiliate takes one more piece: Podia's checkout cannot stamp Rekomi metadata onto the Stripe payment, so a first-time buyer attributes by matching the checkout email against a lead recorded in the last 90 days. Capture that lead at signup with window.Rekomi.convert({ email: "the-signup-email" }) from a page you control, or relay a signup webhook from your backend to POST /api/tracking/lead. See Track leads and signups.

Server-to-server relay. If your plan hides the custom-code field, or your Podia sales do not run through a Stripe account you can connect, relay each sale from your own backend to Rekomi's server-to-server endpoint. S2S and a live Stripe connection are mutually exclusive: the endpoint returns 409 while Stripe is connected, so pick one rail.

How attribution works

The Website tracking code field loads the Rekomi loader on the visitor's first page, capturing the referral from the affiliate link's query string. On the Stripe rail that click is never read server-side; attribution for a first-time buyer comes from the lead you record at signup (email match), and returning customers who were attributed once stay attributed. Podia's own coupon system never reaches Rekomi: a Podia coupon is not a Stripe promotion code, so creating a matching code in Podia does nothing for attribution.

Quirks worth knowing

Podia coupons are invisible to Rekomi. Rekomi coupon codes only attribute when redeemed as real Stripe promotion codes at a checkout running on your Rekomi-connected Stripe. Podia's checkout applies its own native coupons instead, so coupon-based attribution is not available here; use lead capture.

One conversion path covers every product type. Podia's checkout is unified across courses, downloadable products, coaching, webinars, and community memberships. The Stripe rail plus lead capture (or the S2S relay) attributes all of them; you do not need per-product configuration.

The custom-code field is plan-gated. On some Podia plans the Analytics custom-code section is hidden, so you cannot install the loader on Podia pages. Capture clicks and leads on a marketing site you control, or use the S2S relay.

Rekomi's async loader works in the footer. Podia injects the Website tracking code before </body>, not in <head>. Rekomi's loader is async, so footer placement does not delay any first-paint metric.

Refunds

If your Stripe account is connected to Rekomi, refunds fire charge.refunded to the Stripe rail and the commission reverses automatically; no Podia-side configuration is needed. If you record sales through the server-to-server relay instead, forward refund events from the same backend to /api/tracking/refund.

Troubleshooting

Click captured but no conversion is recorded. Confirm your Stripe account is connected in Rekomi (or your S2S relay is receiving order events). The Website tracking code field only captures the click; it does not record the sale on its own.

Sale recorded but no affiliate credited. No lead was recorded before checkout, the lead was older than 90 days, or the buyer paid with a different email than they signed up with. Verify the lead capture fires with the same email the buyer uses at checkout.

Test purchases do not appear in Rekomi. Podia's test/preview mode does not run the full checkout. Use a real purchase (you can refund it immediately) to verify the install works end to end.