Getting Started with Turnjo
Turnjo lets you add lead popup widgets, surveys, guided tours, on-site A/B experiments, and a feedback widget to any website by installing a single script tag. No per-page code changes are needed — everything is managed from the dashboard.
What you can do
- Popups — popup, corner, and banner widgets that collect leads, with targeting rules and A/B testing.
- Experiments — A/B test changes to your own pages (text, styles, visibility) and track conversions.
- Guided tours — step-by-step walkthroughs for onboarding and feature announcements.
- Visitor feedback — a feedback button that collects comments, bug reports, and screenshots.
- Integrations — deliver leads to HubSpot, Shopify, Klaviyo, Mailchimp and more, or any webhook endpoint.
How it works
- Create a Property — a Property represents one website. Turnjo generates a unique embed token for it.
- Install the script — add one
<script>tag to your site's<head>. It loads Turnjo and stays in place permanently. - Build Popups (and tours, experiments, feedback) — configure what to show, to whom, and when, all from the dashboard.
- Leads come in — submissions are stored in Turnjo, delivered to your CRM, and optionally sent to a webhook endpoint.
Which features you can use, and how many, depends on your plan.
Installing the embed script
Go to your Property's settings page and copy the snippet shown there. It looks like this:
<script async src="https://cdn.turnjo.com/embed.js?token=YOUR_PROPERTY_TOKEN"></script>
Paste it into the <head> of every page on your site, or add it once through your tag manager (Google Tag Manager, Segment, etc.). The token travels in the script URL, so this single line works everywhere — including tag managers.
Installing via a tag manager (Google Tag Manager, Segment)
Use the same one-line snippet above. Because the token is part of the script URL, there's nothing for the tag manager to strip and no load-ordering to get wrong — just add it as a Custom HTML tag firing on All Pages.
Older installs may instead set the token as a global before the script loads; this still works but is no longer necessary:
<script>window.turnjoToken = "YOUR_PROPERTY_TOKEN";</script>
<script async src="https://cdn.turnjo.com/embed.js"></script>
Once installed, anything you activate in the dashboard — Popups, Tours, Experiments, or the feedback widget — appears on your site within about a minute, with no further changes to the site. On the Property page, Verify installation confirms Turnjo has loaded (it checks whether the embed has actually called home, so it works for tag-manager installs too).
If your site changes page without reloading (React, Next.js, Vue and other single-page apps), there's nothing extra to install: see Single-page apps.
Turnjo's own buttons and messages (Next, Send, error messages) follow each page's <html lang>, in nine languages. You can reword any of them in Settings: see Languages and visitor text.
Restricting where the script runs
Your Property token travels in the script URL, so it is visible to anyone who views the source of your site. That's by design — it identifies the Property, it isn't a password — but it does mean the token could be pasted onto a site you don't control.
Property → Settings → Allowed domains is the lock. List the domains your widgets may run on, and Turnjo refuses everything else.
| Entry | Matches |
|---|---|
example.com |
example.com only |
*.example.com |
example.com and any subdomain — www., shop., staging. |
staging.example.com |
that subdomain only |
The most common mistake is adding example.com and finding the widget doesn't
run on www.example.com. They are different hosts. Either add both, or use
*.example.com, which covers the bare domain and every subdomain at once.
A few details worth knowing:
- Leaving the list empty means no restriction — the script runs anywhere it's installed. That's the default, and it's the right setting while you're still developing.
- You can paste a full URL.
https://example.com/is stored asexample.com. - Ports are ignored, so a single
localhostentry coverslocalhost:3000and friends during local development. - Changes take up to 10 minutes to take effect, because the list is cached. If you've just added a domain and the widget still isn't showing, wait before assuming it's wrong.
What gets blocked
Reading and writing are treated differently on purpose:
- Loading the widget is lenient. A request from a domain that isn't on the list is refused, but a request with no origin information at all is allowed through.
- Sending data — form submissions, impressions, tour and experiment events, feedback — is strict. A request from an unlisted domain, or with no origin at all, is refused.
That strictness is the point: real submissions come from a browser on your site, which always identifies where it came from. A script hitting the API directly doesn't, so a copied token can't be used to push fake leads or impressions into your account.
If you set a domain list and your own tooling talks to the embed API directly, it will be refused — that's the rule working, not a bug.
Accounts, Properties, and Campaigns
- Account — your organization in Turnjo. Holds your CRM credentials and billing settings.
- Property — one website. You can have multiple Properties per Account (e.g. your main site and a landing page subdomain).
- Campaign — a container for Popups with optional start and end dates. Use campaigns to organize seasonal or product-specific efforts.
- Popup — the actual widget shown to visitors (popup, corner, or banner).
More docs
Getting Started
Popups
Surveys
Guided Tours
Experiments
Visitor Feedback
Integrations
Team & Account
Billing & Plans
Privacy & Compliance