Understanding Event Capacity & Usage Guidelines

Overview

This article explains how event capacity is designed and how to build an efficient event strategy for marketing attribution.

Event tracking should enable marketing measurement and optimization — not replicate product analytics. A focused event setup leads to clearer insights, better performance, and long-term scalability.

Event Slots in the Events Page

Each app is provisioned with a predefined number of event mapping slots for custom events.

These slots are designed to capture high-impact marketing actions, such as:

• Purchases and revenue signals

• Signups and onboarding milestones

• Subscription lifecycle events

• Campaign conversion actions

• By default, customers receive 12 event slots per app

• Unified plan customers can use up to 30 event slots per app

• Additional capacity may be reviewed upon request

For most customers, the default allocation is more than sufficient when events are aligned to marketing outcomes.

Additional event capacity may be reviewed for advanced use cases to ensure the event architecture remains efficient and scalable.

Best practices for event slots

- Track only events tied to marketing decisions
- Consolidate similar actions into a single event
- Avoid internal telemetry, QA, or debugging signals
- Review and remove unused events regularly
- Keep event naming simple and consistent

SDK / S2S Event Capacity

Apps are provisioned with scalable SDK and S2S event capacity to support attribution, optimization, and revenue measurement.

Event capacity is evaluated independently per:

• App

• Platform (iOS, Android, Web, etc.)

• App version

• By default, apps can send up to 150 unique SDK/S2S events

• Unified plan customers can scale up  the events when required

For the vast majority of integrations, this capacity comfortably supports marketing use cases when events are thoughtfully designed.

Expanded capacity is available for Unified plan customers when business needs justify additional coverage.

Important Guidance

Singular is a marketing attribution and measurement platform — not a full product analytics suite.

Sending excessive low-value or highly granular telemetry can:

• Create reporting noise

• Reduce signal clarity

• Increase processing overhead

• Introduce operational inefficiencies

Recommended Event Strategy

Use this simple rule when deciding whether to send an event:

Strong event candidates

- Purchases and revenue signals
- Subscription lifecycle milestones
- Onboarding completion
- Campaign conversions
- High-intent engagement actions

Events better suited for product analytics tools

- UI interaction tracking
- Debugging telemetry
- Granular session behavior
- Internal QA signals
- Engineering instrumentation

Using Analytics Tools Alongside Attribution

If you are using product analytics or CRM tools (for example, Firebase or Mixpanel), it is not recommended to replicate or forward the full set of analytics events to the MMP.

Attribution platforms require only events necessary for:

• Marketing attribution

• Campaign optimization

• Conversion funnels

• Revenue measurement

Sending large volumes of analytics events can reduce signal quality and increase operational overhead without improving marketing outcomes.

Best practice:
Use analytics tools for deep behavioral insights, and send only high-value marketing events to the MMP.

When to Contact Your Customer Success Manager

Reach out if:

• Marketing reporting needs expand

• New monetization flows are introduced

• Enterprise-level event coverage is required

• You are unsure whether an event belongs in attribution

• You want help optimizing your event architecture

Summary

A disciplined event strategy delivers:

• Clearer marketing insights

• Lower integration complexity

• Stable platform performance

• Scalable long-term growth