Seentics Documentation

Welcome to Seentics - a comprehensive analytics and workflow automation platform. Track visitor behavior, create conversion funnels, and automate responses with intelligent workflows. This guide covers everything from basic setup to advanced integrations.

Analytics

Real-time visitor tracking, custom events, and performance insights

Funnels

Sequential conversion tracking with dropoff analysis

Workflows

Automated responses to user behavior and funnel events

Installation

Getting Seentics onto your website is incredibly simple. All it takes is a single line of code.

Navigate to the Websites page in your Seentics dashboard.
For your desired website, click the "Tracking Code" button.
Copy the provided script tag. It will look something like this:

<!-- Paste this before the closing </head> tag on your site -->
<script
  defer
  src="https://seentics.com/trackers/tracker.js"
  data-website-id="YOUR_WEBSITE_ID">
</script>

Paste this snippet into the <head> section of your website's HTML. Once the script is added, Seentics will immediately begin tracking visitors and become ready to execute any active workflows you've created for that site.

Analytics

Visitor Tracking

Seentics automatically tracks visitor behavior once the tracking script is installed:

Page views: Every page visit with URL and timestamp
Session tracking: Groups page views into user sessions
Device detection: Mobile, tablet, or desktop classification
Traffic sources: Referrer and UTM parameter tracking
Geographic data: Country and region information

Custom Events

Track specific user actions beyond page views:

window.seentics.track('button_click');

Common event examples:

form_submit - Form submissions
video_play - Video interactions
download_start - File downloads
signup_complete - User registrations

Real-time Data

View analytics data as it happens:

Live visitor count: See current active users
Real-time events: Track events as they occur
Funnel progression: Monitor conversions in real-time
Workflow triggers: See automations as they execute

Workflows

Workflows automate responses to user behavior. They consist of Triggers, Conditions, and Actions that work together to create intelligent automations.

Triggers: The "When"

Triggers are the events that initiate a workflow. They are the "when" something should happen.

Page View: Fires when a user lands on a page
Element Click: Fires when a user clicks a specific element
Time Spent: Fires after a user has been on a page for specified seconds
Exit Intent: Fires when mouse moves toward browser top (leaving)
Funnel: Fires on funnel events (dropoff or conversion)

Conditions: The "If"

Conditions are rules that must be met for a workflow to proceed. They are the "if" statement in your automation. If a condition fails, the workflow stops at that point for that specific user session.

URL Path: Checks if the user is on a specific page or section of your site (e.g., URL contains `/checkout`).
Device Type: Checks if the user is on a desktop or mobile device.
New vs. Returning Visitor: Checks if it's the user's first time visiting your site.
Tag: Checks if the visitor has a specific tag that was applied in another workflow.

Actions: The "What"

Actions define what happens when triggers fire and conditions are met.

Show Modal: Display popup modal with custom content
Show Banner: Display banner at top or bottom of page
Track Event: Send custom event to analytics
Webhook: Send data to external URL for integrations
Redirect URL: Navigate user to different page

Funnel Triggers

Funnel triggers allow workflows to respond to specific funnel events:

Dropoff: Triggers when a user leaves a funnel without completing it
Conversion: Triggers when a user successfully completes a funnel

Use funnel triggers to create targeted responses like exit-intent offers for dropoffs or thank-you messages for conversions.

Funnels

Funnels help you track user journeys through specific conversion paths on your website. Monitor where users drop off and optimize your conversion rates.

Creating Funnels

Create multi-step funnels to track user progression through your conversion process:

Go to your website's Funnels page
Click "Create Funnel" and give it a descriptive name
Add steps by defining page URLs or custom events
Set up step conditions (exact match, contains, starts with)
Activate the funnel to start tracking

Funnel Tracking

Seentics automatically tracks funnel progression with sequential validation:

Sequential progression: Users must complete steps in order
Dropoff detection: Tracks when users leave the funnel
Conversion tracking: Measures completion rates for each step
Real-time monitoring: See funnel performance as it happens

Analytics & Insights

Get detailed insights into funnel performance:

Step-by-step breakdown: See completion rates for each step
Daily performance: Track conversion trends over time
Dropoff analysis: Identify where users are getting stuck
Conversion optimization: Use data to improve your funnels

API & Customization

Identifying Users

Associate visitor data with known users for personalized experiences:

window.seentics.identify('user_123', {email: 'user@example.com', name: 'John Doe', plan: 'premium'});

This data is used in workflows and webhook payloads for personalization.

Tracking Events

Send custom events with additional data:

window.seentics.track('purchase', {value: 99.99, currency: 'USD', product_id: 'prod_123'});

Custom UI (Modals & Banners)

For fully custom experiences, use the "Show Modal" or "Show Banner" actions with Display Mode = Custom. We render your HTML/CSS/JS inside an isolated iframe so your animations and scripts work reliably without affecting the host page.

