Why is my event exceeding the usage limits?
We occasionally receive reports that customers have more downloads for their event than seems possible or that an event has exceeded its usage limits when they haven't published it yet.
If you've experienced this, there are a number of possible reasons:
Link checkers
If you're using an add to calendar link in an email service like Mailchimp, HubSpot, etc., the service you've added the link to is using a "link checker." This is a tool that actively goes in and clicks the links in your email, thereby marking it as a click (event-add) in our service. This can happen even if you haven't yet sent out the email. Unfortunately, there isn't anything we can do about this, although we would love to. Currently, we are working to stop this by filtering out robots like search engines, but we're not able to filter out services like Mailchimp, HubSpot, etc., as they don't leave a trace/user agent.
The link checker issue should not affect you if you have a paid plan since the event-add limit on each plan is significant. If you have a Hobby plan and your usage limit has been exceeded, please consider upgrading your account to increase your plan usage limit and avoid this issue in the future. Otherwise, the count will automatically reset when a new calendar month begins.
Users adding an event multiple times
The second possible reason is that some of your users might be clicking your add to calendar button or link multiple times – people are curious and love to click on things if they have a nice effect (such as our beautiful button).
If you are on a paid plan and you are reaching/exceeding your usage limits, please consider that the usage might be a combination of the reasons explained above and you may need to consider being on a higher plan.
Apple calendar
When adding events to your calendar on an iPhone when using a browser other than Safari, we are forced to "subscribe" a user to the event becuase of limitations to iOS imposed by Apple (read more here: Add to Calendar on iPhone). While this solution is far from ideal, it's unfortunately our only option for this scenario and our best effort to "make it work" - if we didn't subscribe the user to the event, it would result in an error for the user.
There is a tradeoff here however: becuase the user is "subscribed" to the event, it will periodically try to hit our services to refresh. This will result in an additional event-add being recorded for that event when that happens. Please note that these event-adds will only be recorded until the event has passed.
Updated 2 days ago