Identify Users and Accounts
Get insights into which users and companies are engaging with your product.
Endpoint
To send events from the server side you will use our events API with an s2s token which will be available during onboarding. Kindly use the following endpoint and attach the identify or track payload in the body. You can also send bulk requests in a single call by sending the payload as an array.
https://events.hyperengage.io/api/v1/s2s/event?token=YOUR_SERVER_TOKEN
Users
Overview
This guide will walk you through the identify method to effectively identify your product’s users. By doing so, you can monitor which users are triggering events in Hyperengage. It’s advisable to integrate this code snippet where user sign-ups, logins, or account details are updated.
Code Implementation
Replace YOUR_USER_ID with a distinct identifier, ideally the user ID from your database. It’s also madatory to add your user’s name and email. It’s also beneficial to include the user’s other “traits” such as avatar, role, etc. This data will be displayed on the user’s profile and can be utilized to filter users in reports. You will also need the WORKSPACE_KEY and API_KEY which will be provided during onboarding.
Companies
Overview
For B2B products, it’s common to have multiple users accessing your product within a “workspace”. This guide offers instructions on the group method to effectively identify companies using your product.
By implementing this, you can monitor company-level usage in Hyperengage, view individual company profiles, and see the users associated with each company. It’s recommended to incorporate this code snippet alongside your identify call, such as during user sign-ups or logins.
Code Implementation
Substitute YOUR_ACCOUNT_ID with unique identifiers, ideally the workspace ID from your database. It’s also mandatory to include the company’s name. Any other “traits” such as avatar, company_size, etc can also be added. This information will be displayed on the company’s profile and can be utilized to filter companies in views. You will also need the WORKSPACE_KEY and API_KEY which will be provided during onboarding.