Skip to main content

​
Overview

Trodo ingests behavioral data from the websites and web apps you register as sites. Each site has its own Site ID, domain allowlist, and settings.

​
Sites

Sites are the surfaces you want to track with Trodo—marketing sites, logged-in apps, agent dashboards, or embedded widgets, as long as they load the SDK with that Site ID.

​
Adding a Site

1

Go to Settings

Navigate to Settings → Sites
2

Add New Site

Click Add Site
3

Configure Site

  • Name: Human-readable name (e.g., “Production App”)
  • Domain: Your website domain (e.g., app.example.com)
4

Get Site ID

After creation, you’ll receive a Site ID to use in your tracking code

​
Site Configuration

Site: Production App
├── Site ID: prod-app-12345
├── Domain: app.example.com
├── Status: Active
├── Created: Jan 1, 2024
└── Last Event: 2 minutes ago

​
Multiple Sites

One team can have multiple sites: 
Team Sites:
├── Production (app.example.com)
│   └── Site ID: prod-app-12345
├── Staging (staging.example.com)
│   └── Site ID: staging-app-67890
└── Marketing (www.example.com)
    └── Site ID: marketing-site-abcde
Use cases for multiple sites:
  • Separate production and staging
  • Track multiple products or workspaces
  • Different domains for different regions

​
Domain Whitelist

For security, Trodo only accepts events from whitelisted domains: 
Allowed Domains for prod-app-12345:
├── app.example.com ✓
├── www.example.com ✓
└── *.example.com (wildcard) ✓
Add domains that should be allowed to send events with this Site ID.

​
Site Settings

SettingDescription
Auto-eventsDefault auto-event configuration
Allowed domainsDomains that can send events
Data retentionHow long to keep event data

​
Data Flow

​
Cross-Site Tracking

If the same user visits multiple sites that share your analytics setup (and identity strategy), you can compare journeys across properties using Site ID filters in the product. 
User: distinct_id abc
├── Site A: 15 events
└── Site B: 8 events

​
Managing Sites

​
Edit Configuration

  1. Go to Settings → Sites
  2. Click the site to edit
  3. Modify settings
  4. Save changes

​
Archive vs Delete

Archive: Stops tracking new data but preserves historical data
Delete: Removes configuration (historical data retained per retention policy)
Deleting a site removes the Site ID. Any tracking code using that ID will stop working.

​
Status Monitoring

Check health of your sites: 
Sites Status:
├── prod-app-12345: ✅ Active (1,234 events/hour)
├── staging-67890: ⚠️ Low activity (2 events/hour)
└── old-site-xyz: ❌ No events (30+ days)

​
Best Practices

✅ Recommended:
├── One site per environment (prod, staging, dev)
├── Separate sites for distinct products
├── Consistent naming convention

❌ Avoid:
├── One site for everything (hard to filter)
├── Duplicate sites for same domain
├── Cryptic Site IDs in production code

​
Security

  • Keep Site IDs confidential (treat like API keys)
  • Use domain whitelisting
  • Regularly audit active sites
  • Remove unused configurations

​
Troubleshooting

  1. Verify Site ID in tracking code
  2. Check domain is whitelisted
  3. Ensure SDK is loading correctly
  4. Check browser console for errors

​
Next Steps

Installation

Add the SDK to your app

Privacy & Compliance

Data handling and retention