Event Caps - FAQ

Follow
Avatar
Product Team
Updated
How do I know what my event cap is?
  • The yearly event caps are reflected in the Account page.
  • The event cap applies to the whole account, not to each individual app.
Which events are included in the events cap?

All events sent to Singular via the SDK or S2S are counted toward the cap. These include:

  • Sessions
  • Revenue events
  • Ad monetization (admon) revenue events
  • Custom events
What happens if I go over the cap?

If you go significantly over the cap and don't mitigate the issue, you will be blocked from the Singular UI.

Note: Attribution, postbacks, and ETLs will continue to operate normally, so going over the cap will not impact your marketing efforts.

How do I mitigate the issue?

You need to do one of the following:

  1. Reduce the number of events you are sending to below the run rate.
  2. Purchase additional events. You can reach out to your CSM to inquire about purchasing additional events.

Tip: If you are sending admon events, you can reduce your event volume by enabling the admon batching feature. This SDK feature aggregates several admon events and sends them as one, reducing the total number of events Singular receives. Reach out to support to enable this functionality.

What is the run rate?

The run rate is the average number of events per day calculated based on the last 2 weeks of data.

What is my target run rate?

You can see the target run rate in the Account page. The target run rate is only shown if action is required on your part.

If I want to reduce my event volume, how do I know which events to reduce?

The choice is yours, but it is recommended to stop sending events that are not impacting your marketing activity — meaning events that are not used in postbacks.

To identify high-traffic events:

  1. Go to the Export Logs page and download a report of all your events. This report will show you which events have the most traffic.
  2. Run a separate report for each app.
  3. Make sure you select Type = Events.
  4. Usually, one day of data is enough to determine which events are the most problematic.
After reducing the number of events, how do I check if my efforts are sufficient?

Singular evaluates the run rate based on the last 2 weeks of data. This means that a reduction in event volume will take up to 2 weeks to fully take effect.

You can check whether the reduction is sufficient by pulling a 1-day report in the Export Logs page and verifying that the daily event count is below the target run rate.