Tracya documentation

Tracya is a no-code onboarding builder for web apps. You create in-app guidance, tooltips, modals, highlights, and banners, by pointing at elements on your own pages, and it appears for your users through a small JavaScript snippet. No design tools, no engineering ticket for every change, no code beyond pasting the snippet once.

This documentation covers everything from first install to the finer points of triggers, theming, and the JavaScript API.

How Tracya fits together

Three pieces work together, and it helps to know which does what:

The snippet is a small script you add to your app once. It loads the widget and, from then on, displays whatever flows you have published. You never touch it again after installation.

The browser extension is how you build. It opens a sidebar on your own live app so you can select elements and design flows visually, on the real interface your users see. Nothing you build lives in the extension itself; flows are saved to your account.

The dashboard at app.tracya.io is where you manage everything else: your projects, your published flows, their theme, and their analytics.

Quick start

1. Add the snippet. In the dashboard, open the Projects tab, click Show snippet, and paste the two script tags into your app before the closing </body> tag. This is the only code step, and you do it once. Full details are on the Installation page.

2. Install the browser extension. Add Tracya from the Chrome Web Store or Firefox Add-ons, then connect it to your account with an extension token from the Account tab. The Browser extension page walks through it.

3. Build a flow. Open the extension on your app, click Open Builder, and design your first flow by selecting elements and adding steps. Click Publish flow when you are done. See Building flows.

That is the whole loop. Publish a flow, and it appears for your users on their next visit, according to the trigger you chose.

Where to go next

Installation covers the snippet in full: the init options, restricting which domains can load your flows, and Content Security Policy.

Browser extension is about installing and connecting the extension, and what it can and cannot see.

Building flows is the visual Builder in detail: selecting elements, the four step types, previewing, and publishing.

Flow triggers explains when a flow appears, first visit, every visit, once per session, or new users only, and how to limit a flow to specific pages.

Theming shows how to match each component to your brand, colour by colour, with a preview.

Analytics reads the funnel: how many people start a flow, how many finish, and where they drop off.

JavaScript API is the Tracya object your own code can call, for replaying flows and driving them programmatically.

Troubleshooting is the first place to look when a flow does not behave as expected.

A note on privacy

Tracya is built in the EU and keeps its data there. Its analytics are deliberately thin: flows are tracked against a random, per-browser ID and nothing personal, with no cookies used for analytics and no cross-site tracking. Your users get guided without being profiled, which is covered in more depth on the Analytics page.