What you can provide

Custom HTML: Provide a complete snippet or a full HTML. We automatically extract the body.
Custom CSS: Paste styles, including keyframes and media queries.
Custom JS: Vanilla JS; runs when the iframe loads.

Notes

Iframe sandbox allows scripts and same-origin for functionality while isolating styles from the host.
We auto-resize the iframe to match content height for banners.
Close button is overlayed outside the iframe for consistent UX.

Example: Custom Banner

Custom HTML

<div class="banner">
  <div class="banner-content">
    <h1>Create Something <span class="highlight">Amazing</span></h1>
    <p class="subtitle">Transform your ideas into reality</p>
    <button id="primaryBtn">Get Started</button>
  </div>
</div>

Custom CSS

html, body { margin: 0; padding: 0; }
.banner {
  background: linear-gradient(135deg, #667eea 0%, #764ba2 100%);
  color: white;
  padding: 40px 20px;
  text-align: center;
  font-family: 'Arial', sans-serif;
}
.banner-content h1 {
  font-size: 2.5rem;
  margin: 0 0 10px 0;
  font-weight: bold;
}
.highlight {
  color: #ffd700;
}
.subtitle {
  font-size: 1.2rem;
  margin: 0 0 30px 0;
  opacity: 0.9;
}
#primaryBtn {
  background: #ffd700;
  color: #333;
  border: none;
  padding: 15px 30px;
  font-size: 1.1rem;
  border-radius: 25px;
  cursor: pointer;
  font-weight: bold;
  transition: all 0.3s ease;
}
#primaryBtn:hover {
  transform: translateY(-2px);
  box-shadow: 0 5px 15px rgba(255, 215, 0, 0.4);
}

Custom JS

document.getElementById('primaryBtn')?.addEventListener('click', () => {
  window.parent?.postMessage({ type: 'banner_cta_click' }, '*');
});

Tip: Track CTA clicks by listening for the posted message in the host page or trigger a workflow Custom Event from your own code.

Using localStorage in Actions

Actions such as Send Email, Webhook, Show Modal/Banner (custom), and Insert Section can read values from your site's localStorage and inject them into action fields via placeholders.

In the action settings, add localStorage keys (e.g., cartId, userPlan).
Use placeholders like {{cartId}} or {{userPlan}} in Subject, Body, or Webhook JSON.

Save values in your app

localStorage.setItem('cartId', 'CART_12345');
localStorage.setItem('userPlan', 'pro');

Reference in Actions

Subject:  "Order {{cartId}} is pending"
Webhook JSON: { "plan": "{{userPlan}}" }

You can also use identified user fields: {{identifiedUser.id}}, {{identifiedUser.attributes.email}} when calling seentics.identify().

Implementation verified: client collects keys in workflow-tracker.js, server receives them in the execution payload, and actions resolve placeholders using localStorageData and identifiedUser.

Webhooks

Send workflow data to external services using webhook actions:

{
  "event": "webhook_triggered",
  "workflow_id": "workflow_123",
  "trigger_type": "funnel",
  "visitor": {
    "id": "visitor_456",
    "session_id": "session_789",
    "user_agent": "Mozilla/5.0...",
    "ip_address": "192.168.1.1",
    "referrer": "https://google.com",
    "identified_user": {
      "id": "user_123",
      "email": "user@example.com",
      "plan": "premium"
    }
  },
  "trigger_data": {
    "funnel_id": "funnel_abc",
    "event_type": "conversion",
    "step_name": "Purchase Complete"
  },
  "timestamp": "2024-01-15T10:30:00Z"
}

API Reference

Available JavaScript methods on your website:

window.seentics.track(eventName, data) - Track custom events
window.seentics.identify(userId, attributes) - Identify users
window.seentics.funnelTracker.trackFunnelStep(funnelId, stepNumber) - Manual funnel tracking
window.seentics.funnelTracker.trackFunnelConversion(funnelId, value) - Track conversions

Privacy & Compliance

Data Retention

Configure how long visitor data is stored:

Default retention: 2 years for analytics data
Custom retention periods available
Automatic data cleanup and archiving
Export before deletion options

Seentics Documentation

Analytics

Funnels

Workflows

Installation

Analytics

Visitor Tracking

Custom Events

Real-time Data

Workflows

Triggers: The "When"

Conditions: The "If"

Actions: The "What"

Funnel Triggers

Funnels

Creating Funnels

Funnel Tracking

Analytics & Insights

API & Customization

Identifying Users

Tracking Events

Custom UI (Modals & Banners)

What you can provide

Notes

Example: Custom Banner

Using localStorage in Actions

Webhooks

API Reference

Privacy & Compliance

GDPR Compliance

Data Retention

Cookie Consent