Install on Podia

Create or select your website in Seean, then copy its snippet from Settings → Installation. Replace YOUR_SITE_TOKEN below with that website’s public token. Keep the external script and both data attributes; never put a server order API secret in this code.

Check third-party code access

Podia requires a supported plan and a verified account email for third-party code. From the home feed, open your site name and choose Admin. Go to Settings → Analytics, then edit Third-party code. Podia third-party apps.

Add Website tracking code

Paste the tag into Website tracking code and save:

<script defer src="https://app.seean.io/k.js"
  data-site="YOUR_SITE_TOKEN"
  data-api="https://app.seean.io"></script>

Podia inserts this code before the closing </body>, rather than in <head>. The Seean classic external tag can read its data attributes from that location. Keep it intact; do not use the separate conversion-tracking field for general pageviews.

Public and member pages

Website tracking code covers public site pages, including checkout, where Podia inserts it. It does not cover the logged-in home feed, customer dashboard, product viewer or community areas. Test the pages you actually need instead of assuming a site-wide setting covers member activity. Podia advanced analytics scope.

The conversion field runs in a purchase-related context, but adding Seean there does not create verified orders or a native Podia revenue connector. Use the server order API for supported order data after payment verification.

Save and verify

Visit the public site after saving. Check a product landing page and the checkout document without making a purchase merely to test pageviews. Test logged-out and logged-in navigation separately to identify where collection stops.

Open the published site in a browser and follow installation verification: confirm k.js loads, a collection request is sent, and the correct website and paths appear in Events. Check a direct page load, a link to a different pathname, and Back/Forward. Setup health shows the last received pageview time and offers a published-homepage check; it does not certify every page.

If events are missing, check the published HTML, consent settings, content blockers, CSP and exclusions. Install the tracker only once: a second tag, plugin or tag-manager installation can double count. Supported pathname navigation is automatic; do not add another pageview tag for every history change. Hash-only changes are not distinct pages.

Changes and removal

To change the site token, update this installation and publish again. To stop future collection, remove the same tag and publish; existing reports remain. Recheck installation after platform, theme or routing changes.

See script options, custom events and technical privacy. Loading this script must follow your site’s analytics-consent policy; a platform cookie banner does not necessarily control custom code automatically.

Something unclear? Contact support.