We already use algolia to track search terms in documentation to see what users are searching for. We have been considering doing the same thing in the explore site for the same reason - tracking downloads!
The overture maps org already has an algolia account, so we'd need to figure out how to get a JS app to send analytics data regarding the download button.
[x] Set up new algolia 'app' instance'
[x] integrate with the io-site code
[x] open a PR that sends bbox data back to the algolia app
[x] revoke existing app keys now that poc works
[x] generate new keys
[ ] Figure out how to properly lock down credentials
We already use algolia to track search terms in documentation to see what users are searching for. We have been considering doing the same thing in the explore site for the same reason - tracking downloads!
The overture maps org already has an algolia account, so we'd need to figure out how to get a JS app to send analytics data regarding the download button.