Use Actions to build your use cases in minutes

Action is the basic unit of tracking with HyperTrack. Developers must create and complete actions in HyperTrack to track the movement of users and build their use cases with movement data. Today, we are excited to announce a simplified version of the HyperTrack Action API. Developers who tested the pre-release version were able to build their use cases within minutes.
Action types

Create and complete actions to track user movement

Thousands of developers have built their movement tracking use cases with HyperTrack across industries, regions and applications.

Mapping your use case with the actions use model is now minutes of work.

  • Actions may be created or completed from the app or back-end when the respective action happens in your system
  • Actions may be automatically created and completed using rules based on time and place
  • Actions may be organized in collections such as orders (with a pickup and delivery) or meetups (with multiple friends sharing) so they can be tracked live in one view and data can be queried easily in one API call
Tracking one action Tracking multiple actions

Track through the day

Most developers sign up and follow the quickstart to plug the SDK into their app and then track users through the day, using a rule that automatically creates an action for each user at midnight and completes it the following midnight. Developers tracking business users may modify the rule to create and complete actions in working hours—create at 9AM and complete at 5PM, say. Each active day of tracking for a user is one action in this case.

Track users through the day

Common use cases built with actions

After testing movement tracking for accuracy, real-timeness and battery efficiency, the popular next step is to create more granular actions depending on the primary use of your app.

  • Geofence visits: Sales and service executives visiting a list of expected places (customer addresses) in an ad-hoc sequence are geofenced in and out of the expected places visited. Actions are automatically created when they enter the geofence and completed when they exit the geofence.
  • Visits in a milk run: Professionals visiting customers through the day in an ad-hoc sequence mark their visits as done as they go. Actions are simultaneously created and completed when they are marked done in the app. If the sequence of visits is known ahead of time, actions are created with expected place at the start of day and marked done by users as they go.
  • Pickups and drops: Uber-for-X providers servicing orders are assigned orders on-demand with expected places for pickups and drops. Customers and ops teams track orders live with ETA and status when on the way. Pickup and drop actions are created when the order is assigned and completed as the pickup and drop are marked done respectively. Uber-for-X
  • Live location sharing: Consumers sharing live location with friends start sharing when on the way to meet up and automatically stop sharing when they arrive. Similarly when buyers and sellers in a marketplace are meeting up to consummate a transaction. Actions are created when sharing starts and automatically completed upon arrival.Live location sharing

What you get with actions

All the movement data for actions — activity, location and device health — is available through APIs, events and visuals with no limit on the number of location data points, API calls, events delivered, use cases, map views, team members or consumers viewing the data. All of that comes included with every action you track!

Once actions are created, you can track the live movement of the user with their current location, activity and device health. The Placeline of the action gives you the movement data for the action so far. This may be consumed as visuals, data or events. Additionally, if actions are created with an expected place, you can track live movement with ETA, expected route, remaining distance, arrival status and delay reasons.ETAs and expected route

Simple API calls are available for commonly queried data for a set of actions by the user—Placeline, mileage and events. Live movement tracking experiences may be built for web dashboards or in-app product experiences. Dashboard visuals may be embedded within your web dashboards for nearly all the views available in your Hypertrack dashboard.

Impact on existing customers

The new APIs have reduced the number of API calls by half. Which means you have that much lesser code to write and multiplicatively lesser states to manage. Furthermore, it implies that we can provide more reliable data with lesser dependence on user behavior. Read more on how the new APIs are different.

We understand that many of you have production systems running on our older version of APIs. We are fully committed to ensuring no disruption to your usage. Should you wish to migrate to the new APIs for all the good things it offers, we would be happy to work closely with you to migrate your integration.

Get started

We hope the simplified use model expands the imagination of what developers can build with movement data, and makes is possible to build it easily within minutes. We would love to hear about what you are building with HyperTrack and share it with the rest of the community.

If you haven't started yet, please sign up and start building today!