Repository navigation
Send analytics to ingest.loopkit.org - #35
Merged
Merged
Conversation
Usage data now goes to the LoopKit ingest endpoint instead of Amplitude's default API host.
This was referenced Oct 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Points LoopKitAnalytics at
https://ingest.loopkit.org/v1/eventsinstead of Amplitude's default API host. The API key, tracking options and event payloads are unchanged.Tested with a device build: with Share Usage Data on, events and identifies uploaded to the new endpoint with HTTP 200.
next-dev builds pick this up once LoopWorkspace bumps the LoopSupport submodule.