# Turnjo documentation > Turnjo helps businesses turn more website visitors into customers. One script on a site adds popups, surveys, guided tours, A/B tests and visitor feedback, all managed from one dashboard. --- Source: https://turnjo.com/docs/getting-started/overview # 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](https://turnjo.com/docs/popups/creating-popups.md)** — popup, corner, and banner widgets that collect leads, with targeting rules and [A/B testing](https://turnjo.com/docs/popups/ab-testing.md). - **[Experiments](https://turnjo.com/docs/experiments/overview.md)** — A/B test changes to your own pages (text, styles, visibility) and track conversions. - **[Guided tours](https://turnjo.com/docs/tours/overview.md)** — step-by-step walkthroughs for onboarding and feature announcements. - **[Visitor feedback](https://turnjo.com/docs/feedback/overview.md)** — a feedback button that collects comments, bug reports, and screenshots. - **[Integrations](https://turnjo.com/docs/integrations/overview.md)** — deliver leads to HubSpot, Shopify, Klaviyo, Mailchimp and more, or any [webhook](https://turnjo.com/docs/integrations/webhooks.md) endpoint. ## How it works 1. **Create a Property** — a Property represents one website. Turnjo generates a unique embed token for it. 2. **Install the script** — add one ` ``` Paste it into the `` 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: ```html ``` 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](https://turnjo.com/docs/getting-started/single-page-apps.md). Turnjo's own buttons and messages (Next, Send, error messages) follow each page's ``, in nine languages. You can reword any of them in Settings: see [Languages and visitor text](https://turnjo.com/docs/getting-started/visitor-language.md). ## 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 as `example.com`. - Ports are ignored, so a single `localhost` entry covers `localhost:3000` and 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). --- Source: https://turnjo.com/docs/getting-started/leads # Working with Leads Every time a visitor submits a Popup form, Turnjo records a lead. You can view, filter, export, and manage leads from the **Leads** page in your account. ## Viewing leads The Leads page shows all submissions across your account. Use the filters to narrow down by: - **Campaign** — show leads from a specific campaign - **Popup** — show leads from a specific widget - **Date range** — filter by submission date - **Search** — find a lead by email address Click any lead to open a detail drawer showing all submitted fields, the page URL where the form was filled in, and the Popup variant (if an A/B test was running). ## Duplicate leads If the same email address submits the same Popup more than once, subsequent submissions are marked as duplicates. Duplicates are hidden by default — toggle **Show duplicates** to include them. ## Exporting leads Click **Export CSV** to download all leads matching your current filters. The export includes email, campaign, Popup, variant, property, submission time, page URL, and all custom form fields. ## A copy of someone's data (GDPR) When someone asks what you hold about them, go to **Account settings** › **Lead data**, click **Export by email**, and download the file for their address. It holds their leads, survey answers and Chat conversations, and where each lead was sent. See [GDPR & data privacy](https://turnjo.com/docs/gdpr/overview.md#right-of-access). ## Erasing a lead (GDPR) To delete all records for an email address, go to **Account settings** › **Lead data**, click **Erase by email**, enter the address, and confirm. This permanently removes: - The lead record and all form data - Webhook delivery payload logs containing that lead's data CRM delivery audit records (status, timestamps) are retained without the personal data. This action cannot be undone. --- Source: https://turnjo.com/docs/getting-started/single-page-apps # Single-page apps Some sites change page without reloading: those built with React, Next.js, Vue, Nuxt, Angular, Svelte and similar. Turnjo notices those page changes on its own, so there's nothing extra to install. ## What happens when the page changes - **Popups, corner boxes, banners and surveys** are checked against the new page. One set to show on `/pricing` appears when the visitor reaches Pricing. One showing on a page it isn't set for closes. "Time on page" and "scroll depth" count from the new page. - **Tours** set to start on a page start when the visitor reaches it. - **Experiments** apply their changes to the new page. - **Chat** stays open across pages. The bubble hides on pages you've hidden it on, and Center Stage boxes on the new page are set up. - **Feedback** shows only on the pages you've chosen. Turnjo treats a change of path or query string as a new page, for example `/pricing` or `?plan=pro`. A hash change only counts when the site routes with it, like `#/pricing`. Jumping to an anchor such as `#faq` doesn't count. ## Apps that don't change the URL If your app swaps content without changing the address, tell Turnjo when the page has changed: ```js window.turnjo.page(); ``` Call it after the new content is on screen. --- Source: https://turnjo.com/docs/getting-started/visitor-language # Languages and visitor text Turnjo shows the text you write (popup copy, survey questions, tour steps, Chat greetings) exactly as you wrote it, in any language. Around that copy, Turnjo adds a few words of its own: Next and Back on tours, Send, "Step 2 of 5", error and status messages, the feedback widget, Chat's notes and contact card, and labels for screen readers. That's **visitor text**, and it can be in your visitors' language. ## Built-in languages English, Spanish, French, German, Portuguese, Italian, Dutch, Arabic and Hebrew. By default, Turnjo reads the language from each page's `` attribute, so `` (or `fr-CA`) gets French. A site with pages in several languages needs no setup, as long as each page declares its own. A page with no `lang`, or one in a language Turnjo doesn't have yet, shows English. To use one language everywhere, go to **Property → Settings → Visitor text** and choose it under **Language**. ## Changing the wording In **Settings → Visitor text**, pick the language under **Change the text in**, find the string, and type your own wording. Turnjo's text shows in grey in each empty field. Leave a field empty to keep it. Changes are per language, so you can also reword the English, say "Let's go" instead of "Next" to match your brand. Keep words in braces, like `{n}` and `{total}` in "Step {n} of {total}", where you want the number or name to appear. "Powered by Turnjo" is translated but can't be reworded. Changes reach visitors within about a minute, and in their next browser session if they've already visited. ## Right-to-left sites On Arabic and Hebrew pages, widgets follow your page's direction. Text that mixes directions, such as a Latin brand name inside an Arabic sentence, keeps its words in the right order. ## The Help page Chat's hosted Help page has no page of yours to read the language from. It uses the language set in Settings, or otherwise the visitor's browser language. Our translations are new. If something reads wrong in your language, change it in Settings and [let us know](mailto:support@turnjo.com). --- Source: https://turnjo.com/docs/popups/creating-popups # Creating and Configuring Popups A Popup is the widget shown to your visitors — popup, corner, or banner. Each Popup belongs to a Campaign, made for it automatically unless you group popups yourself, and has its own content, theme, form fields, triggers, targeting filters, and delivery settings. ## Popup types | Type | Description | |---|---| | **Center** | An overlay in the middle of the screen. High visibility; best for high-intent moments. | | **Corner** | Anchored to a corner of the viewport (any of the four). Less intrusive; good for persistent offers. | | **Banner** | Fixed bar at the top or bottom of the page. Works well for announcements or time-sensitive offers. | ## Creating a Popup 1. Go to **Popups** and click **New popup**. (To add one to an existing Campaign, open the Campaign and click **Add Popup**.) 2. Pick a starting point under **Start from**: Blank, a template from the Turnjo library, or one your team has saved. The popup is created straight away, named after the template, and opens in the editor with a live preview. 3. Change anything you like there: content, type and placement, theme, fields, triggers and targeting. Picked the wrong starting point? A popup that has never been shown can be deleted from the editor (**Delete**, top right). Once a popup has been shown or collected a lead, pause it instead: that keeps its leads and stats. 4. When you're ready for visitors to see it, click **Publish** in the editor. Publishing needs a confirmed email address. If you haven't clicked the link in your confirmation email yet, Turnjo remembers the click and publishes the Popup as soon as you confirm. Campaigns group popups and give them a schedule. You only need one of your own to run several popups together, or to start and stop them on set dates: **New campaign** on the Popups page. ### Templates A template is a reusable snapshot of a Popup's content, theme, and fields. To save one, open any Popup in the editor and click **Save as template** — it becomes available when creating a Popup on any of the account's Properties. Two things to know: - **Templates are copies, not links.** Editing a template later never changes Popups that were made from it, and editing those Popups never changes the template. - Templates don't carry triggers, targeting, frequency, or delivery settings — those are decisions about *where and when*, made per Popup. Saved templates can be deleted from the picker; Popups already made from them are not affected. ## The editor Building a Popup takes four steps, shown across the top of the editor. You can open any step at any time, and **Next** at the bottom of each suggests the order: 1. **Design**: Content (its screens and their blocks), Style & layout, and Form fields. 2. **Audience**: Triggers (when it appears, and how often) and Targeting (who sees it, and on which pages). 3. **Integrations**: where its leads go, and which field goes where. 4. **Publish**: a check of each step, what's changed since the last publish, and the Publish button. A/B tests start from here too, once the Popup is live. Within a step, the editor has three panes: - **Sections** (left): the current step's sections. - **Canvas** (center) — a live preview of the Popup on a mock of your page, exactly as visitors will see it. Click any block to edit it. Toggle **Desktop / Mobile** to preview both. In **Content**, the strip of screens above the canvas switches between the Popup's screens; see [Screens](https://turnjo.com/docs/popups/screens.md). - **Settings** (right) — the controls for the current section. Changes **autosave** a couple of seconds after you stop editing; the save bar in the corner shows the current state, and the Save button forces an immediate save. Undo and redo (Ctrl/Cmd+Z, Shift+Ctrl/Cmd+Z) cover your content edits. ### Editing a live Popup Once a Popup is live, your edits are saved as a **draft**: visitors keep seeing the published version until you publish the changes. The top of the editor always says which state you're in: - **Live**: what you see is what visitors see. - **Live · unpublished changes**: you've changed something visitors don't see yet. Click **Publish changes** to make it live, or **Discard** to go back to the published version. - **Not published**: nobody sees it, so edits save directly. **Publish** puts it live. The Popup's name isn't shown to visitors, so a new name saves straight away. The Content section is built from screens, and each screen from blocks: headings, text, images, buttons, the form, questions, and Columns for side-by-side layouts. See [Content Blocks and Layout](https://turnjo.com/docs/popups/content-blocks.md) for what each block does, how columns and their widths work, and what you can upload as an image, and [Screens](https://turnjo.com/docs/popups/screens.md) for popups in several steps. ## Style & layout The **Style & layout** section sets where the Popup sits on the page (its type and position) and styles the whole Popup: every screen shares one theme. - **Colors** — background and text, plus optional button, button text, link, and fine-print colors. Blocks without their own colors follow the theme, so changing the theme's button color restyles every button at once. A block can override any color individually; the field is labeled **Overrides the theme** and offers a ✕ to fall back again. - **Layout** — padding, corner radius, and max width. - **On phones (≤640px)** — optional mobile values for padding, corner radius, and max width. Anything you don't set inherits the desktop value. The canvas's **Mobile** toggle previews exactly what a phone will render. Columns blocks stack into one column at this same width — see [Content Blocks and Layout](https://turnjo.com/docs/popups/content-blocks.md). - **Close button (×)** — its color, size, an optional circle behind it (with its own opacity, so it can be see-through over a photo), and whether it sits inside the corner or on the edge of the Popup. With a circle and no color of its own, the × turns dark or light to stand out against the circle. You can turn it off: visitors can still close a centred Popup by clicking outside it or pressing Escape, and any Popup with a button set to **Close popup**. - **Typography** — headings and text blocks accept per-block size, weight, line height, letter-spacing, and spacing above/below, with a one-click **Reset to theme**. ## Fonts Set a default typeface for a Property under **Property → Settings → Branding**. It applies to every Popup, Tour, and the feedback widget on that Property. Any individual Popup can override it in **Style & layout**. There are three kinds of choice: | Option | What it does | |---|---| | **Match your site** | The widget inherits your page's own typeface. Nothing extra loads — usually the most seamless look. | | **System fonts** | Arial/Helvetica, Georgia, Times, Verdana, Trebuchet, Tahoma, Courier. Rendered from fonts the visitor's device already has, so nothing is downloaded. | | **Webfonts** | A curated set — Inter, Roboto, Open Sans, Lato, Montserrat, Poppins, Nunito, Work Sans, Source Sans 3, Merriweather, Lora, Playfair Display, JetBrains Mono. | A webfont is only downloaded when a widget that uses it actually appears on the page — one small file per weight, and never on page loads where nothing shows. Text stays visible while it loads (it renders in a fallback face first, then swaps), so a slow font never leaves a blank widget. **We host these fonts ourselves rather than loading them from Google Fonts.** Requesting fonts from Google would send every one of your visitors' IP addresses to a third party, which is a GDPR exposure and would undermine running Turnjo without a cookie-consent banner. Self-hosting means your visitors' browsers only ever talk to your site and ours. ## Closing without taking action Add a **Button** block and set **When clicked** to **Close popup** for a "No thanks" option. It closes the Popup like the ×, so the Popup's frequency limits treat it the same way. ## Form fields | Field type | Use for | |---|---| | Text | Name, company, or any short free-text input | | Email | Email address (always required; included by default) | | Phone | Phone number | | Consent checkbox | An explicit opt-in with a configurable label — use when the visitor is subscribing to marketing (e.g. a mailing list), where consent must be an action they take | | Consent statement | Notice-only fine print with no checkbox — use when the visitor is already asking you to contact them (e.g. a quote request), where a notice is enough and a checkbox only adds friction | For both consent types, write the label as plain text with optional markdown links: `I agree to the [Privacy Policy](https://yoursite.com/privacy)`. The link will be clickable in the rendered form. A statement never blocks submission; a required checkbox does. ## Triggers — when the Popup fires Triggers are the firing moment. A Popup can have several; it shows on the **first** trigger to fire. | Trigger | Description | |---|---| | On page load | Fires as soon as the page loads | | After time on page | Fires after N seconds | | At scroll depth | Fires when the visitor scrolls N% down the page | | On exit intent | On a computer, fires when the mouse leaves through the top of the window. On phones and tablets, which have no mouse, fires when the visitor scrolls quickly back up toward the top, or back to the top after reading down the page, and never in their first 10 seconds. A visitor who leaves without scrolling back up isn't caught, so on short pages a time or scroll trigger reaches more phone visitors. | | On element click | Fires when the visitor clicks an element matching a CSS selector | | When an element comes into view | Fires once any part of an element matching a CSS selector is on screen, e.g. the pricing table or the reviews | ### Frequency cap — Show again after New popups show **once per browser session**: a visitor who closes one doesn't see it again until their next visit. The **Show again after** setting — the Popup's *frequency cap* — holds it back once a visitor has seen it: | Setting | Behavior | |---|---| | Every page view | No cap: shows on every eligible page view | | Once per browser session | The default. Won't reappear until the visitor's next session | | After 3 more visits, or a number of visits… | Won't reappear until that many visits (browser sessions) after the one they saw it on, 1 to 99 | | After 5 more page views, or a number of page views… | Won't reappear until they've viewed that many more pages, 1 to 99 | | After 1, 3, 7, 14, 30 or 90 days, or a number of days… | Won't reappear within the window, counted from when they saw it, 1 to 999 days | | Never — show only once | One appearance per visitor, ever | The clock starts when the visitor **sees** the Popup, whether they dismiss it or just navigate away. Visitors who **submit** the form never see the Popup again, regardless of this setting. Appearances are recorded whatever the cap is set to, so tightening the cap later applies to appearances that already happened. Switching a long-running Popup from "Every page view" to "After 30 days" won't show it to a visitor who saw it last week — they're already inside the new window. ### After it's closed, show again **After it's closed, show again** sets how long a Popup stays away once a visitor closes it with the ×, Escape, a click outside it, or a **Close popup** button. The clock starts at the close. | Setting | Behavior | |---|---| | Use the setting above | Only **Show again after** applies | | On their next visit | Not again until the visitor's next browser session | | After 3 more visits, or a number of visits… | Not again until that many visits (browser sessions) after the one it was closed on, 1 to 99 | | After 5 more page views, or a number of page views… | Not again until the visitor has viewed that many more pages, 1 to 99 | | After 1, 3, 7, 14, 30 or 90 days | Not again until that many days after the close | | After a number of days… | Any number from 1 to 999 | | Never show it again | Once closed, it's gone for that visitor | Both settings apply: the Popup shows only when neither is holding it back. For example, "Every page view" with "After 7 days" keeps the Popup up on every page until the visitor closes it, then hides it for a week. Like the frequency cap, closes are remembered in the visitor's browser. ### Closes in analytics A Popup's analytics page shows how many times it was **Closed**, and what share of impressions that is. The close rate is also shown per Popup in a site's analytics (Popups by campaign) and in your account's Top Popups. A high close rate with few leads usually means the Popup shows too early, or to the wrong visitors. ## Targeting filters — who sees it Targeting filters limit who is eligible. They don't fire the Popup — that's the trigger's job — they decide whether a visitor qualifies at all. Targeting is per Popup. If you want to control which *sites* Turnjo runs on at all, that's the Property's [allowed domains](https://turnjo.com/docs/getting-started/overview.md) setting, not a targeting filter. | Filter | Description | |---|---| | Page URL | Pages whose URL contains — or doesn't contain — a specific string | | URL Parameter | Only when a query parameter (e.g. a UTM tag) is present or has a specific value | | Page content | Pages that have — or don't have — an element, some words, or a number in a range (see below) | | Visit Count | After N visits to the site | | Visitor Type | New or returning visitors | | Device Type | Desktop or mobile visitors | | Country / Region / ZIP + Radius | Visitors inside — or outside — a geographic area | | Another popup | Visitors who saw, closed, submitted, or chose Yes or No on another of this site's Popups — or never did | ### Targeting what's on the page The **Page content** filter shows a Popup only where the page has — or doesn't have — something: - **An element**: anything matching a CSS selector, such as `.out-of-stock` or `[data-category="flooring"]`. - **These words**: anywhere on the page, in the page title, in the main heading, or in a chosen element. Not case-sensitive. For example, show a kitchen planning guide on any article whose heading mentions *kitchen*. A phrase matches its words in that order, and by default inside longer words too: *product owner* also matches *product ownership*. Tick **Whole words only** to match it only as whole words. - **A number**: the first number in an element compared with a value, such as a cart total of at least 100 for a free-shipping offer. Prices are read however they're written: `$1,299.00`, `1.299,00 €`. Several **Page content** filters match if any one does, so add one per phrase to match any of several. Content that appears a moment after the page loads, as on many shops and single-page apps, still counts. It's all checked in the visitor's browser; nothing about the page is sent to Turnjo. For an element, type a selector or click **Pick on site**: your site opens in a new tab, you click the element, and the selector fills in. Prefer stable markers such as an `id` or a `data-` attribute; class names and wording can change when the site is redesigned, and the filter then stops matching. Add `?turnjo_debug=1` to a page's address to see in the browser console which filters match. ### Following up on another popup The **Another popup** filter lets one Popup follow another. Pick the Popup, what the visitor did with it, and whether they did it (**Visitor**) or never did (**Visitor never**). For example: - A discount corner card for visitors who **closed** the newsletter Popup. - A demo offer for visitors who **submitted** the lead magnet. - An exit-intent Popup for visitors who **never submitted** the main one. When the other one is a **survey**, you can also pick **answered it**, then a question and the answers that count: any of the listed options for a choice question, or a range for a rating or NPS score (for example 4 to 5 stars, or 9 to 10). That's how a discount goes only to happy customers, or a "talk to us" offer only to unhappy ones. Free-text questions can't be targeted, and their answers aren't kept in the browser. When Popups follow each other, **Targeting** shows a **Sequence** box: what this Popup follows, and which Popups follow it. The **Publish** step warns when a follow-up points at a Popup that's paused or deleted, when a follow-up shows on page load, and when another live Popup uses the same trigger with no show-again limit, so the two could show back to back. It's remembered in the visitor's browser, like the show-again settings. Give the follow-up its own trigger, such as time on page or a number of page views, so it doesn't appear the moment the first one closes. "Chose Yes / No" counts answers from when this filter was added. ### Including and excluding The URL and geographic filters each have a **Match** setting with two options: | Match | Meaning | |---|---| | **Contains** / **Is** | The visitor qualifies only if the rule matches | | **Doesn't contain** / **Is not** | The visitor qualifies only if the rule *doesn't* match | Use the negative form to keep a Popup off pages it shouldn't interrupt — a "Doesn't contain" rule of `/checkout/` keeps it away from your checkout flow while leaving it on every other page. **How filters combine:** it depends on whether a filter includes or excludes. - **Including filters of the same kind** match if **any** one does — two Country filters mean "either country". - **Excluding filters of the same kind** must **all** hold — excluding `/checkout/` and `/account/` keeps the Popup off both, not just one. - **Filters of different kinds** must **all** match — a Country filter plus a Device filter means "that country AND that device". So a URL "Contains `/pricing`" together with a URL "Doesn't contain `/pricing/enterprise`" shows the Popup across your pricing pages except the enterprise one. Leave filters empty to show the Popup to everyone the trigger fires for. ## Enabling and disabling Toggle a Popup active or inactive from the Campaign page or the Popup's editor. Inactive Popups are not shown to visitors and do not count toward impressions. --- Source: https://turnjo.com/docs/popups/content-blocks # Content Blocks and Layout Everything a visitor sees inside a Popup is built from blocks. Add them from the **Content** panel in the Popup editor, drag them to reorder, and click one to edit it. ## The blocks | Block | What it's for | |---|---| | **Heading** | A title. Choose the level (H2, H3) and alignment. | | **Text** | A paragraph or two of rich text — bold, italics, links, lists. | | **Image** | A picture. See **Images** below. | | **Button** | Opens a link, closes the Popup, or goes to a later screen (**When clicked**). Can run full width. | | **Spacer** | Blank vertical space, in pixels, when two blocks need separating. | | **Form** | The email field (and any other fields you've defined) plus the submit button. Each Form block can show only some of the fields, for a form on each of several screens. | | **Yes / No** | A two-button choice. "Yes" moves on to the next screen (or a web page); "No" closes the Popup. | | **Question** | Asks something: single or multiple choice, a 1 to 5 rating, a 0 to 10 recommend score, or a short answer. Its answer can decide which screen comes next. See [Screens](https://turnjo.com/docs/popups/screens.md). | | **Columns** | Puts other blocks side by side. See **Columns** below. | | **Countdown** | The time left until a date and time, or a set time for each visitor, ticking down. See **Countdown** below. | Blocks with no color or type settings of their own inherit the Popup's theme, so changing the theme restyles them. Setting a color on a block overrides the theme for that block only. ## Countdown A Countdown shows time running out, ticking every second. It counts one of two ways: - **To a date**: a sale that ends on Friday, an event, the last day to order before the holidays. The same for every visitor. Set **Counts down to** and **Time zone**, the moment it reaches zero; visitors anywhere see the right time left. - **Per visitor**: each visitor gets the same length of time, such as 15 minutes, from the first time they see the Popup. Their countdown keeps running across pages and visits on that browser, so coming back doesn't reset it. With consent mode on, until a visitor consents their countdown starts again on each page. Set the length in **Hours** and **Minutes**. The rest applies to both: - **Show**: days, hours, minutes and seconds, in any combination. A unit you hide carries into the next one shown, so without days, two days and three hours shows as 51 hours. - **Look**: numbers in **Boxes** or **Plain**, aligned left, center or right, with or without colons between them. - **Numbers**: font, weight, size and color. **Labels**: size and color, and your own words for each; left blank, they're in the visitor's language. - **Boxes**: their color and corner radius. - **When it reaches zero**: stop showing the Popup (the default), keep showing zeros, hide the countdown, or show a message instead. A Popup that's already open when it ends keeps its zeros. For a per-visitor countdown, stopping the Popup applies to each visitor when their own time runs out. A Countdown can go in a column like any other block, and on any screen, including a thank-you screen. ## Columns A Columns block arranges other blocks side by side instead of stacked. The usual case is a banner: a heading and a line of text on the left, the form on the right, all on one row. ### Setting it up 1. Add a **Columns** block. 2. Pick a **Layout** and an **Align**. 3. Choose a column with its tab, then fill it — add new blocks, or move in blocks you've already written (see below). The inspector edits **one column at a time**. Tabs across the top show each column's name, its share of the width and how many blocks it holds, and the block you open gets the panel's full width to lay its settings out in. ### Layout Six layouts, shown as tiles drawn in their own proportions: | Two columns | Three columns | |---|---| | 50/50 | 33/33/33 | | 60/40 | 25/50/25 | | 40/60 | | | 70/30 | | A banner with text on the left and a form on the right usually reads best at **60/40**. Switching layout never loses a block. Moving to more columns adds empty ones; moving to fewer moves the blocks from the columns that go away into the last column that remains, so you can rearrange them rather than retype them. Three columns is the maximum — past that there isn't enough width left for a form field to be usable, particularly in a corner Popup. ### Align **Top** lines the columns up at their top edges. **Center** centers them against each other, which is what you normally want in a banner so a heading sits level with the form beside it. Top is the default. ### Moving blocks you've already made You don't have to rebuild a block to put it in a column. Either: - **Drag** it from the Content list onto the tab of the column you want — the column doesn't have to be the one you're editing, or - use **Or move an existing block into…** below the block list and pick it. To move a block somewhere else, open it and use the **Move to** row: the other columns, or **Main list** to take it back out of the Columns block entirely. You can also drag it from the column back onto the Content list. A block moved out lands directly after the Columns block, so it keeps its place in the order rather than jumping to the end. Two blocks can't go in a column: - **Columns**, because nesting columns inside columns has no layout meaning here. - **Yes / No**, because it controls the whole Popup — it advances to a second step or closes it — which isn't something one column can own. A column tab will refuse the drop rather than accept it and do nothing. ### Working with the preview Click a column in the preview to jump to its tab. The column you're editing is outlined with a dashed line, so it's clear which one the settings belong to. The preview uses the same proportions as the layout you picked. ### On phones Columns sit side by side on desktop and **stack into a single full-width column on screens narrower than 640px** — the same breakpoint as the editor's Mobile preview. Nothing to configure; a two-column banner becomes two stacked rows on a phone, so the email field stays wide enough to type in. Check the **Mobile** preview before publishing: three columns of text stack into a tall banner, which is worth seeing before a visitor does. ## Images An Image block takes a picture from one of three places: - **Upload image** — upload from your computer. - **Media library** — reuse something already uploaded to this account. - Paste a URL directly, if the image is already hosted somewhere. ### What you can upload | | | |---|---| | **Formats** | JPG, PNG, GIF, WebP | | **Maximum size** | 5 MB | **SVG files are not accepted.** An SVG can carry scripts inside it, and these images are served from a domain your visitors trust, so we don't allow them. Export the artwork as PNG (or WebP, for a smaller file) instead. If you upload something outside the list you'll get a message saying so — nothing is stored. Always fill in **Alt text**: it describes the image to visitors using a screen reader, and it's what shows if the image fails to load. Leave it empty only when the image is purely decorative. The media library is per account, so every Popup on every property in the account can reuse what's in it. ### Edge to edge Tick **Edge to edge** to let an image run past the Popup's padding to its sides, like a header photo. When it's the first block on a screen it also reaches the top (with the Popup's rounded corners), and when it's the last, the bottom. Text, buttons and forms keep their padding. Width and alignment don't apply to an edge-to-edge image; it always fills the width. Inside a column, it fills the column. The close button (×) sits over an edge-to-edge image at the top. If it's hard to see against the picture, give it a background under **Style & layout**. ## See also - [Creating and Configuring Popups](https://turnjo.com/docs/popups/creating-popups.md) — types, triggers, targeting and theming. - [Screens](https://turnjo.com/docs/popups/screens.md) — popups in several steps, and where each screen leads. --- Source: https://turnjo.com/docs/popups/screens # Screens and Rules A Popup can be one screen, or a short path of them: ask what the visitor is shopping for, then ask for their email, then say thank you. Each screen is its own list of blocks, styled by the Popup's one theme. The visitor's answers and clicks decide which screen comes next. Surveys use the same screens. See [Surveys](https://turnjo.com/docs/surveys/overview.md). ## The screen strip The **Content** section of the editor shows a strip of the Popup's screens above the canvas. Click one to edit its blocks; the canvas previews it. **+ Screen** adds one of two kinds: - **Question screen**: shows something and moves on. A Popup can have up to six, counting the first. - **End screen**: where the visitor's path stops, such as a thank-you or a link to your shop. It asks nothing. Up to ten. Give a screen a name in its settings, under its blocks, so it's easy to pick later. **Delete screen** removes it along with the rules that lead to it. The first screen can't be deleted. **Map** shows the whole path at once: every screen, and the way from each one to the next. Click a card to open that screen. ## Moving on from a screen A visitor leaves a screen in one of these ways: - **The Form block's button.** Sending the form moves on. - **A Yes / No block's "Yes".** "No" closes the Popup. - **Tapping an answer**, when the screen asks a single question with one answer (single choice, rating or recommend score) and has no form. - **A Button set to Go to a screen.** It goes straight to the screen you pick, skipping the screen's rules. Required questions on that screen don't have to be answered, and a form on it isn't sent. A screen can also just show something with no way on: the visitor closes it, or follows a button's link. Visitors only move forward. A screen's rules and buttons can only lead to a later screen, so a Popup can't loop. ## Rules: where to go next Under a screen's blocks, **Next** says where the visitor goes when they move on. By default it's the next screen in the strip. To send people different ways by their answer, click **+ Add a rule**. A rule picks a question from this screen or an earlier one, the answers that count (any of the ticked options, or a range for a rating or recommend score), and where to go: a later screen, or **Leave for a web page**, which ends the Popup there. Rules are tried in order and the first that matches wins, so order them with the arrows. **Otherwise** says where everyone else goes. For example, on a "What are you shopping for?" screen: - If **Shopping for** is *Hardwood*, go to **Hardwood offer**. - If **Shopping for** is *Tile*, go to **Tile offer**. - Otherwise, the next screen. Short-answer questions can't be used in rules. ## Questions in a Popup Add a **Question** block to any screen to ask something: single choice, multiple choice, a 1 to 5 rating, a 0 to 10 recommend score, or a short answer. Answers are kept from the screen where the visitor leaves their email onwards. They're saved on the lead, and your integrations can map them like form fields. Answers given before that are only counted, so you can see how many people gave each answer on the Popup's **Analytics** page, but they aren't stored against anyone. Each Form block chooses which of the Popup's form fields it shows, so you can ask for an email on one screen and a phone number on a later one. ## When leads are sent to your integrations A lead is created as soon as the visitor sends a form with their email. It's sent to your integrations once, with everything they answered: - when they reach an end screen or leave for a web page, or - 10 minutes after they left their email, if they never finish. A Popup whose form goes straight to an end screen sends the lead at once. ## Seeing how visitors moved A Popup's **Analytics** page shows the same map with counts: how many reached each screen, how many left there, and how many took each way on. Below it are the answers counted on the way. ## A/B testing a popup with screens A variant replaces only the **first screen** and the theme. Every later screen and every rule is shared with the live Popup. A rule that depends on a question the variant doesn't have goes to its **Otherwise**. See [A/B Testing Popups](https://turnjo.com/docs/popups/ab-testing.md). --- Source: https://turnjo.com/docs/popups/ab-testing # A/B Testing Popups Popup A/B tests let you run two or more variants of a Popup simultaneously to find which performs better. Turnjo splits traffic between variants, tracks conversions, and can automatically conclude the test when a winner is found. ## How it works 1. In a Popup's editor, open the **A/B test** section and click **Create A/B Test**. 2. Name the test and choose what it's **judged on**: - **Became a lead** (the default) - **Clicked a button or link** - **Reached** a particular screen - **Finished** — reached the end of the popup The goal can't be changed once the test starts. 3. Check **How long will it take?** (below). Then set the stopping rules: confidence, minimum improvement (default 20%) and maximum duration (default 30 days). 4. Add variants and set their traffic weights. The original Popup content becomes the **reference** variant. 5. Click **Edit** on a variant to design it on the canvas — the same live preview you use for the Popup itself. A variant changes only the **first screen and the theme**; form fields and every later screen are shared with the live Popup. 6. Click **Start Test**. Variant edits are saved with an explicit **Save variant** button (no autosave) — while a test is running, a content change is a deliberate act, and you can optionally reset the variant's data at the same time if the change was meaningful enough to invalidate earlier results. ## How long will it take? The **New A/B Test** form estimates how many visitors each variant needs to find the minimum improvement you've set, and how many days that is at your Popup's traffic over the last two weeks. It starts from your current rate for the chosen goal, which you can change. If the estimate is longer than the maximum duration, the form tells you the smallest lift the test could find in time. Small lifts need a lot of traffic: at 200 visitors a day and a 5% rate, finding a 20% lift takes about 100 days, while a 40% lift takes about a month. Testing a bolder change, such as a new offer or headline, is usually the quickest way to a result. ## Stopping rules Turnjo checks running tests every 15 minutes. It concludes a test automatically when: - **A winner is found** — a variant beats the reference at your confidence level (default 95%) and improves on it by at least your minimum improvement (default 20%). Each side needs at least 100 visitors first. - **Maximum duration** is reached — the test has run for N days without a winner. Because results are checked so often, the bar a variant must clear starts high and falls as the test approaches its maximum duration. With several variants it's higher for each one. This keeps the chance of a false winner at your confidence level, however often the results are checked and however many variants you test. You can also pause or conclude a test manually at any time. ## Promoting a winner When a test concludes, open the A/B test section in the Popup's editor and click **Promote Winner**. The winning variant's blocks and style replace the Popup's default content and the test is archived. ## Viewing results Open **View full results** from the A/B test section. For each variant you'll see: - **Visitors** — each person counted once, however many times they saw the Popup. - **Converted** — visitors who reached the test's goal. For leads, duplicates of an earlier lead aren't counted. - **Rate** and **uplift** over the reference, with a **likely range** — for example "+18% (likely −4% to +40%)". While the range includes zero, the result isn't clear yet. - The **z-score** and the z-score needed to win right now. If the split between variants is further from their weights than chance would explain, the page warns you. That usually means something other than the test is deciding who's counted, such as a cached page or bots, and the results should be treated with caution. Tests started before visitors were counted show impressions instead. The **Analytics** page for a Popup shows each variant's impressions, leads and rate for the current date range. ## Traffic splitting Variants are assigned to visitors randomly at impression time using the configured weights. The assignment is sticky — a visitor who sees variant B will always see variant B on that property (stored in the browser's localStorage). --- Source: https://turnjo.com/docs/popups/troubleshooting # Why isn't my popup showing? Turnjo can tell you. Open the page on your site with `?turnjo_debug=1` on the end of the address, for example: ``` https://example.com/blog/my-post?turnjo_debug=1 ``` Then open your browser's console (right-click the page, choose **Inspect**, then the **Console** tab). Turnjo lists each popup with when and where it shows, and says why it is showing, waiting, or held back: - **Waiting**: its trigger hasn't fired yet, for example "after 15s on this page (6s so far)". - **Won't show on this page**: its targeting doesn't match, and Turnjo names the rule, for example `url contains "/pricing"`. - **Already seen**: it shows once per session, or every 7 or 30 days, and this browser has seen it. Type `turnjo.debugReset()` in the console and reload to see it again. - **Already submitted**: this browser filled in the form. `turnjo.debugReset()` forgets that too. - **Unpublished changes**: you've edited it, but haven't clicked **Publish changes**. Visitors see the published version. - **No live popups**: none are published for this site, or they're paused. - **Domain not allowed**: the site's **Allowed domains** don't include the one you're on, for example `www.` versus without it. Debug mode lasts for the browser tab and always loads the latest settings. Turn it off with `?turnjo_debug=0`. ## Without debug mode - **Changes take a new tab.** Turnjo keeps a site's settings for the browser session, so a tab that was already open keeps the old ones. Open a new tab or a private window after publishing. - **Time on page starts on each page.** A popup set to show after 15 seconds needs 15 seconds on the same page. - **The Page URL filter matches text exactly.** `/blog/` matches `/blog/my-post` but not `/blog` on its own. --- Source: https://turnjo.com/docs/surveys/overview # Surveys Surveys ask visitors a question or two on your site and show you what they said. Use one to learn whether people found what they came for, how likely they are to recommend you, or why they're leaving. A survey is built and shown the same way as a [Popup](https://turnjo.com/docs/popups/creating-popups.md). It uses your brand, can be a popup, corner box or banner, and has the same triggers and targeting. The difference is what it collects: answers rather than leads. A survey doesn't need an email address. Surveys use the same embed script as your Popups, so there's nothing extra to install. ## Starting a survey 1. Open a Property and choose **Surveys** in the menu. 2. Pick a template: - **Did you find what you needed?** One tap at the bottom of a page: Yes, Partly or No. - **How likely are you to recommend us?** The 0 to 10 recommend score, with an optional reason. - **What stopped you today?** Shown as visitors are about to leave, to learn what held them back. - **Rate your experience.** A five-star rating in the corner of the page. - **New survey.** One question and a Send button, to build from. 3. The survey opens in the editor, styled with your brand. Change the wording, add or remove questions, and set when and where it shows. 4. Click **Publish**. Visitors start seeing it within a minute. Nothing shows on your site until you publish. **Pause** takes a published survey off your site and keeps its results. ## Questions Add a **Question** block for each thing you want to ask. Each question has an answer type: | Answer type | What the visitor sees | What Results shows | | --- | --- | --- | | **Single choice** | A list of options; they pick one. | How many picked each option. | | **Multiple choice** | A list of options; they tick any. | How many ticked each option. | | **Rating (1 to 5)** | 1 to 5 stars. | The average and how many gave each score. | | **Recommend score (0 to 10)** | A row of buttons from 0 to 10, with your labels at each end. | The recommend score and how many gave each score. | | **Short answer** | A text box (up to 1,000 characters). | The answers, newest first. | Questions are required unless you untick **Required**. When a survey has a single choice, rating or recommend-score question and no Form block, the answer is sent as soon as the visitor picks it. With more than one question, or a multiple-choice or short-answer question, add a **Form** block for the Send button. ## Asking for an email A survey doesn't collect contact details unless you ask for them. To give visitors the option of leaving their email, for example so you can follow up, add an email field in the editor's **Email (optional)** section, and make sure the survey has a **Form** block. When a visitor leaves an email, Turnjo also creates a lead with the source **Survey**. It goes to your integrations like any other lead. Their answers stay linked to that lead. ### Sending answers to your email tools A survey has an **Integrations** step, like a Popup. Connect HubSpot, Klaviyo, Mailchimp or another tool there, and its **Field mapping** lists each question beside the form fields. Choose the contact property each answer goes to, for example a rating question to a "Satisfaction" number property. Then you can segment and email on the answer. #### Tags from answers For tools that use tags (Mailchimp, ActiveCampaign and Shopify), the integration also has **Tags from answers**. Each rule picks a question, the answers that count (any of the ticked options, or a range for a rating or NPS score), and a tag to add. For example, a rating of 1 to 2 adds **at-risk** and 4 to 5 adds **fan**. These tags are added alongside the integration's own **Tags**, and tags already on a contact are kept. Answers are sent only with a lead, so only when the visitor leaves their email. A rating or NPS score is sent as a number; several choices are sent as one comma-separated value. ## Screens and thank-yous by answer A survey can ask over several screens, and send people different ways by how they answered. It uses the same screens and rules as a Popup: the strip of screens above the canvas, **+ Screen** to add a question screen or an end screen, and rules under each screen's questions saying where to go next. See [Screens](https://turnjo.com/docs/popups/screens.md) for the details. To thank people differently by their answer, add an end screen for each case and a rule for each on the screen that asks. For example, on a five-star rating: - If **Rating** is from 4 to 5, go to an end screen saying "Thank you! Would you leave us a quick review?" with a **Leave a review** button linking to your Google review page. Or skip the screen and **Leave for a web page**, straight to the review page. - If **Rating** is from 1 to 2, go to an end screen saying "Sorry to hear that. Reply to our email and we'll make it right." - Otherwise, a plain thank-you. Answers are saved at each screen, so a visitor who stops partway still counts in Results, and the survey doesn't show to them again. ## Results Open **Results** from the survey list or the editor to see: - **Responses**, **times shown** and the **response rate**. - Each question, with its answers summarised as in the table above. - The **recommend score** for a 0 to 10 question: the percentage of promoters (9 to 10) minus the percentage of detractors (0 to 6), from −100 to +100. Filter by the last 7, 30 or 90 days, or all time, and by page (for example `/pricing`) to compare parts of your site. **Export CSV** downloads every response with its date, page and one column per question. ## Privacy Survey answers are kept like leads: for as long as you're on a paid plan, or 24 months on the Free plan, unless you set your own retention period. Erasing a lead by email also deletes the survey answers given with it. See [GDPR & privacy](https://turnjo.com/docs/gdpr/overview.md). --- Source: https://turnjo.com/docs/tours/overview # Guided Product Tours Tours walk visitors through your site with a sequence of tooltips — great for onboarding, feature announcements, or explaining a workflow. Each step can point at an element on the page, show text or rich content, and even include a video. Tours run through the same embed script as your Popups. ## Building a tour 1. Go to **Tours** and click **New tour**, then pick how it starts: a **Welcome message** (one step), a **Short walkthrough** (three steps), or **Blank**. The tour is created on your homepage and opens straight away. 2. Add steps. The easiest way is **Add steps on your site**: your site opens with a panel, you click the button, menu or section a step should point at, write the step there, and save. Or click **Write a step here** to add one in Turnjo. For each step you can set: - **Title** and **body** text (or use content blocks for richer layouts) - A **target element** to anchor the tooltip to, picked on your site or typed as a CSS selector. Leave it empty for a centered box. - **Placement**: auto, top, bottom, left, or right (auto picks the best fit) - A **page URL** to navigate to before showing the step (for multi-page tours) - **Spotlight**, to dim the rest of the page and highlight the target *(advanced)* - A **video**, from YouTube or Mux *(advanced)* - Custom **Next** / **Back** button labels 3. Click **Preview** to play it on your site, then **Publish** at the top of the tour's page. A tour needs at least one step to publish. Changes to when a tour starts and who sees it save as you go. ## When a tour appears Choose a trigger: - **When a page opens**: the tour starts automatically when the visitor lands on a matching page. Choose a match type — *matches* (exact), *starts with*, *contains*, *ends with*, *matches pattern* (`*` wildcards), or *matches regex* — and enter the value. Leave it blank to start on every page. - **When something is clicked**: the tour starts when the visitor clicks a specific element. You can also layer on an **Audience** — the same targeting rules used by Experiments and Popups (device type, visitor type, URL contains, time on page, scroll depth, visit count, exit intent, and location: country / region / ZIP radius). Rules of the same kind match if any one does; different kinds must all match for the tour to run. *Audience targeting is part of advanced tour features.* A visitor who finishes or dismisses a tour won't see it again. Multi-page tours resume where the visitor left off after navigating. ## Navigation Steps show "Step X of N" with Back and Next buttons; the last step's button reads **Finish**. Visitors can close a tour at any time with the dismiss button. ## Tracking Turnjo records tour events — started, advanced (per step), completed, and dismissed — so you can see how far visitors get. Completion analytics are available from the tour's page. ### Remembering completion across devices By default a finished tour is remembered in the visitor's browser, so it won't reappear on that device. If you tell Turnjo who a signed-in visitor is, completion is remembered on the server too — so a user who finishes a tour on their laptop won't see it again on their phone. Identify a visitor with their **stable user id** and a **signature** your server computes from it, so nobody can pose as another user by typing their id into the browser: 1. Copy the **identity secret** from the Property's **Settings → Identified Visitors**. Keep it on your server; never put it in page source. 2. On your server, compute an HMAC-SHA256 of the user id, keyed with the secret, as a hex string. 3. Add both to the Turnjo embed script tag: ```html ``` In PHP the signature is `hash_hmac('sha256', $userId, $secret)`; in Node, `crypto.createHmac('sha256', secret).update(userId).digest('hex')`. Instead of attributes you can set `window.turnjoUserId` and `window.turnjoUserHash` before the script loads. An id without a valid signature is ignored, and that visitor is treated as anonymous, with browser-only memory. If the secret leaks, **Regenerate secret** on the same page; signatures made with the old secret stop working immediately, so update your site at the same time. ## Plan limits Your plan caps how many tours you can create and how many steps each can have. Video, spotlight, and click triggers require a plan that includes advanced tour features. See [Billing & Plans](https://turnjo.com/docs/billing/overview.md). --- Source: https://turnjo.com/docs/experiments/overview # Experiments Experiments let you A/B test changes to your existing site — swap headline text, change a color, hide an element, or inject custom CSS — without editing your site's code. Turnjo splits traffic between variants, tracks a conversion goal, and can conclude the test automatically when a variant wins. Experiments are different from [Popup A/B tests](https://turnjo.com/docs/popups/ab-testing.md), which test variants of a Turnjo widget. Experiments change your own page elements. ## How it works 1. Go to **Experiments** and click **New experiment**. Give it a name, choose a **type** (*DOM changes* to edit the page visually, or *Split URL* to redirect to different pages) and the page it runs on. Traffic, statistics and audience are under **Advanced**; the defaults suit most tests. 2. Turnjo creates two variants: a **Control** (your site as-is) and **Variant B**, each at 50% weight. 3. Make your changes to Variant B and add a goal. An experiment can't start without a goal, or (for DOM tests) without at least one change on a variant. 4. Click **Start** at the top of the experiment's page. Settings save as you go. Visitors are assigned a variant at random according to the weights, and the assignment is sticky — a visitor keeps the same variant across visits (stored in their browser). A small blocking snippet hides the page until the variant's changes are applied, so visitors never see the original content flash first. ## Split URL tests A **Split URL** experiment sends a share of visitors to entirely different pages instead of editing the current one — perfect for comparing two separately-built landing pages. - The **entry page** (set under "Redirects visitors arriving on pages where") is the original page visitors arrive on (the Control). - Each non-control variant has a **Destination URL**. A visitor assigned to that variant is redirected there (and stays there on future visits, since the assignment is sticky). - Set a **goal** — usually a *Page visit* goal on a shared success URL (e.g. `/thank-you`). Because the assignment follows the visitor, a conversion on the destination or a later page is still credited to their variant. Add a destination to every variant before starting — Turnjo won't start a split-URL test with a missing destination. ## Variant changes (DOM-change experiments only.) Each non-control variant holds a list of changes. Every change targets an element by CSS selector (except Custom CSS): | Type | What it does | |---|---| | **Text** | Replaces the element's text | | **CSS** | Sets a single CSS property (e.g. `background-color`) on the element | | **Visibility** | Shows or hides the element | | **Image** | Swaps an image's source (must be an `https://` URL) | | **Custom CSS** | Injects a block of CSS into the page | A visual editor is available from the variant so you can point at elements on your own site. ## Targeting and audience - **Runs on pages where** — restrict the experiment to matching pages. Pick a match type — *matches* (exact), *starts with*, *contains*, *ends with*, *matches pattern* (`*` wildcards), or *matches regex* — and enter the value. Leave the value blank to run on every page. For the homepage, choose *matches* and enter `/`. - **Traffic** — enrol only a percentage of eligible visitors (1–100%). - **Audience** — layer on targeting rules: device type, visitor type, URL contains, time on page, scroll depth, visit count, exit intent, and location (country / region / ZIP radius). Rules of the same kind match if any one does; different kinds must all match. *Audience targeting requires a plan that includes it.* ## Goals and conversions Set a goal that defines a conversion. The first goal you add is the primary goal used to decide a winner. Goal types: - **Click** — a visitor clicks an element matching a selector. - **Page** — a visitor reaches a matching URL (e.g. a thank-you page), using the same match types as the experiment's page targeting. - **Custom event** — your site dispatches a `turnjo:goal` event with a matching name. Each visitor counts once per goal, so repeated clicks or page views aren't double-counted. ## Automatic conclusion Turnjo checks running experiments every 15 minutes and can conclude them for you: - **A winner is found** — a variant beats the control with statistical significance at your chosen confidence level (80/90/95/99%), once minimum sample size is reached (and at least 100 visitors on each side) and the improvement clears your minimum improvement (default 20%). - **Time runs out** — the experiment passes its maximum duration with no clear winner. Because results are checked so often, the bar a variant must clear starts high and falls as the experiment nears its maximum duration, and it's higher for each variant when there are several. This keeps the chance of a false winner at your confidence level however often results are checked. You can also pause or conclude an experiment manually at any time. When an experiment concludes, team members who've opted in are emailed. Tuning the confidence level and minimum sample size requires a plan that includes advanced experiment settings; otherwise confidence defaults to 95%. ## Results The **Results** page shows each variant's enrollments, conversions, conversion rate, uplift versus control with a likely range (for example "+18% (likely −4% to +40%)"), the z-score and the z-score needed right now, and an estimated completion date. It warns you if the split between variants is further from their weights than chance would explain, which usually means something other than the experiment (a redirect, a cached page, bots) is deciding who's counted. ## Plan limits Your plan caps how many experiments can run at once and how many variants each can have. See [Billing & Plans](https://turnjo.com/docs/billing/overview.md). --- Source: https://turnjo.com/docs/feedback/overview # Visitor Feedback Widget The feedback widget adds a floating button to your site that lets visitors send you comments, bug reports, and feature requests — optionally with a screenshot and recent console logs attached. Reports land on a triage board in your dashboard. The widget uses the same embed script as your Popups, so once the script is installed no extra code is needed. ## Enabling feedback Feedback is configured per Property and requires a plan that includes the **Visitor Feedback** feature. 1. Open a Property and go to its **Feedback** page. 2. Turn on the **Enable feedback** switch. (You'll see an "Upgrade required" note if your plan doesn't include the feature.) Once enabled, the widget appears on your site within about a minute. ## Configuring the widget From the Property's **Feedback** page you can set: | Setting | Options | |---|---| | **Launcher style** | Icon button or a text button | | **Icon** | Arrow, message, bug, sparkle, smile, or question | | **Launcher text** | Up to 30 characters (used when style is "text") | | **Position** | Bottom-left, bottom-right, top-left, or top-right | | **Edge spacing** | Distance from the edge in pixels (0–200) | | **Feedback form position** | Anchored to the launcher, or centered as a modal | | **Feedback types** | Any combination of Feedback, Bug, Feature request, and Question | ### Where the widget appears The **Page targeting** setting controls where the launcher shows: - **All pages** — everywhere the script is installed. - **Specific pages** — only on URLs containing a string you specify (e.g. `/pricing`). - **Query string** — only when a query parameter is present (e.g. `?feedback=1`), useful for internal or staged testing. - **Do not display** — hides the launcher entirely (for example while you configure it). ## What gets captured When a visitor submits feedback, the report includes their comment, the feedback type, and the page URL. Two options are shown as checkboxes in the form, both on by default: - **Attach a screenshot** — captured in the browser, so it reflects exactly what the visitor sees. - **Include recent console logs & browser info** — the last 50 console messages plus browser details (user agent, viewport and screen size, language). This is the visitor's disclosure and opt-out: if they uncheck it, no console logs or browser info are sent. Console logs are only ever captured on pages where the widget is active — the script never touches the console on sites or pages where feedback is turned off. ### Masking sensitive elements from screenshots What visitors typed in form fields — emails, card numbers, passwords — is always blanked out in screenshots, unless you turn on **Show what visitors typed in form fields** under **Privacy** (only if you need it to debug a form). If your pages show other sensitive data (an order summary, personal details), add CSS selectors under **Privacy** on the Feedback page. Matching elements are blanked out in the screenshot only — they keep working normally for the visitor. For example: `.card-number, #ssn-field`. You can also mark elements in your site's own code: anything with a `data-turnjo-mask` attribute is always blanked out, with no selectors needed. For example: `
…
`. ## Triaging reports The Feedback page includes a board with a column for each status: - **New** - **In progress** - **Resolved** - **Closed** Drag a card between columns to change its status, or assign a report to a team member from the card. Click a card to see the full comment, screenshot, console log, and browser info. Anyone with access to the Property can view and triage feedback. Enabling the widget and changing its appearance or privacy settings requires an admin (see [Team & Roles](https://turnjo.com/docs/team/overview.md)). --- Source: https://turnjo.com/docs/integrations/overview # Integrations overview Turnjo connects to the tools you already use. Integrations are set up once in **Account → Integrations**, then chosen per Popup, Survey or Chat. ## Send leads to | Tool | What happens | Guide | |---|---|---| | HubSpot | Contacts, added to a static list | [HubSpot](https://turnjo.com/docs/integrations/hubspot.md) | | Shopify | Customers, tagged and subscribed to email marketing | [Shopify](https://turnjo.com/docs/integrations/shopify.md) | | Klaviyo | Profiles, subscribed to a list with consent | [Klaviyo](https://turnjo.com/docs/integrations/klaviyo.md) | | Mailchimp | Audience members, with tags | [CRM integrations](https://turnjo.com/docs/integrations/crm.md) | | Brevo | Contacts, added to a list | [Brevo](https://turnjo.com/docs/integrations/brevo.md) | | ActiveCampaign | Contacts, with a list and tags | [ActiveCampaign](https://turnjo.com/docs/integrations/activecampaign.md) | | Loops | Contacts on a mailing list, and an event to start a Loop | [Loops](https://turnjo.com/docs/integrations/loops.md) | | SharpSpring | Leads | [CRM integrations](https://turnjo.com/docs/integrations/crm.md) | | Zapier | Any app Zapier connects to | [CRM integrations](https://turnjo.com/docs/integrations/crm.md) | | Your own endpoint | A signed JSON request | [Webhooks](https://turnjo.com/docs/integrations/webhooks.md) | Every lead is sent, a returning visitor's too, so the contact gets their new details. Integrations need a plan that includes CRM integrations. ## Get alerts in - **Slack**: new leads, Chat handoffs, visitor feedback and experiment results. See [Slack](https://turnjo.com/docs/integrations/slack.md). ## Send feedback to - **GitHub** and **Linear**: visitor feedback becomes an issue. See [GitHub](https://turnjo.com/docs/integrations/github.md) and [Linear](https://turnjo.com/docs/integrations/linear.md). ## Measure in - **Google Analytics & Tag Manager**: popup views, leads, survey answers and Chat opens as events. See [Google Analytics & Tag Manager](https://turnjo.com/docs/integrations/google-analytics.md). Using something else? Zapier and webhooks reach almost any other tool. --- Source: https://turnjo.com/docs/integrations/crm # CRM Integrations Turnjo can deliver leads directly to Mailchimp and SharpSpring as they come in. Credentials are configured once at the account level; field mapping is configured per Popup so each form can map to the right CRM fields. ## Setting up credentials 1. Go to **Account → Integrations**. 2. Click **Add Integration** and choose Mailchimp or SharpSpring. 3. Enter your credentials: - **Mailchimp** — API key and Audience (list) ID - **SharpSpring** — Account ID and Secret Key 4. Save. The integration is now available to connect to Popups. ## Connecting a Popup to an integration 1. Open the Popup in the editor and go to the **Integrations** step, then **CRM Integrations**. 2. Click **Connect** next to the account integration you want to use. 3. Configure **field mapping** — map each CRM field to the corresponding Popup form field name. 4. Enable the integration. From this point, every new lead from that Popup is delivered to the CRM automatically. ## Mailchimp Audience and tags Each Popup or Survey connected to Mailchimp can set its own: - **Audience ID**: leave it blank to use the default on the integration. - **Tags**: separated by commas, e.g. `spring-promo, popup`. Every contact from that form gets these tags in Mailchimp. A contact who's already in the Audience is updated and still gets the form's tags. This includes a returning visitor whose submission Turnjo marks as a duplicate: duplicates aren't counted as new leads, but they're still sent so the CRM gets any new details. SharpSpring works the same way: an email it already has updates that lead instead of creating a second one. Fields left blank on the form never clear what the CRM already holds. Every contact also gets a tag naming where it came from, for example `Turnjo: Spring newsletter`. Turnjo only adds tags; it never removes tags you've added in Mailchimp. Someone who unsubscribed stays unsubscribed. To change a connected integration's Audience or tags, click **Edit** next to it in the Popup's **Integrations** step. ## Chat leads Leads from Chat's Contact Card don't come from a Popup, so they have their own settings in **Chat → Settings → Lead delivery**. Choose which integrations they go to, and for Mailchimp, an Audience and tags (e.g. `chat`). Loops has a mailing list and an event instead. An integration turned on for the whole site in **Property → Settings → Lead delivery** also gets Chat leads; a lead is never sent to the same integration twice. ## Field mapping When you connect an integration to a Popup, Turnjo lists the Popup's fields, and each one gets a dropdown of that tool's own contact fields, read from your account: HubSpot's contact properties (custom ones included), your Mailchimp Audience's merge fields, Brevo's attributes, ActiveCampaign's fields, Loops' contact properties. You don't need to know any internal names, and your Popup's field names don't have to match the tool's. - Turnjo fills in its best guesses: a **Name** field is sent as **Full name**, split into first and last name; **Phone**, **Company** and the like go to the matching field. Change anything that's wrong. - **Don't send** leaves a field out. **Other…** lets you type a field's internal name if it isn't listed. - **Email** is always sent, so it isn't in the list. If Turnjo can't reach the tool to list its fields, the standard fields are still offered. To change the mapping later, click **Edit** next to the integration in the Popup's **Integrations** step. The editor marks the **Integrations** step with a dot when your account has integrations but the Popup isn't sending its leads to any of them. ## Delivery status CRM delivery attempts are logged. If a delivery fails (network error, invalid credentials, etc.), Turnjo retries automatically. You can see delivery status in the Popup's **Integrations** step. ## Webhooks For HubSpot and Loops, see the [HubSpot](https://turnjo.com/docs/integrations/hubspot.md) and [Loops](https://turnjo.com/docs/integrations/loops.md) articles. For other platforms, use **Webhooks** — Turnjo will POST lead data to any URL you specify with an HMAC signature for verification. See the [Webhooks article](https://turnjo.com/docs/integrations/webhooks.md) for details. --- Source: https://turnjo.com/docs/integrations/hubspot # HubSpot Send leads from Popups, Surveys and Chat to HubSpot as contacts. ## Before you start - You need a plan that includes CRM integrations, and to be an admin of your Turnjo account. - In HubSpot, you need to be a **Super Admin**, or have the **App Marketplace Access** permission, to connect an app. ## Connect HubSpot 1. Go to **Account → Integrations** and click **Add Integration**. 2. Choose **HubSpot**, then **Connect HubSpot**. 3. Sign in to HubSpot, choose the HubSpot account and approve access. HubSpot may warn that the app is **unverified**. That's expected while Turnjo's listing in the HubSpot App Marketplace is under review; you can continue. You come back to Turnjo with HubSpot connected. Connecting the same HubSpot account again refreshes the connection; it doesn't add a second one. ## Send a Popup's leads to HubSpot 1. Open the Popup and go to the **Integrations** step, then **CRM Integrations**. 2. Click **Connect** and choose your HubSpot integration. 3. Optionally set a **List ID**: contacts are added to that list. Use a static list. The ID is the number at the end of the list's address in HubSpot. Chat's leads have the same settings in **Chat → Settings → Lead delivery**. ## What's sent - The contact's **email**. HubSpot creates the contact, or updates the one it already has. - **First name**, **last name**, **phone** and **company**, from fields with those names (a `name` field is split into first and last name). - With field mapping, any other field. The name on the left is the HubSpot contact property's internal name, for example `jobtitle`. Fields left blank on the form never clear what HubSpot already holds. ## Seeing which leads came from Turnjo Turnjo adds a **Turnjo** group of contact properties to your HubSpot account the first time it sends a lead, and fills them on every lead: - **Turnjo popup**: the popup or survey they signed up through, or "Chat". - **Turnjo source**: Popup, Survey or Chat. - **Turnjo page**: the page they signed up on. - **Turnjo first conversion date**: when they first signed up through Turnjo, including contacts HubSpot already had (for example from its own tracking code). It's set once and never changes. Use them to filter contacts, build lists and report, for example "Turnjo popup is Spring newsletter". Popup and page show the latest sign-up. If you connected HubSpot before these properties were added, reconnect it once (**Account → Integrations → Add Integration → HubSpot**) so Turnjo can create them. Until then, leads are still sent, without them. Reconnecting makes Turnjo try again with the next lead. ## Troubleshooting - **"You don't have permission" in HubSpot:** ask a Super Admin to connect it, or to give you App Marketplace Access. - **A contact isn't added to the list:** check that the list is a static list, and that its ID is right. Lists that add contacts by their own rules can't be added to. - **Disconnecting:** remove the integration in **Account → Integrations**. To revoke Turnjo's access in HubSpot too, uninstall it under **Settings → Integrations → Connected apps**. --- Source: https://turnjo.com/docs/integrations/shopify # Shopify Send leads from Popups, Surveys and Chat to your Shopify store as customers, subscribed to email marketing. ## Connect Shopify 1. Go to **Account → Integrations** and click **Add Integration**. 2. Choose **Shopify** and enter your store's address, like `yourstore.myshopify.com`. Your own domain won't work here: use the myshopify.com address shown in Shopify under **Settings → Domains**. 3. Click **Connect Shopify**, sign in to Shopify and approve access. Connecting the same store again refreshes the connection; it doesn't add a second one. Uninstalling Turnjo in Shopify disconnects it. ## Send a Popup's leads to Shopify 1. Open the Popup and go to the **Integrations** step, then **CRM Integrations**. 2. Click **Connect** and choose your Shopify integration. 3. Optionally set **Tags**: added to every customer from this form, separated by commas, for example `spring-popup`. Use them for customer segments and discounts. Chat's leads have the same settings in **Chat → Settings → Lead delivery**. ## What's sent - The **email**. A new email becomes a customer; an email the store already has updates that customer. - **First name**, **last name** and **phone**. Shopify only accepts phone numbers in international format, like `+44 20 7946 0000`, so others are left out. - **Email marketing**: new customers are subscribed, and so are existing customers who never chose. Anyone who unsubscribed stays unsubscribed. Tags are only added, never removed, and fields left blank on the form never clear what the store has. --- Source: https://turnjo.com/docs/integrations/klaviyo # Klaviyo Send leads from Popups, Surveys and Chat to Klaviyo, and subscribe them to a list. ## Connect Klaviyo 1. In Klaviyo, go to **Settings → API keys** and create a **private API key**. Give it **Full access** to **Profiles**, **Lists** and **Subscriptions**. 2. In Turnjo, go to **Account → Integrations**, click **Add Integration** and choose **Klaviyo**. 3. Paste the key and save. ## Send a Popup's leads to Klaviyo 1. Open the Popup and go to the **Integrations** step, then **CRM Integrations**. 2. Click **Connect** and choose your Klaviyo integration. 3. Set the **List ID**. Find it in Klaviyo under **Audience → Lists & segments**, in the list's **Settings**. Each lead is subscribed to the list for email marketing, with Turnjo recorded as the consent source. Leave the list blank to save the profile without subscribing it. Chat's leads have the same settings in **Chat → Settings → Lead delivery**. ## What's sent - The **email**. Klaviyo creates the profile, or updates the one it already has. - **First name**, **last name**, **organization** (from a `company` field) and **phone number**. Klaviyo only accepts phone numbers in international format, like `+44 20 7946 0000`, so others are left out. - Where they came from, as profile properties: **turnjo_popup** (the popup or survey, or "Chat"), **turnjo_source** (Popup, Survey or Chat) and **turnjo_page** (the page they signed up on). Use them in segments and flows. - With field mapping, any other field. Use Klaviyo's names `first_name`, `last_name`, `phone_number`, `organization` or `title`; any other name becomes a custom property. --- Source: https://turnjo.com/docs/integrations/brevo # Brevo Send leads from Popups, Surveys and Chat to Brevo (formerly Sendinblue) as contacts. ## Connect Brevo 1. In Brevo, open the menu under your account name and go to **SMTP & API → API keys**. Create a key. 2. In Turnjo, go to **Account → Integrations**, click **Add Integration** and choose **Brevo**. 3. Paste the key and save. ## Send a Popup's leads to Brevo 1. Open the Popup and go to the **Integrations** step, then **CRM Integrations**. 2. Click **Connect** and choose your Brevo integration. 3. Set the **List ID**: contacts are added to that list. It's the number shown next to the list under **Contacts → Lists**. Chat's leads have the same settings in **Chat → Settings → Lead delivery**. ## What's sent - The **email**. Brevo creates the contact, or updates the one it already has. - **FIRSTNAME** and **LASTNAME**, from `first_name` and `last_name` fields, or split from a `name` field. - With field mapping, any other field. The name on the left is the Brevo contact attribute, for example `SMS` or `COMPANY`. The attribute must already exist in Brevo. --- Source: https://turnjo.com/docs/integrations/activecampaign # ActiveCampaign Send leads from Popups, Surveys and Chat to ActiveCampaign as contacts, with a list and tags. ## Connect ActiveCampaign 1. In ActiveCampaign, go to **Settings → Developer**. Copy the **URL** and the **Key**. 2. In Turnjo, go to **Account → Integrations**, click **Add Integration** and choose **ActiveCampaign**. 3. Paste the API URL (like `https://youraccount.api-us1.com`) and the key, then save. ## Send a Popup's leads to ActiveCampaign 1. Open the Popup and go to the **Integrations** step, then **CRM Integrations**. 2. Click **Connect** and choose your ActiveCampaign integration. 3. Optionally set: - **List ID**: contacts are subscribed to this list. It's the number in the list's address in ActiveCampaign. - **Tags**: added to every contact from this form, separated by commas. Tags that don't exist yet are created. Chat's leads have the same settings in **Chat → Settings → Lead delivery**. ## What's sent - The **email**. ActiveCampaign creates the contact, or updates the one it already has. - **First name**, **last name** and **phone**. - With field mapping, `firstName`, `lastName`, `phone`, or a custom field by its ID (the number under **Contacts → Fields**). Turnjo only adds tags; it never removes tags you've added in ActiveCampaign. --- Source: https://turnjo.com/docs/integrations/loops # Loops Send leads from Popups, Surveys and Chat to [Loops](https://loops.so), and start a Loop when someone signs up. ## Connect Loops 1. In Loops, go to **Settings → API** and create an API key. 2. In Turnjo, go to **Account → Integrations**, click **Add Integration** and choose **Loops**. 3. Paste the API key and save. ## Send a Popup's leads to Loops 1. Open the Popup and go to the **Integrations** step, then **CRM Integrations**. 2. Click **Connect** and choose your Loops integration. 3. Optionally set: - **Mailing list ID**: contacts are subscribed to this list. Find the ID in Loops under **Audience → Lists**. - **Event**: sent to Loops for every lead, for example `popup_signup`. Use it as the trigger of a Loop to send a welcome email. Chat's leads have the same settings in **Chat → Settings → Lead delivery**. ## What's sent - The contact's **email**. Loops creates the contact, or updates the one it already has. - **First and last name**, from a `first_name` and `last_name` field, or split from a `name` field. - Any other field you map. The name on the left is the Loops contact property, which must already exist in Loops. - **Source** is set to `Turnjo`. Someone who unsubscribed in Loops stays unsubscribed. A retried delivery never sends the event twice. --- Source: https://turnjo.com/docs/integrations/google-analytics # Google Analytics & Tag Manager Send Turnjo's events to the Google Analytics or Google Tag Manager already on your site, so popup views, leads and Chat show up next to the rest of your data. ## Turn it on 1. Open the site's **Settings** and find **Google Analytics & Tag Manager**. 2. Under **Send events to**, choose how your site loads Google Analytics: - **Google Tag Manager (dataLayer)** if Google Analytics runs through a Tag Manager container. - **Google Analytics 4 (gtag.js)** if the Google tag is pasted straight into your site. Choose only the one your site uses. Picking Tag Manager on a site that also loads gtag.js directly is fine; picking both isn't possible, so events are never counted twice. ## The events | Event | When | |---|---| | `turnjo_view` | A popup, slide-in, bar or survey is shown | | `turnjo_lead` | Someone submits a popup's form | | `turnjo_survey_submit` | Someone submits a survey | | `turnjo_chat_open` | A visitor opens Chat | Each event has two parameters: `turnjo_id`, the popup or survey's ID, and `turnjo_type`, what it is (for example `popup`, `slide_in` or `survey`; `chat` for Chat). ## With Google Tag Manager Events are pushed to the `dataLayer`. To pass them on to Google Analytics: 1. In Tag Manager, create a **Custom Event** trigger with the event name `turnjo_lead` (or use the regex `turnjo_.*` with **Use regex matching** for all of them). 2. Create two **Data Layer Variables**, `turnjo_id` and `turnjo_type`. 3. Create a **Google Analytics: GA4 Event** tag with the event name `{{Event}}`, add the two variables as parameters, and fire it on the trigger. 4. Submit and publish the container. ## With Google Analytics 4 Events are sent with `gtag('event', …)` and appear in **Reports → Engagement → Events** within a day (straight away in **DebugView**). To count leads as conversions, go to **Admin → Events** and mark `turnjo_lead` as a **key event**. To report on `turnjo_type`, add it as a custom dimension under **Admin → Custom definitions**. ## Consent These events only go to analytics your site has already loaded. If your consent banner holds Google Analytics back until the visitor agrees, Turnjo's events wait too. With [consent mode](https://turnjo.com/docs/gdpr/overview.md#consent-mode) on, Turnjo also holds its own events back until your banner reports consent. Events from before consent wait in memory on that page and are sent the moment the visitor consents there. If they decline, or leave the page first, those events are dropped and never sent. With consent mode off, events are sent straight away as before. --- Source: https://turnjo.com/docs/integrations/webhooks # Webhooks Webhooks let you receive lead data at any HTTP endpoint in real time. Turnjo signs every request so you can verify it came from Turnjo and not a third party. ## Adding a webhook 1. Open a Popup in the editor and go to the **Integrations** step. 2. Under **Webhooks**, click **Add Webhook**. 3. Enter a name and your endpoint URL. 4. Save — Turnjo generates a signing secret for this webhook. ## Payload Turnjo sends a JSON POST request to your endpoint for every lead submission: ```json { "event": "lead.submitted", "created_at": "2026-06-27T10:00:00Z", "source": "capture", "duplicate": false, "hook": { "id": 1, "name": "Homepage Popup", "type": "popup" }, "campaign": { "id": 1, "name": "Summer 2026" }, "lead": { "email": "visitor@example.com", "data": { "first_name": "Alex" }, "page_url": "https://yoursite.com/pricing", "submitted_at": "2026-06-27T10:00:00Z" } } ``` `duplicate` is `true` when this email has already sent a lead from the same form (or, for Chat, the same site). Update the record you already have rather than adding a new one. For a lead from Chat's Contact Card, `source` is `chat` and `hook` and `campaign` are `null`. Chat's webhooks are set in **Chat → Settings → Webhooks**. ## Verifying the signature Every request includes an `X-Turnjo-Signature` header: ``` X-Turnjo-Signature: sha256=abc123... ``` To verify it, compute `HMAC-SHA256` of the raw request body using the webhook's signing secret and compare it to the value in the header: ```php $expected = 'sha256=' . hash_hmac('sha256', $rawBody, $signingSecret); $valid = hash_equals($expected, $request->header('X-Turnjo-Signature')); ``` Reject any request where the signatures don't match. ## Retries If your endpoint returns a non-2xx status or times out, Turnjo retries the delivery up to 5 times with exponential backoff (1 min, 2 min, 3 min, 4 min, 5 min). ## Delivery log The last 20 deliveries for each webhook are shown in the Popup's **Integrations** step, including response status code, error details, and the lead's email. You can manually retry failed deliveries from there. ## Regenerating the signing secret If your secret is compromised, open the webhook in the Popup's **Integrations** step and click **Regenerate** next to its secret. Update your endpoint immediately — requests signed with the old secret will fail verification. --- Source: https://turnjo.com/docs/integrations/github # GitHub Send visitor feedback to GitHub as issues — complete with the screenshot, page URL, browser details, and console log — so your development team picks it up in the workflow they already use. ## Connect a repository 1. Go to **Integrations** (account settings). You'll need an **admin** role, and your plan must include visitor feedback. 2. In the **GitHub** card, click **Connect GitHub**. You'll be sent to GitHub to install the Turnjo app and choose which repositories it can access. 3. After installing, you'll land back on the Integrations page. Pick the **repository** issues should be filed in, add any **default labels**, and **Save**. Turnjo only ever stores the installation reference — never a personal access token. Issues are opened by the app, and you can revoke access at any time from your GitHub settings. ## Manual or automatic - **Manual (default).** Open a report on the feedback board and click **Send to GitHub**. Nothing leaves Turnjo until you choose to send it — good for teams that triage first and promote only the reports worth tracking. - **Automatic.** Turn on *"Automatically create an issue for every new feedback report"* in the GitHub card. Every new report is filed the moment it arrives. Best for lower-volume sites, or when every piece of feedback should land in your backlog. You can switch between the two at any time. ## What ends up in the issue Each issue includes: - The visitor's comment as the body, and a title summarizing it. - **Metadata**: feedback type, status, the page it was submitted from, browser and viewport. - The **screenshot**, embedded inline. - The captured **console log**, in a collapsible section. - A link back to the report on your Turnjo feedback board. A report is only ever filed once — sending the same report again (or retries behind the scenes) will never open a duplicate issue. Once filed, the report shows a **View issue** link. ## Route a property to its own repository By default every property files into the repository chosen above. To customize a specific property, open that **property's settings** → **GitHub routing** and pick a different repository — and, if you like, its own auto-create setting and labels. Other properties keep using the account default; switch back to *Use the account default* any time. Use **Apply to all properties** to copy one property's routing to every property at once. (The connection stays account-wide — routing only changes where and how issues are filed.) ## Disconnecting Use **Disconnect** in the GitHub card to stop filing issues. To fully remove the app's access to your code, also uninstall it from your organization's GitHub settings. --- Source: https://turnjo.com/docs/integrations/linear # Linear Send visitor feedback to Linear as issues — complete with the screenshot, page URL, browser details, and console log — so it lands straight in your team's backlog. ## Connect a team 1. Go to **Integrations** (account settings). You'll need an **admin** role, and your plan must include visitor feedback. 2. In the **Linear** card, click **Connect Linear**. You'll be sent to Linear to authorize the Turnjo app for your workspace. 3. Back on the Integrations page, pick the **team** issues should be filed in and **Save**. Issues are created by the Turnjo app (not as one of your users), and you can revoke access at any time from your Linear settings. ## Manual or automatic - **Manual (default).** Open a report on the feedback board and click **Send to Linear**. Nothing leaves Turnjo until you choose to send it. - **Automatic.** Turn on *"Automatically create an issue for every new feedback report"* in the Linear card, and every new report is filed the moment it arrives. You can switch between the two at any time, and connect **GitHub and Linear at the same time** — a report can be filed to both. ## What ends up in the issue Each issue includes the visitor's comment, the feedback type, the page it was submitted from, browser and viewport details, the captured console log, the screenshot, and a link back to the report on your Turnjo feedback board. A report is only ever filed once per tracker — retries and repeat clicks won't open duplicates. Once filed, the report shows a **View issue** link. ## Route a property to its own team By default every property files into the team chosen above. To customize a specific property, open that **property's settings** → **Linear routing** and pick another team — and, if you like, its own auto-create setting. Other properties keep using the account default; switch back to *Use the account default* any time. Use **Apply to all properties** to copy one property's routing to every property at once. (The connection stays account-wide — routing only changes where and how issues are filed.) ## Disconnecting Use **Disconnect** in the Linear card to stop filing issues. To fully revoke the app's access, also remove it from your Linear workspace settings. --- Source: https://turnjo.com/docs/integrations/slack # Slack Get a heads-up in Slack when things happen in Turnjo — new visitor feedback, concluded experiments, and @-mentions — and triage feedback right from the message. ## Connect a channel 1. Go to **Integrations** (account settings). You'll need an **admin** role. 2. In the **Slack** card, click **Connect Slack** and authorize the app for your workspace. 3. Back on the Integrations page, pick the **channel** to post to and choose which events you want. **Save**. If a channel isn't listed, invite the Turnjo app to it in Slack (`/invite @Turnjo`) and reload. ## What you can be notified about - **New visitor feedback** — posted to your channel with the comment, type, and page, plus **Mark in progress** / **Resolve** buttons that update the report in Turnjo without leaving Slack. - **A/B test / experiment concluded** — a message with the winner and a link to the results. - **Feedback @-mentions** — sent as a **direct message** to the mentioned teammate (matched by their email), mirroring the in-app mention. - **New lead** — each new lead from a Popup, Survey or Chat, with their name, email and where they signed up. Returning visitors aren't posted again. - **Chat visitor asks for a person** — a Chat handoff, with a link to the conversation so someone can pick it up. New lead and Chat handoff alerts are off until you turn them on. Each event has its own toggle, so you can keep the channel as noisy or quiet as you like. ## Route a property to its own channel By default every property posts to the channel you picked above. To customize a specific property, open that **property's settings** → **Slack routing** and choose *Customize for this property* — pick its channel and which events it posts (new feedback, experiment concluded). Other properties keep using the account default; choose *Use the account default* any time to revert. Use **Apply to all properties** to copy one property's routing to every property at once. (Mention DMs are always sent workspace-wide and aren't affected by per-property routing.) ## Acting from Slack The buttons on a feedback message change the report's status in Turnjo and update the Slack message to show who actioned it. Anyone in the channel can use them, so they're best in a team channel your Turnjo admins trust. ## Disconnecting Use **Disconnect** in the Slack card to stop all notifications. You can also remove the Turnjo app from your Slack workspace's settings to fully revoke access. --- Source: https://turnjo.com/docs/team/overview # Team & Roles Invite colleagues to your account and control what they can do with roles. Manage everything from **Team** in your account. ## Roles There are three roles, in order of privilege: | Role | What they can do | |---|---| | **Member** | View, create, edit, publish, and delete content (Popups, Experiments, Tours); view and export leads; view and triage feedback. | | **Admin** | Everything a member can do, plus: delete campaigns, erase leads (GDPR), manage integrations and webhooks, change account settings (data retention, branding, allowed domains), and manage the team. | | **Owner** | Everything an admin can do, plus owner-only actions: delete properties, cancel the subscription, delete the account, and transfer ownership. Each account has exactly one owner. | **Billing** is a separate permission. The owner can always manage billing and may grant an admin the ability to manage billing too. There's no read-only role — every member can create and edit content. The member/admin line is about destructive actions, exporting data off-platform, integrations, security settings, and team management. ## Inviting members 1. Go to **Team** and click **Invite**. 2. Enter the person's email and choose a role (Admin or Member). 3. They receive an email with a link to accept. The invite expires after **7 days**. You can revoke a pending invite before it's accepted. Each pending invite counts toward your plan's seat limit. ## Managing members - **Change a role** — switch someone between Admin and Member. Demoting an admin to member removes their billing access. - **Grant billing access** — the owner can let a specific admin manage billing. - **Remove a member** — detaches them from the account. - **Leave** — you can remove yourself from an account. The owner can't be removed, have their role changed, or leave directly — ownership must be **transferred** to another member first. When you transfer ownership, the previous owner becomes an admin. ## Seat limits Each plan includes a number of seats (members plus pending invites). If you hit the limit, remove a member or upgrade your plan. See [Billing & Plans](https://turnjo.com/docs/billing/overview.md). --- Source: https://turnjo.com/docs/billing/overview # Billing & Plans Turnjo is billed per plan, with usage measured in **monthly tracked visitors (MTV)**. Manage your plan, payment method, and usage from **Billing** in your account. Billing is available to the account owner and any admin the owner has granted billing access. ## Plans Plans range from a free tier up to Enterprise. Higher tiers raise your limits and unlock features: | Capability | Gated by plan | |---|---| | Monthly tracked visitors (MTV) allowance | Increases with tier | | Number of Properties (websites) | Increases with tier | | Team seats | Increases with tier | | Concurrent Experiments and variants per experiment | Increases with tier | | Number of Tours and steps per tour | Increases with tier | | Popup A/B testing, Webhooks, CRM integrations | Included from paid tiers | | Advanced experiment settings (audience targeting, confidence tuning) | Higher tiers | | Advanced tour features (video, spotlight, click triggers) | Higher tiers | | Remove "Powered by Turnjo" branding | Paid tiers | | Keep data while subscribed, or set your own retention period | Paid tiers | | Visitor Feedback widget | Plans that include the feature | | Priority support | Higher tiers | To change plan, open **Billing** and choose a plan — you'll be taken to a secure Stripe checkout. Enterprise is arranged with sales rather than self-service. Use **Manage billing** to open the Stripe portal, where you can update your card and download invoices. ## Monthly tracked visitors (MTV) MTV counts unique visitors to pages where your embed script runs, **once per visit session**. Counting is privacy-preserving: Turnjo stores only a salted, one-way hash derived from the visitor — nothing is written to the visitor's device, so no cookie-consent banner is needed for it. The salt rotates every billing period and is then destroyed, so visitors can't be re-identified or linked across periods. Your MTV period is anchored to your billing day (your signup or renewal date), not the calendar month. The **Billing** page shows your current usage against your allowance. Turnjo emails your team when usage crosses **90%** and **100%** of your allowance. ## Overage If you exceed your MTV allowance, what happens depends on whether you've opted in to overage: - **Overage opted in** — extra visitors are billed per 1,000 at your plan's overage rate, added to your next invoice at renewal. Turn this on from the **Billing** page. - **Not opted in** — you simply stay capped at your allowance for the period. Unlimited-allowance plans never incur overage. ## Payment problems and grace period If a payment fails or your subscription is canceled, your account enters a **7-day grace period** during which everything keeps working. Paying successfully clears the grace period. If the grace period passes without a successful payment, the account is downgraded to the Free plan and its limits apply. Re-subscribing at any time restores your plan. ## Data retention Paid plans keep leads and survey answers for as long as you're subscribed. The Free plan keeps them for **24 months**. On a paid plan, an admin can set a custom retention period instead. Moving to Free gives you 30 days' notice before older data is deleted. See [GDPR & Data Privacy](https://turnjo.com/docs/gdpr/overview.md). --- Source: https://turnjo.com/docs/gdpr/overview # GDPR & Data Privacy Turnjo includes several features to help you meet your obligations under GDPR and similar data protection regulations. Your legal team should review your specific requirements — this article explains the tools available to you. For an overview to share with your privacy team, including the services that process data for Turnjo and where it's hosted, see [Turnjo and the GDPR](/gdpr). ## Consent collection Use the **Consent** field type in your Popup forms to collect explicit consent from visitors before capturing their data. You control the exact wording — write your consent label to match your privacy policy and legal requirements. The label supports markdown links so you can link directly to your privacy policy: ``` I agree to the [Privacy Policy](https://yoursite.com/privacy) and consent to being contacted. ``` The consent checkbox value (`yes` or `no`) is recorded with every lead, giving you an auditable record of consent at submission time. ## Data retention How long Turnjo keeps leads and survey answers depends on your plan: - **Paid plans** keep them for as long as you're subscribed. - **The Free plan** keeps them for **24 months**. Anything older is deleted on the 1st of each month. On a paid plan, an admin can set a shorter or longer retention period, for example to match your own privacy policy: 1. Go to **Account → Settings**. 2. Under **Data Retention**, enter the number of months. 3. Save. Leads and survey answers older than that period are deleted on the next monthly purge. Leave the field blank to go back to your plan's default. **If you move to the Free plan**, including when a paid subscription is cancelled or lapses, nothing is deleted straight away. You get 30 days' notice: Turnjo emails your team with how many leads and survey answers are older than 24 months and the date they'll be deleted, and shows the same warning in Account → Settings. Choose a paid plan before then to keep them, or export your leads first. ### Visit events Records of what visitors did, such as a popup being shown, a Yes/No choice or a tour step, are kept for **13 months**. After that they're replaced by daily counts with no visitor details, so your analytics history stays complete. Anonymous visitor counts used for billing are kept for the current and previous billing period, then kept only as a total per month. ## Right to erasure To delete all data for a specific individual: 1. Go to **Leads**. 2. Click **Erase by Email**. 3. Enter the email address and confirm. This permanently deletes all lead records for that email, any survey answers and Chat conversations given with that email, and scrubs their data from webhook delivery logs. The action cannot be undone. ## Right of access When someone asks for a copy of the data you hold about them: 1. Go to **Account settings** › **Lead data**. 2. Click **Export by email**. 3. Enter the email address and download the file. The file (JSON) holds every lead for that email across your properties, with the fields and answers they gave, the consent wording they agreed to, their survey answers and Chat conversations, and where each lead was sent (your integrations and webhooks). Send it to the person who asked. Exporting and erasing need an account admin. ## What the embed stores in the visitor's browser Turnjo's embed sets no cookies. It does use the browser's own storage, scoped to your site, so that popups, experiments and tours behave consistently for each visitor. None of it is a cross-site identifier, and none of it is shared with other sites. The **With consent mode** column shows what happens before the visitor consents when [consent mode](#consent-mode) is on: **Stored** keys serve something the visitor asked for or remember a choice they made, and are stored as usual; **Waits** keys are kept in memory for the page only, until consent. **Session storage** is cleared when the visitor closes the tab: | Key | Purpose | With consent mode | |---|---|---| | `turnjo_visitor_{token}` | A random visitor identifier for the session, used to attribute experiment enrollments and tour progress. It's regenerated every session, so it can't link visits together. | Waits | | `turnjo_tracked_{token}` | A `1` flag so the visitor is counted for billing only once per session (see below). | Waits | | `turnjo_shown_{token}` | Popups shown this session, for the "once per session" frequency setting. | Waits | | `turnjo_closed_{token}` | Popups the visitor closed this session (consent mode only, see below). | Stored | | `turnjo_active_tour` | The tour and step in progress, so a tour resumes after a page change. | Stored | | `turnjo_geo_{token}` | Cached approximate location looked up from the visitor's IP address (country, region and coordinates, for location targeting). | Waits | | `turnjo_cfg_{token}` | The Property's configuration, to avoid refetching it on every page. | Stored | | `turnjo_chat_{token}` | The Chat conversation's opaque id, so the conversation continues across pages. | Stored | | `turnjo_chat_notice_{token}` | Whether the visitor dismissed the Chat privacy notice. | Stored | | `turnjo_chat_peek_{token}` | Whether Chat's greeting has already been shown this session, so it pops up only once. | Waits | | `turnjo_counts_{token}` | A `1` flag marking this session's visit as counted, for the "after N visits" settings. | Waits | | `turnjo_debug` | Set only when someone opens your site with `?turnjo_debug=1`, so Turnjo's debug messages stay on in that tab until `?turnjo_debug=0`. Meant for your team, not visitors. | Stored | **Local storage** persists until the visitor clears their browser data: | Key | Purpose | With consent mode | |---|---|---| | `turnjo_seen_{token}` | Popups the visitor has already submitted, so they aren't asked again. | Stored | | `turnjo_closed_{token}` | When the visitor closed each popup (consent mode only, see below). | Stored | | `turnjo_shown_{token}` | When each popup was last shown, for the 7-day, 30-day and "show once" frequency settings. | Waits | | `turnjo_visits_{token}` | A count of page views, for the "visit count" targeting rule. | Waits | | `turnjo_counts_{token}` | Running counts of page views and visits, for the "show again after N visits / page views" settings. | Waits | | `turnjo_closed_counts_{token}` | The visit and page view counts at which the visitor closed each popup, so a popup closed with an "after N visits / page views" limit stays closed for that long. | Stored | | `turnjo_shown_counts_{token}` | The visit and page view counts at which each popup was last shown, for the "after N visits / page views" frequency settings. | Waits | | `turnjo_choice_{token}` | The visitor's Yes/No answer to each popup that asks one, for targeting on it. | Waits | | `turnjo_answers_{token}` | The visitor's choice and rating answers to each survey, for targeting on them. Written (free-text) answers are never stored in the browser. | Waits | | `turnjo_cd_{token}` | When the visitor first saw each popup with a per-visitor countdown, so their countdown keeps running across pages and visits. | Waits | | `turnjo_hv_{id}`, `turnjo_exp_{id}` | The popup variant or experiment variant assigned to the visitor, so they see the same version on every visit. | Waits | | `turnjo_done_tour_{id}` | Tours the visitor has finished or dismissed. | Stored | Apart from the session's approximate location and survey choice and rating answers, these values hold only Turnjo ids, timestamps, counts and Yes/No answers. They never include anything the visitor typed. ## Consent mode Under the ePrivacy Directive and similar laws, storing information on a visitor's device (in browser storage as well as cookies) can require consent unless it's strictly necessary for something the visitor asked for. A/B tests, visit counting and impression-based frequency limits may not meet that test. Turn on **Consent mode** in the Property's **Settings** and Turnjo stores only the keys marked **Stored** above until your consent banner reports that the visitor has consented. Until then, Chat, Popups, Surveys and tours still work, but anything that needs to remember the visitor between pages can't: - **Popups without a close-based limit show again on every page until the visitor closes one.** Limits based on when a popup was shown ("once per session", "every 7 days", "after N page views") need storage, so before consent they count from when the visitor closes it instead. A popup closed with an "after N visits / page views" limit stays closed until the visitor consents, then counts from there. - **Lower-priority popups may not get a turn.** Only one popup shows at a time, and the first one to qualify shows again on each page, so another popup on the same pages may wait behind it until it's closed. - **Experiments need consent before the script loads.** A visitor is only enrolled, and only sees an A/B variant, once consent is known. Set `window.turnjoConsent = true` before embed.js for visitors who have already consented, so the right variant shows as the page loads. When consent arrives part-way through a page, Turnjo enrols the visitor then and applies their variant to the page already on screen (split-URL tests start from their next entry page); from then on every page shows their variant. - **Analytics treat each page as a new visitor.** The visit-count rule only sees the current page, the session visitor id is new on every page, and events for your own [Google Analytics or Tag Manager](https://turnjo.com/docs/integrations/google-analytics.md) wait on the page until consent, and are dropped if the visitor declines or leaves. ### Waiting only in Europe Consent Mode can wait for consent **everywhere** (the default) or **only in the EEA, the UK and Switzerland**, where the law requires consent before anything is stored. Choose under **Wait for consent** in the Consent Mode card. With **only in the EEA, UK and Switzerland**, visitors elsewhere are treated as having consented, so A/B tests, experiments and frequency limits work for them from their first page. The visitor's country comes from their IP address, looked up by our network edge; a visitor whose country can't be determined waits for consent. If your banner does report a refusal (`window.turnjoConsent = false`) for a visitor outside Europe, Turnjo still honours it. Some places outside Europe have their own rules. Check with your privacy adviser which setting fits your site. Tell Turnjo about consent from your banner's callback, on every page. Any of these works, whether or not embed.js has loaded yet: ```html ``` ```js // When the visitor accepts or withdraws, once embed.js has loaded: window.turnjo.consent(true); window.turnjo.consent(false); // Or, at any time, by setting the same value again: window.turnjoConsent = false; // Or, if your banner may answer before embed.js has loaded, through a queue Turnjo reads when it starts: window.turnjo = window.turnjo || {}; window.turnjo.q = window.turnjo.q || []; window.turnjo.q.push(['consent', true]); ``` On consent, everything waiting in memory for that page is stored, merged with anything stored when the visitor consented before, so earlier visits, closed popups and the variant they were shown are kept. On withdrawal, Turnjo deletes the **Waits** keys from the browser, even if the withdrawal arrives before Turnjo has finished loading. Turnjo doesn't remember the decision itself; your banner owns it. Classify Turnjo in your banner as functional or analytics, whichever matches your policy. Whether each **Stored** key is exempt where your visitors are is a legal judgement, so check this list with your legal team. ## Billing visitor counts For billing, Turnjo counts monthly tracked visitors. The only thing stored on the device is the per-session `turnjo_tracked_{token}` flag above, which holds no identifier (with consent mode on and no consent yet, not even that). On the server, Turnjo records only a salted, one-way hash of the visitor's IP address and browser type; the IP address itself is never stored. The salt is specific to your account and changes every billing period, and is destroyed about 40 days after the period starts, so visitors can't be re-identified or linked across periods. Hashes are kept for the current and previous billing period, then replaced by a total per month. Visitors are counted this way even before they consent, in consent mode too. Turnjo still shows them your popups, Chat and tours, so the visit is real use of the service, and counting it stores and reads nothing on their device. The hash is used only to count unique visitors for your bill, never to track or profile anyone, and isn't linked to leads or other visit records. ## Page addresses Visit records, leads, survey answers, feedback reports, Chat conversations and tour events note the page they came from. Turnjo sends that address without its query string or `#` fragment, which can carry personal details such as an email address or a reset token, keeping only the `utm_source`, `utm_medium`, `utm_campaign`, `utm_term` and `utm_content` campaign tags. Targeting rules still see the full address in the visitor's browser. ## Chat conversations If you use Chat, Turnjo keeps each conversation so your team can read it in **Conversations**: - **Messages.** What the visitor and Chat wrote. With **Sensitive details** turned on under Chat → Guardrails, card numbers, ID numbers and passwords are removed before a message is stored or sent to the AI, and the visitor is told. - **Who started it, for blocking.** A keyed hash of the visitor's IP address, specific to your Property, so it can't be turned back into the address or matched across sites, and a shortened version such as `203.0.113.x` for your team to recognise. These let you block a visitor from Chat; a block lasts 30 days. - **How long.** A conversation that ends in a lead is kept as long as that lead, and goes with it when the lead is erased or reaches your retention period. Any other conversation is deleted 90 days after its last message. Erasing a lead by email also deletes the Chat conversation that produced it. ## Survey answers If you use [Surveys](https://turnjo.com/docs/surveys/overview.md), Turnjo keeps each response so you can see it in **Results**: - **Answers.** What the visitor chose or wrote. Written answers can contain personal data if a visitor types it, so treat them as you would any other personal data you hold. - **Where and who.** The page the survey was answered on, and the embed's visitor id for that browser session (only while that id is stored, see above). A survey asks for an email only if you add an email field; giving one also creates a lead. - **How long.** Answers are deleted after your account's data retention period, and with the lead when a lead is erased by email. ## Visitor feedback data If you enable the [feedback widget](https://turnjo.com/docs/feedback/overview.md), submitted reports may include a screenshot of the page and recent browser console logs, which can contain personal data depending on your site. Visitors control this: the screenshot and diagnostics options are shown as checkboxes they can turn off before sending. What visitors typed in form fields (emails, card numbers, passwords) is hidden from screenshots by default. You can also mask other sensitive elements with CSS selectors on the Property's Feedback page, or with a `data-turnjo-mask` attribute in your markup. If you need typed values to debug a form, turn on **Show what visitors typed in form fields** there. Treat feedback reports as you would any other personal data you hold. Feedback reports, with their screenshots and your team's comments on them, are deleted after your account's [data retention period](#data-retention), on the same monthly purge as leads. A report doesn't ask for the visitor's email, so **Erase by Email** doesn't find it; if a visitor asks you to delete feedback they sent, delete the report from the Property's Feedback page. ## Webhook delivery logs Webhook delivery logs include the lead payload for debugging purposes. Payload data is automatically scrubbed from delivery logs after **90 days**. The delivery record itself (status, timestamps, error messages) is kept for **13 months** for audit purposes, then deleted. ## Data processors Integrations you connect receive data from Turnjo. Make sure you have appropriate Data Processing Agreements in place with those providers before enabling them. - **Lead destinations.** When you connect HubSpot, Klaviyo, Brevo, ActiveCampaign, Loops, Mailchimp, SharpSpring, Shopify or Zapier, or add a webhook, each lead (and the survey answers given with it) is sent there. - **Slack.** New leads, Chat handoffs and feedback reports can be posted to the Slack channel you choose. - **Feedback destinations.** When you connect Linear, GitHub or Slack for feedback, each report is sent there with the page address, browser details and, when the visitor left those options on, the screenshot link and console log. If you use Chat, visitors' messages and your site content are sent to the AI provider that answers them (Anthropic, or OpenAI if that model is chosen) to generate each reply. Those providers act as Turnjo's sub-processors and don't use the data to train their models.