Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.datalyr.com/llms.txt

Use this file to discover all available pages before exploring further.

Usage Tracking shows your current usage for events and conversions, helping you stay within plan limits and avoid unexpected overage charges.

What It Does

Track Usage:
  • Events used this billing period
  • Conversions sent to ad platforms
  • Usage by workspace
  • Overage status
  • Days until reset
Shows:
  • Current usage vs plan limits
  • Usage percentage
  • Projected overages
  • Per-workspace breakdown

Accessing Usage Tracking

Go to: Settings β†’ Billing β†’ Usage section View real-time usage for current billing period.

Event Usage

Events Include:
  • Pageviews
  • Custom events you track
  • Shopify orders
  • Stripe payments
  • Any event sent to DATALYR
Not Counted:
  • System events (session_start, session_end)
  • Duplicate events (deduplicated automatically)
  • Failed/rejected events
Usage Display:
Events: 32,450 / 50,000 (65%)
Status: βœ“ Within limit
Remaining: 17,550 events
Resets: January 15, 2025

Conversion Usage

Conversions Include:
  • Events sent to Meta Ads
  • Events sent to Google Ads
  • Events sent to TikTok Ads
  • Based on Conversion Rules
Not Counted:
  • Events tracked in DATALYR only
  • Events not matched to Conversion Rules
  • Failed postbacks (retries don’t count)
Usage Display:
Conversions: 750 / 1,000 (75%)
Status: ⚠ Nearing limit
Remaining: 250 conversions
Resets: January 15, 2025

Per-Workspace Usage

Breakdown Shows:
  • Each workspace separately
  • Events per workspace
  • Conversions per workspace
  • Total across all workspaces
Example:
Workspace: Production Site
Events: 28,000
Conversions: 600

Workspace: Staging Site
Events: 4,450
Conversions: 150

Total: 32,450 events, 750 conversions
Useful for agencies managing multiple clients or brands with multiple sites.

Usage Alerts

Automatic Notifications:
  • 75%: Warning - approaching limit
  • 90%: Urgent - nearing limit
  • 100%: Overage - limit exceeded
Alert Email Includes:
  • Current usage
  • Limit exceeded
  • Projected overage cost
  • Recommendation to upgrade
Sent to account owner only.

Overage Tracking

Real-Time Overage Display:
Events: 55,000 / 50,000 (110%)
Overage: 5,000 events
Overage charge: $2 ($2 per 50k)
Status: πŸ”΄ Over limit
Projected Overage:
Current: 32,450 / 50,000 (Day 10 of 30)
Projected: ~97,350 at month end
Projected overage: 47,350 events
Estimated charge: $95
Recommendation: Upgrade to Growth plan
Helps you decide whether to upgrade or accept overage charges. Historical View:
  • Last 3 months usage
  • Average monthly usage
  • Peak usage days
  • Growth trend
Use Cases:
  • Plan capacity planning
  • Identify traffic spikes
  • Optimize plan selection
  • Budget forecasting

Understanding Usage Spikes

Common Causes:
  • Marketing campaign launches
  • Viral content or press
  • Holiday shopping seasons
  • Product launches
  • Traffic bot attacks
Temporary Spikes:
  • Accept overage charges for one-time events
  • Cheaper than upgrading annually
Sustained Growth:
  • Upgrade plan for consistent high usage
  • More cost-effective long-term

Managing Usage

Reduce Event Usage:
  • Filter out bot traffic
  • Remove unnecessary custom events
  • Reduce pageview tracking on admin pages
  • Consolidate duplicate events
Reduce Conversion Usage:
  • Limit Conversion Rules to essential events
  • Don’t send every event to every platform
  • Remove test conversion rules
Example Optimization:
Before:
- Send all events to all platforms
- 3 platforms Γ— 10,000 events = 30,000 conversions

After:
- Send only purchase events to all platforms
- 3 platforms Γ— 2,000 purchases = 6,000 conversions
Savings: 24,000 conversions (80% reduction)

Billing Period

Usage Resets:
  • Resets on billing anniversary each month
  • Counter goes back to 0
  • Fresh limits for new period
Example:
Billing date: 15th of each month
January 15: Reset to 0 events
February 15: Reset to 0 events
March 15: Reset to 0 events
Days until reset shown in usage display.

Multiple Workspaces

Usage Aggregated:
  • All workspaces count toward total
  • Plan limits apply account-wide
  • Cannot allocate limits per workspace
Best Practice:
  • Monitor highest-usage workspaces
  • Consider separate accounts for large clients (agencies)
  • Use workspace breakdown to identify heavy users

Workspace-Level Monitoring

Per Workspace:
Settings β†’ [Select Workspace] β†’ Settings β†’ Usage
Shows usage for that specific workspace only. Useful For:
  • Agency reporting to clients
  • Multi-brand usage tracking
  • Identifying problem workspaces

API Usage Limits

Separate from Event Limits:
  • API requests for data retrieval
  • 10,000 requests/day (all plans)
  • Resets daily at midnight UTC
API Usage Display:
API Requests: 2,450 / 10,000 (25%)
Resets: Today at midnight UTC
Shown in Usage Tracking section.

Best Practices

Monitor Regularly:
  • Check usage weekly
  • Set calendar reminder for billing date
  • Review overage projections mid-cycle
Plan Ahead:
  • Upgrade before hitting limits
  • Budget for seasonal spikes
  • Review usage trends quarterly
Optimize Tracking:
  • Only track events you need
  • Use Conversion Rules strategically
  • Filter internal/test traffic
Set Budget Alerts:
  • Enable usage notifications
  • Set custom thresholds (e.g., 50%)
  • Add finance team to alert emails

Next Steps

Subscription Management

Upgrade or modify plan

Pricing

Compare plans

Dashboard

View event metrics

Conversion Rules

Manage conversion rules