Skip to content

Capture SDK analytics #6256

Description

@lobsterkatie

Problem Statement

It's helpful to know how people are using our SDK. For example, in the past we've wondered things like:

  • How many nextjs SDK users are deployed to Vercel?
  • Do most people use us via npm or CDN? Of the ones who use us via CDN, how many use the tunneling option?
  • How widely-used is ? How many of those people are actually using the current version of the SDK?

and so on and so forth.

In order for this to be useful, however, we also need a) for relay to not drop the data as something it doesn't recognize, and b) for it to be queryable somewhere. This issue is meant to track both that larger meta project and specific instances where we implement various analytics.

Solution Brainstorm

Prerequisite non-SDK work

  1. Work with the ingest and data teams to figure out
  • Where in the event to store the data
  • What changes are necessary in relay
  • How the data will be accessed
  1. Make necessary non-SDK changes
  • relay
  • ??? (wherever querying will happen, if changes are necessary there)

Work to add specific metrics to the SDK

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions