View IPFS Analytics

Display analytics for IPFS content

Overview

Help members of your community access analytics for their IPFS content. The Leto Analytics API will return a view count for each piece of content.

If your platform, website, or app uses Leto Analytics, your community can lookup analytics for IPFS content in your system.

We hosted a version of this app here (hosted on IPFS using Spheron)! Monitor engagement and potential system abuse on webpages, NFTs, blogs, and more. No login required!

To host this web-app for your community, use the instructions below and this Github repo to get started.

UI for View IPFS Analytics

Getting Started

Follow the steps below to set up and run the React App in a local development environment.

1. Clone the Repository:

   git clone [https://github.com/galaxyxtwo/viewIpfsAnalytics]
   cd [viewIpfsAnalytics]

2. Run the Development Server:

   npm install
   npm start

3. Add your IPFS CIDs: Copy and paste your CIDs into the box to create a list! When running viewIpfsAnalytics, the inputs (cids) and associated analytics data are saved in local storage.

Keep in mind: Only IPFS CIDs that have been served through the Leto IPFS Gateway will return analytics data.

This project was bootstrapped with Create React App.

Note

/worker is Javascript code meant for a Cloudflare worker that processes api requests. /src is the front-end built with React. Use this repo to get started hosting your own app in the cloud!

Leto Background

When a developer serves IPFS content (webpage, blog, NFT) with the Leto IPFS gateway, the analytics collected is publicly available via the Leto Analytics api.

The View IPFS Analytics tool uses the Leto Analytics api to retrieve and display anonymous, aggregate analytics for a given IPFS CID. End-users love having access to the data for business and fun!

We hope you find this useful! If your business needs more functionality, login to the Leto dashboard for free and upgrade your service to a pro plan when needed.

Learn more by visiting the Leto docs or Blog.

Note: In the future Leto will give developers a choice to opt in or out of this public dataset for privacy reasons. It will be up to each dev to commuinicate this with end users.