LogoLogo
API DocsChangelogPlaybooksLoginBook a Demo
  • Getting Started
    • Introduction to Reo.Dev
    • For Users
      • Step 1: Find active accounts to target
      • Step 2: Track developer activity on your target accounts
      • Step 3: Identify developers engaging with your product
      • Step 4: Build custom segments that are most likely to convert
      • Step 5: Use filters to spot high-intent leads
    • For Admins
      • Step 1: Identify active accounts to target
      • Step 2: Track developer activity on your target accounts
      • Step 3: Find developers engaging with your product
      • Step 4: Create custom segments that are most likely to convert
      • Step 5: Integrating data sources with Reo.Dev
      • Step 6: Integrate Slack and set up notifications
      • Step 7: Add Customer Fit Criteria
  • Accounts
    • Account Lifecycle Stage
    • Custom CRM Stages
    • Developer Funnel Stages
    • Account Activity Score
    • Tags
    • Customizing Tags
    • Custom Lists
    • Using the Lists API in Reo.Dev
    • Managing CRM Owners in Reo.Dev
    • Follow an Account
    • How to Set Up Notification Alerts for Accounts, Developers & Segments in Reo.Dev
    • Flag incorrect data
  • Developers
    • Interpreting Intel on the Developer view page
    • Developer Activity Score
    • How to Find Inbound Developers in Reo.Dev
  • Segments
    • Creating Segments
    • Basic & Advance Segments
    • Filters 101
    • Segment Actions
    • My Segments
    • Shared Segments
    • Magic Segments
    • Favourite Segment
    • Add notes for better collaboration and context
    • CSV Exports for Segments
    • 10 Advanced Segments to create to spot high-intent opportunities
  • Buyers
    • Find Buyer Contact
    • How to Find, Segment & Engage Decision-Makers in Reo.Dev’s Buyer Section
    • Buyer Persona Configuration in Reo.Dev
  • Enrichment
    • Enrichment
  • Audiences
    • Buyer Audience
  • Integrations
    • Connect GitHub repositories
    • Reo.Dev Zapier Integration Guide
    • Webhooks
    • Developer Docs
      • Docusaurus
      • GitBook
    • CRM
      • HubSpot
      • Salesforce
      • Pipedrive
      • Zoho
      • Freshworks
      • Leadsquared
    • Tracking Beacon
      • Install JavaScript for Documentation
      • Install JavaScript for Product
      • Install JavaScript in Website
      • Install JavaScript in Local Product
      • Track Code Interactions
      • Install JavaScript for Documentation through Google Tag Manager
      • Reo.Dev JavaScript Cookies and Consent Guide
    • Product Usage API
      • Overview
      • How to Configure Product Usage Metrics in Settings
      • Telemetry Data
      • Product API
      • Examples of Product Usage Metrics
      • Data Collected for Product Usage
    • Communities
      • Open Communities
      • Owned Communities
        • Slack
        • LinkedIn Company Page
    • Email
      • Apollo.io
      • How to Integrate and Use Outreach.io with Reo.Dev
      • How to Integrate and Use Salesloft with Reo.Dev
    • Website Tracking
      • RB2B
  • Analytics
    • Impact Dashboard
  • Campaigns
    • Run bulk email campaigns
    • Testing Your Email Integration with Reo.Dev
  • Settings
    • Add Customer Fit Score Criteria
    • Add Firmographic and Technographic Filters
    • Configure Slack & Email Notifications
  • Account and Contact Usage Limit
    • Manage Account and Contact Limit Usage
  • User Management
    • Invite a teammate to Reo.Dev
    • Manage CRM Permissions
    • Roles and Permissions: Admin vs User
    • What Happens to Data When a User Is Deleted in Reo.Dev?
  • FAQs/Troubleshooting
    • How to Exclude Competitors from My Segments in Reo.Dev?
    • How to Sync a Segment to Salesforce/HubSpot?
    • Why Is the 'Sync to CRM' Button Greyed Out?
    • I Synced My Accounts, But They Are Not Showing in My CRM – What to Do?
    • Why Am I Seeing More Accounts in CRM Than I Synced?
    • Why Can't I Find My Account in the Dashboard Search Bar?
    • Resolving Caching Issues in Reo.Dev
    • Understanding Score Discrepancies Between Account and Developer Activity Score
    • Reo.Dev Credit-Based Pricing: FAQs
Powered by GitBook
LogoLogo

Resources

  • Changelog
  • Playbooks
  • DevGTM Conversations
  • Support
  • API Docs

Company

  • Blog
  • Contact Us
  • Book a Demo

Policies

  • Privacy Policy
  • Terms of Service

© 2025 All rights reserved Reo.Dev

On this page
  • API Structure
  • Tenant API Key
  • Sample JSON Request
  • Sample JSON Response [Success]
  • Sample JSON Response [Wrong API Key]

Was this helpful?

  1. Integrations
  2. Product Usage API

Telemetry Data

PreviousHow to Configure Product Usage Metrics in SettingsNextProduct API

Last updated 12 days ago

Was this helpful?

If you have an open source offering with call home/telemetry functionality to collect anonymous usage or event data, you can use the Product Usage API to share the data with Reo.Dev

From the telemetry data, we should be able to get

  • IP address of the system

  • Unique user ID

  • Activity Details

From the telemetry data, we will be able to enrich the

  • IP address and find out the company to which the user belongs

  • With the unique user ID, we will aggregate the product usage at a developer level and ultimately map it to the company to which the user(s) are associated

Important Note: Telemetry Data functionality requires the configuration of relevant metrics in the Product Usage Settings. Without this setup, the data cannot be transmitted or processed in the Reo.Dev platform.

To ensure proper integration, follow the steps in before proceeding with telemetry data workflows.

API Structure

Header

Description

Data type

X-API-KEY

Generated Reo.Dev <API_KEY> for authorization.

string

Content-Type

Request content-type is always set to application/json.

string


curl --location 'https://ingest.reo.dev/api/product/usage' \
--header 'X-API-KEY: <API_KEY>' \
--header 'Content-Type: application/json' \
--data '{
    "payload": {
				"activity_type" : "LOGIN_ACTIVITY",
				"source": "TELEMETRY",        
				"environment":"PRODUCTION",
        "user_id": "https://www.linkedin.com/in/userid",
        "user_id_type":"LINKEDIN",
        "ip_addr": "156.59.87.83",
        "event_id": 1231231232,  
        "event_at": 639303296,  
        "product_id": "reoWebApp",
        "user_agent": "Mozilla/5.0 (Macintosh, Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36",
        "meta": {"property1":"value1","property2":"value2"}
    }
}'

Tenant API Key

To access your API key, navigate to:

Settings → Integrations → API Keys → Product Usage API

  • Admins can generate and copy the key

  • Non-admin users can only view and copy the existing key


Parameter
Description
Datatype
Allowed Values
Example

source (Required)

Source of the activity.

enum

TELEMETRY, SAAS_PRODUCT

"TELEMETRY"

activity_type (Required)

Usage Metrics of the product. The definition of primary, secondary1 and secondary2 should match with metrics defined in the Reo.Dev settings. Where Source is Telemetry and you do not get any product usage data, activity type can be "CALL HOME"

string

Keys defined in metrics section in Reo.dev UI

"CALL HOME"

environment (optional)

Environment where product has been deployed.

string

"PRODUCTION"

user_id_type (optional)

Type of user ID such as email, Social, LinkedIn, GitHub, Username.

enum

EMAIL, SOCIAL, LINKEDIN, GITHUB, USERNAME

"EMAIL"

user_id (optional)

Unique user ID captured for a customer.

string

"https://github.com/michaelbevan"

ip_addr (mandatory)

IP address of the system from where the user has logged in.

string

"192.127.0.0"

event_id (mandatory)

A unique identifier for the event for Tenant for filter.

string

193ef456430

event_at (mandatory)

The time at which the event occurred (Formatted as a UNIX epoch in seconds).

integer

639303296

product_id (Required)

Unique identifier of your product.

string

"reoWebApp"

user_agent (optional)

Additional browser properties. This is optional if user_id is sent. In case user_id is not sent, user_agent becomes mandatory.

string

"Mozilla/5.0 (Macintosh, Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36"

meta (optional)

Any other parameter that needs to be sent.

object

Sample JSON Request

"payload": {
	"activity_type": "CALL_HOME",
	"source": "TELEMETRY",        
	"environment": "PRODUCTION",
        "user_id": "",
        "user_id_type":"",
        "ip_addr": "156.59.87.83",
        "event_id": "193ef456430",  
        "event_at": "639303296",  
        "product_id": "V1.2",
        "user_agent": "Mozilla/5.0 (Macintosh, Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36",
        "meta": {}
    }

Sample JSON Response [Success]

{
    "response_code": "200",
    "response": "Data Uploaded",
    "status": "success"
}

Sample JSON Response [Wrong API Key]

{
    "response_code": 400,
    "response": "Authentication Failure",
    "status": "failure"
}
How to Configure Product Usage Metrics in Settings