Overview, unique count and bots

[engram-design]

• The ability to isolate data by date (overview screen)
• The ability to capture unique count (number of users that have viewed or downloaded the asset)
• The ability to exclude Bots and Spiders hit (Our websites get tons of hits from search engine spiders and bots which would increase the number of hits significantly)

[engram-design]

I’ve added support for excluding bots, crawlers and spiders from asset counts. This is available as a new “Ignore bots” setting, and when enabled Asset Count will skip incrementing counts for requests that look like they’re from automated crawlers.

The other two suggestions are a bit more involved with how Asset Count currently stores data. At the moment, the plugin stores a single aggregate count per asset, rather than individual hits or daily records.

Date filtering/overview reporting would require storing count history, either as per-day aggregates or individual hit records. Existing historical totals couldn’t be accurately split back into dates.

Unique counts would require defining and storing a visitor identity. That’s straightforward for logged-in users, but anonymous users would need something like a cookie, hashed IP/user-agent, or another privacy-conscious identifier, along with a decision about how long “unique” should last.

So bot filtering is a good fit for the current architecture and has been added, while date-based reporting and unique counts would need a larger tracking/schema change.

To get this early, run composer require verbb/asset-count:"dev-craft-5 as 3.0.1".