Browsee
  • Getting Started
    • How to use Browsee on Shopify Store?
    • Shopify Stores
  • Integration
    • Snippet Integration
      • Direct JS Integration
      • GTM Integration
      • SDK Integration
      • Wordpress Integration
      • Shopify Integration
      • Troubleshooting Integration
    • Managing Recordings
    • API Calls
      • Log Event Call
      • Identify Call
      • Session Url
      • Generate Secret Key
      • Data Export API
      • Track HTTP API
      • Identify HTTP API
  • Understand Your Users
    • Session Search
      • Date Range
      • User Actions
      • User Attributes
      • Session Tags
        • Network Errors and Slowness
        • Javascript (JS) Errors
        • Frustration Clicks or Rage Clicks
        • Broken Links
        • U Turn
        • Searching For Something
        • Going in Circles
        • High Engagement
        • High Input Time
        • Repeat Pages
        • Repeat Events
      • Regular Expression Search
    • Segments
    • Segment Analytics and Alerts
    • Subscribe to a Segment
    • Configure Dashboard
    • Session Replays - Save, Share, and Delete
    • User Experience Issues
  • Heatmaps
    • Heatmaps
    • Create Heatmaps
    • Compare Heatmaps Across Date Ranges
    • Segmentation in Heatmaps
    • Heatmap Sessions
    • Dynamic Heatmaps
  • Funnels
    • Creating Funnels
    • Funnel Analytics and Alerts
  • FAQ
    • Frequently Asked Questions
    • FAQ - Browsee Installation
    • FAQ - Account and Project
    • FAQ - Session Recordings
    • FAQ - Heatmaps
    • FAQ - Payment & Plans
  • Project
    • Add User
    • Add Project
    • Setting Up SSO Login
    • Third Party Integrations
    • Content Security Policies
  • Plans and Billing
    • Recording and Sampling
  • Data Privacy
    • Privacy
    • Do Not Track Settings
    • Link Browsee with your Privacy Policy
    • GDPR Compliance
  • Feedback & Popups
    • Creating Notifications
    • When to Show
    • Where to Show
    • Advanced Targeting
    • Feedback Widget
    • Integrations
  • Request A Feature
    • Request a New Feature
Powered by GitBook
On this page
  • API Key
  • Track API
  • track
  • Using the track event API

Was this helpful?

  1. Integration
  2. API Calls

Track HTTP API

You can use Browsee's HTTP Track API to send custom events from other platforms like your mobile app or application server.

PreviousData Export APINextIdentify HTTP API

Last updated 4 years ago

Was this helpful?

While Browsee's web SDK automatically most events like page views, clicks users can use Browsee's call to send custom events. In addition, you may want to send custom User Data from your non-web applications like a mobile app, servers, etc. so you can unify a complete picture of a user across all platforms. Sending such data

  • Allows you to create segments on these custom events

  • Creating or generating reports for non-web users.

API Key

To use the below API you will need your project API key. This key is available on your Project's .

Track API

track

POST https://api.browsee.io/api/v1/track

An API to send custom events for some users

Request Body

Name
Type
Description

apiKey

string

Your Project's API Key

event

string

Name of the action that the user has performed like "CLICKED_CHECKOUT"

properties

object

A JSON dictionary of the properties of the event like: { "price": 100, "category": "Apparel" }

userId

string

A unique identifier of the user in your database. At least one of userId or anonymousId is required.

anonymousId

string

This is an identifier that can be sent to tie a series of events to a certain user and a session. In case you are using userId, we will use that, otherwise, this is needed

timestamp

string

Timestamp of the event in ISO-8601 format date string. If not provided we assume the time of receipt like "2021-12-02T00:30:08.276Z".

{
    "status": "success"
}
{
    "status": "failure",
    "message": <Problem in request parameters>
}

Using the track event API

  • This api is rate limited and should not be used to dump historical data.

  • When a user is anonymous, you can send any token as anonymousId. This anonymousId helps us tie a series of events into a session. If you are using other tracking tools, you can also get their unique identifier and send that as a unique identifier as theanonymousId.

userId should be the same as you provide via Identify call, whether used via or .

timestamp is a standard time formatted string.

Identify Call
Identify HTTP API
ISO-8601
logEvent
settings page
Copy your API Key from Settings > Install > I use Google Tag Manager