Frequently Asked Questions

Paste one line of code into your site — the same way you'd add Google Analytics. No developer needed. Onboardics automatically starts mapping your user journeys the moment it's installed. The snippet collects page views, clicks, and navigation patterns. It does not capture passwords, payment information, keystrokes, or any form field content. See our SaaS Onboarding Audit Checklist for what to track.

The snippet tracks page views, clicks, scroll depth, and navigation paths — the same type of behavioral data as Google Analytics or Amplitude. It does NOT capture passwords, form input content, payment details, or personally identifiable information unless you explicitly pass it via the identify() method. All data is tied to anonymous session IDs by default.

Append ?_ob_debug=1 to your page URL and open DevTools console. The snippet logs every pushEvent call and every flush outcome with a [onboardics] prefix so you can filter. You can also toggle at runtime: window.__onboardics.setDebug(true). Common issues surface as always-on console warnings regardless of debug mode: missing data-key attribute on the script tag, duplicate installation (e.g. loaded via GTM and an inline tag), 401 invalid API key, 429 rate limit, or 5xx server errors. If you still can't see events, email tyler@onboardics.com with a screenshot of the console output.

Tooltip and tour flows anchor to a specific element via CSS selector. A daily check verifies each selector is still appearing in click event data. If none of the selectors in your flow have matched a click for 7+ days, the dashboard surfaces an amber “⚠ stale selector” badge on the flow card. Usual cause: your HTML was refactored, the target class or ID changed, or traffic to the element dried up. Easiest fix: open the flow editor, use the Describe the element in plain English option instead of hand-written CSS, and re-describe what the flow should target. AI re-resolves against current click data and picks a fresh stable selector — and re-resolves again if the HTML shifts later, so the flow stays alive through your next refactor. Alternatively, update the CSS selector manually if you already know the new target.

Yes. All data is encrypted in transit using TLS 1.2+ and encrypted at rest using AES-256. Your account data is logically isolated — every project goes through a shared authentication helper that verifies project ownership before returning any data, and a build-time check enforces this on every deploy so the rule cannot be bypassed by future code changes. We enforce strict access controls with row-level security policies, rate limiting on all API endpoints, and automated threat detection. See our Privacy Policy and DPA for full details.

Every customer's data is stored in isolated, access-controlled environments. We enforce row-level security so each account can only query its own data — there is no shared access between customers. All API endpoints require authentication, and we run automated security audits on our infrastructure. We are GDPR-compliant and provide a Data Processing Agreement (DPA) for customers who need one. We never sell, share, or use your data for advertising.

Yes. Onboardics is designed with privacy by default. We provide a Data Processing Agreement (DPA) for GDPR compliance, honor data deletion requests, and support data retention policies per plan tier. We do not sell personal data, and our cookie consent integration works with your existing consent management platform. See our Privacy Policy, DPA, and Cookie Policy for full details.

Your data is retained for 30 days after cancellation, giving you time to export or reactivate. After 30 days, all project data is permanently deleted from our systems. You can request immediate deletion at any time by contacting tyler@onboardics.com.

Any unique user who visits a page where your Onboardics snippet is installed during a given month.

We surface usage warnings at 80% and 100% of your plan's included MAU. Upgrade to increase your included MAU and keep usage aligned with your plan. View our pricing.

Yes. The snippet is framework-agnostic vanilla JavaScript. It works with any web-based product.

Click “Diagnose drop-off” on any analytics page — funnel, activation, adoption, paths, retention, or events. Our AI analyzes seven data dimensions including drop-off rates, exit pages, navigation paths, rage clicks, time-on-page patterns, and weekly trends. It gives you a plain-English explanation of why users leave, with three specific fix recommendations ranked by impact and effort. Each recommendation includes suggested copy and CSS selectors so your engineering team can ship in code on any tier — or, when the fix is overlay-able (Deploy and above), click the “Create flow” button to auto-generate an in-app fix with one click. Some fixes need a redesign rather than an overlay (form simplification, removing fields, real product changes) — those are flagged code-only. We never wedge a flow where it doesn’t belong. See how AI diagnosis works in practice.

Tooltips, guided tours, modals, and checklists that appear inside your product to guide users. You build them with our no-code visual editor — no developer required. Flows are triggered by user behavior, so they show the right guidance at the right moment.

Go to Settings → Define Your Metrics and describe what success looks like in plain English. For example: "Activation means they booked a consultation. Retention means they came back within 30 days." Our AI analyzes your actual event data and maps your descriptions to trackable conditions — no event tagging or engineering work required. Your custom definitions update all dashboard metrics automatically.

No. Onboardics focuses on in-app guidance — tooltips, modals, banners, tours, and checklists that appear inside your product. We don't send emails to your users. If you use an email platform like Customer.io, Loops, or Klaviyo, you can use Onboardics analytics to inform your email strategy, but the delivery stays in your existing tools.

Yes. Start with the free tier to see your funnel data and explore the dashboard. When you're ready, you can upgrade to any paid plan and downgrade or cancel anytime — no contracts, no cancellation fees. Try the live interactive demo to see the full product in action — no signup required.

Yes. Click Heatmaps show element-level click density on every page in your product, ranked by frequency with color intensity indicators. Built-in AI diagnosis identifies broken elements, dead zones, rage clicks, and underperforming CTAs — and suggests specific fixes you can ship in code (Diagnose) or, on Deploy and above, deploy as a no-code flow. Available on Diagnose, Deploy, Scale, and Business tiers. View your heatmaps (requires Diagnose plan or above).

Yes. Every Onboardics project supports unlimited apps. Add separate snippets for your marketing site, product app, mobile web, and staging environments — all unified in one dashboard. Multi-app is included on every plan, including the free tier.

Yes. When you install the snippet, it detects whether you're running Next.js, Nuxt, Shopify, WordPress, Webflow, SvelteKit, Vue, or React and pre-selects the correct install tab on the dashboard. You can still manually switch tabs if the detection is wrong. This works on your first page view with no configuration required.

Onboardics automatically detects your funnel from the pages users visit most often, excluding common non-funnel pages like FAQ, About, Privacy Policy, Terms, Blog, and Contact, and force-including conversion pages like /checkout/success, /booking/confirmed, /welcome, or /thank-you as the final step. If the auto-detected funnel doesn't match your actual flow, customize it in Settings → Funnel Definition: drag to reorder, rename, add missing stages, or remove ones that don't belong.

No. The free tier is free forever — no credit card required.

Yes. Every project admin can disable the tracking snippet from Settings → Pause tracking. It takes effect within about 30 seconds — our events endpoint responds with a kill signal on the snippet's next request, halting collection across your site. Existing data stays intact; you just stop adding new events. Common reasons to pause include major redesigns (avoiding test-data pollution), deployment windows (clean before/after baselines), load tests (not skewing real-user data), compliance or legal holds, or isolating the snippet while investigating a suspected site conflict. Resume from the same section any time — tracking begins flowing again on each visitor's next page load. Available on every tier.

First, invoke your pause control at Settings → Pause tracking — this halts the snippet across your site within ~30 seconds. Then email tyler@onboardics.com with what you're seeing (error messages, browser, affected pages) and we'll investigate. We monitor our own Sentry in real time for snippet errors tagged by customer domain, so we likely already know if something broader is happening. The snippet itself includes a per-browser circuit breaker that auto-disables in any visitor's browser that emits more than 20 internal errors in 10 seconds, so worst-case breakage is self-limiting at the browser level.