Best practices & responsible use

When implementing usage events with Mantle, thoughtful design of your event tracking strategy ensures optimal performance for everyone in our ecosystem. We're committed to maintaining our straightforward, revenue-based pricing without charging for usage events—and your responsible implementation helps us keep this promise.

Event granularity considerations

Right-sizing your usage events

Consider the appropriate level of detail needed to achieve your business goals:

Ask yourself: Does your use case require individual event tracking, or would aggregated data serve your needs?
Consider timeliness: Minute-by-minute reporting versus daily summaries - which truly meets your requirements?
Evaluate application needs: Are specific properties within each event critical, or are you primarily concerned with totals?

Recommendations for event volume

Mantle is built to handle high volumes of usage events at no additional cost to you. While efficient implementation benefits the entire community, we fully support streaming individual events when your use case requires it:

Stream when necessary: If timely, granular tracking is essential to your use case, we encourage you to use our events API as needed
Batch when possible: Where appropriate, consider aggregating similar events before sending to Mantle
Find the right balance: The ideal implementation matches your business requirements without unnecessary overhead

Implementation strategies

Efficient usage event patterns

Use case	Recommended approach
Usage-based billing	Track at whatever granularity your pricing model requires - from individual transactions to daily totals
Feature adoption	Use the level of detail that gives you actionable insights for your specific needs
Customer behavior	Track patterns at the level of detail that drives meaningful business decisions
Resource consumption	Use the measurement frequency that supports your monitoring requirements

Examples of implementation options

Streaming individual events (fully supported when your use case requires it):

// Sending an event for every page view when real-time tracking is needed
await mantleClient.sendUsageEvent({
  eventName: 'page_view',
  properties: { page: '/dashboard' }
});

Batching when appropriate (optional optimization):

// Batching page views into daily summaries when real-time tracking isn't required
await mantleClient.sendUsageEvent({
  eventName: 'page_views_summary',
  properties: { 
    total_views: 247,
    date: '2023-05-15',
    page_breakdown: { '/dashboard': 153, '/settings': 94 }
  }
});

Our commitment to you

Mantle doesn't charge for usage events and we're committed to maintaining this approach. Our pricing is and will remain based on tracked revenue, not event volume. We encourage you to implement the event tracking strategy that best serves your business needs without compromising your use case.

We believe in providing value without nickel-and-diming for features like usage events. By considering efficiency where possible while using the full capabilities of our platform when needed, you help us continue offering this inclusive approach to all our partners.

If you're unsure about your specific implementation, our team is always available to provide guidance on optimizing your usage event strategy.