Add Sumly to a Podia site

Podia has one box for third-party code on your public pages, checkout included. Paste Sumly's line there and the visits to your products and courses start to count.

Open the live demo Start free

Podiaone line, every page

Visitors

Admin › Settings › Analytics › Third-party code

<script defer src="…/s.js" data-site="sl_…">

✓ Saved First visit/ · from Google

Drawn with an example line.

Step by step

1
In Sumly, open Visitors and copy your project's line.
2
In Podia, click your site's name, then Admin › Settings › Analytics, and Edit next to Third-party code.
3
Paste the line into Website tracking code and Save.

The whole line, as Sumly shows it with your own key.

<script defer src="https://sumly.dev/s.js" data-site="sl_your_key"></script>

Or let your coding assistant do it

Paste this into Claude Code, Cursor or Codex in your project. It fits the code to how your project is built, asks you for the dashboard steps and leaves the keys to you.

See what it says

Set up Podia for Sumly in this project.

Sumly (https://sumly.dev) shows revenue next to the visits and app users it came from. The full guide is https://sumly.dev/install/podia; read it if anything below is unclear.

Steps:
1. In Sumly, open Visitors and copy your project's line.
2. In Podia, click your site's name, then Admin › Settings › Analytics, and Edit next to Third-party code.
3. Paste the line into Website tracking code and Save.

Website tracking code: The whole line, as Sumly shows it with your own key.
```
<script defer src="https://sumly.dev/s.js" data-site="sl_your_key"></script>
```

Keep in mind: Podia puts every tracking code just before the end of the page rather than in its head. Sumly's line works there too. It runs on your public pages and checkout, not inside the customer's dashboard, the product viewer or the community. Custom code needs a Podia plan that has it, not a trial, and a verified account email.

How to work:
- Look at how this project is built first, and fit the code to its framework and its way of doing things; the examples above are a starting point, not something to paste as is.
- Steps that happen in a dashboard (Sumly, or Podia's own) are mine: tell me exactly what to click, then wait for me.
- Keys the code needs belong in environment variables, never in the code or the repository. Never ask me to paste a secret key into this chat; tell me which variable to set.
- Change only what this needs, show me the changes before you commit, and tell me how to check that it works.
- sl_your_key stands for the project's public key; it is on the Visitors page in Sumly. Ask me for it.

Consent

In the EU, the EEA, the UK and Switzerland the script sets no cookie until you call sumly.consent(true), usually from your cookie banner once the visitor agrees, and counts visits without one until then. To wait for consent everywhere, add data-consent="always" to the line. Or add data-cookieless: no Sumly cookie anywhere, so nothing to ask, but a returning visitor counts as new each day and a payment is only traced to a visit on the same day.

Checkout

Podia takes the payment itself, so Sumly does not see it unless it goes through a payment provider Sumly reads. Stripe Payment Links on your pages do carry the visitor.

Your own domain

On Starter and Growth, one DNS record serves the script from your own address, past ad blockers: under Visitors › Add tracking › Your own address, enter one such as signal.your-site.com and add the CNAME it shows. If your checkout or app is on another domain, add it under Projects and payments › Other domains: the line then carries data-domains and one person stays one visitor across them.

Clicks and sections

Clicks on links to other sites count by themselves. Mark a button with data-sumly-event="signup" to count its clicks, and a section with data-sumly-scroll="pricing" to count the page views that reached it, a goal such as reached pricing.

Good to know

Podia puts every tracking code just before the end of the page rather than in its head. Sumly's line works there too.
It runs on your public pages and checkout, not inside the customer's dashboard, the product viewer or the community.
Custom code needs a Podia plan that has it, not a trial, and a verified account email.

From Podia's own documentation, checked 4 November 2026: help.podia.com/en/articles/11371020-installing-third-party-apps-on-your-podia-site .