Runway Documentation
  • About Runway
  • 🚀Getting started
    • Adding apps
    • Setting up your integrations
      • Branching strategies
      • Builds and branches
      • Pattern strings / tokens
    • Preparing your first release
    • Setting up your team
  • 🎛️Using Runway
    • Navigating Runway
    • Build Distro
      • Quickstart
      • Uploading builds for distribution
      • Build Distro buckets
      • Sharing builds
      • Installing builds
      • Signing and provisioning cheat sheet
    • App overview
    • Releases
      • Release overview
      • Feature flags
      • Kickoff
      • Feature readiness
      • Translations
      • Release candidate
      • Regression testing
      • Beta testing
      • Screenshots
      • Metadata
      • Approvals
      • App submission
      • App store review
      • Release
    • Workflows
    • Release schedule
    • Rollout
    • Hotfixes
    • Rollbacks
      • Creating rollbacks
    • Checklists
    • Build matching
    • App settings
      • General settings
      • Team settings
      • Release pilot rotation
      • Integrations settings
      • Profiles and devices
      • Signing keys
      • Health metrics settings
      • Automations settings
      • Notifications settings
      • Schedule settings
      • Beta testing settings
      • Metadata settings
      • Release defaults
      • Checklists settings
      • Custom strings settings
    • Organization overview
    • Organization settings
      • Team
      • SSO/SAML
    • User settings
    • Over-the-air (OTA) releases
  • ⚙️Integrations
    • Integrations overview
    • Version control
      • Azure Repos
      • Bitbucket
      • GitHub
      • GitLab
    • Project management
      • Asana
      • Azure Boards
      • GitHub Issues
      • Jira
      • Linear
      • Pivotal Tracker
      • Monday.com
      • Shortcut
    • CI/CD
      • App Center Build
      • Azure Pipelines
      • Bitbucket Pipelines
      • Bitrise
      • Buildkite
      • CircleCI
      • Codemagic
      • GitHub Actions
      • GitLab CI
      • Jenkins
      • TravisCI
      • Xcode Cloud
    • Regression testing
      • TestRail
      • Xray
    • Beta testing
      • Google Play testing tracks
      • TestFlight
      • App Center
      • Firebase App Distribution
    • App stores
      • App Store Connect
      • Google Play Console
      • Amazon Appstore
      • Huawei AppGallery
      • Samsung Galaxy Store
    • Notifications
      • Microsoft Teams
      • Slack
    • Stability monitoring
      • BugSnag
      • Datadog
      • Embrace
      • Firebase
      • New Relic
      • Sentry
      • Dynatrace
    • Observability & analytics
      • Amplitude
      • Datadog
      • Google Analytics
      • Mixpanel
      • New Relic
      • Android Vitals
      • Custom observability & analytics
    • Feature flagging
      • Optimizely
      • LaunchDarkly
    • Scheduling
      • Opsgenie
      • PagerDuty
    • Translations
      • Crowdin
      • Lokalise
    • Calendar
      • Google Calendar
      • Google Calendar (OAuth)
  • ⚡Automations
    • Automations overview
    • Types of automations
  • 🔔Notifications
    • Notifications overview
    • Types of notifications
  • 🪝Webhooks
    • Outgoing webhooks
  • 📡REST API
    • Overview
    • Reference Docs
    • Markdown Badge API
    • App configuration files
  • 🛠️Quickstart CI/CD
    • Quickstart CI/CD overview
    • Getting started
  • Support
    • Contact us
Powered by GitBook
On this page
  • Set up
  • Navigate to the Integration settings view
  • Connect a new integration
  • Sending data to the custom integration

Was this helpful?

  1. Integrations
  2. Observability & analytics

Custom observability & analytics

PreviousAndroid VitalsNextFeature flagging

Last updated 5 months ago

Was this helpful?

If your team has an in-house analytics framework, or would otherwise like to compute metrics on your own servers and push them as needed to Runway, you can connect a custom Observability & analytics integration to accomplish this. Once connected, a unique integration identifier will be generated that you can use to construct an endpoint URL for Runway's public API that can be used to stream data points to your app's integration in Runway.

Set up

Navigate to the Integration settings view

  1. Select an app in the top left corner from the Switcher

  2. Navigate to App Settings by clicking the gear icon (⚙️) at the top of the Timeline sidebar

  3. Click on Integrations in the sidebar

Connect a new integration

  1. Find the Custom Analytics integration module under the Observability & analytics section.

  2. Click the Connect button.

  3. You'll be prompted to choose a Display Name for your custom integration. This can be helpful if you intend to connect multiple custom analytics integrations from different data sources.

  4. Click Submit.

A custom integration will be connected, and its unique integration identifier will be surfaced in the integration details table. You'll need this identifier to construct the public API endpoint that you'll use to send the integration data.

As events are sent to Runway and processed, they'll be shown in the "Events detected" list in the integration details table, along with the date and time of the last received event.

Health metrics must be set up in order for custom analytics event data to be visible on the Rollouts page for releases in Runway.

Sending data to the custom integration

Once the custom integration is set up and configured, data points can be sent to it using Runway's public API.

Once events are received and processed by Runway, they'll be visible in the and available for the configuration of Observability & Analytics health metrics for your app.

For more details on how to send data to your custom Observability & analytics integration, visit our .

⚙️
Health Metrics page
public API documentation