Download websites that use AddEvent

Small components are often easier to read than large ones. AddEvent does one job, adding an event to a visitor's calendar in a single click across Google, Apple, Outlook and the rest, and a site only installs it when there is something dated to add.

The narrowness is what makes it useful. Detecting a framework tells you how a site was built. Detecting a calendar button tells you what the site is trying to get somebody to do, which is commit to a time. Webinars, course intakes, product launches, ticketed events, appointment confirmations and booking flows are the contexts that put it on a page, so the population leans towards organisations running scheduled programmes rather than static catalogues.

As of October 2026 we detect AddEvent on 1,246 sites. Since 2011 AddEvent has sold the product on a Freemium basis, which matters for interpretation, because a free tier lowers the bar to installation and means a detection proves deployment rather than spend. The JavaScript snippet loads from the vendor's own hosts, which makes it comparatively reliable to spot, although buttons injected by a tag manager after a delay, or used inside email campaigns and confirmation pages no crawler will reach, stay outside the count.

Marketing technology vendors read the resulting list as an intent signal. Event platforms, webinar and scheduling tools, registration and ticketing products, and customer relationship vendors with campaign features are all looking for organisations that already run dated programmes and have already accepted third party widgets in their pages, which clears two objections before a conversation starts. Agencies use the same file to size a category or to see what a client's competitors put on their registration pages.

Checking one domain is a curiosity. Holding every domain that installed a calendar button, in one export with a date attached, turns a minor widget into a practical way of finding businesses whose revenue runs on a calendar.