Skip to contentSkip to navigationSkip to topbar
On this page
Looking for more inspiration?Visit the
(information)
You're in the right place! Segment documentation is now part of Twilio Docs. The content you are used to is still here—just in a new home with a refreshed look.

Hawkei Destination


Destination Info
  • Accepts Page, Group, Identify and Track calls.
  • Refer to it as Hawkei in the Integrations object
  • This integration is partner owned. Please reach out to the partner's support for any issues.

Hawkei(link takes you to an external page) provides real-time accurate error detection for your key user paths and product features. Pinpoint the root cause of an issue easily with all the meta data delivered straight to your inbox or slack channel.

This destination is maintained by Hawkei. For any issues with the destination, contact the Hawkei Support team.


Getting Started

getting-started page anchor
  1. From the Segment web app, click Catalog.
  2. Search for "Hawkei" in the Catalog, select it, and choose which of your sources to connect the destination to.
  3. In the settings, enter the following fields:
    • API Key: You can find your Api key inside the Api Keys settings(link takes you to an external page).
    • Workspace: Enter the Hawkei workspace where you want your Segment events to be sent. You can see a list of all your Hawkei workspaces in your Workspace settings(link takes you to an external page).
    • Environment: Enter the environment you are sending events from. If you don't know what to set you should set this field to production.

If you aren't familiar with the Segment Spec, take a look to understand what the Page method does. An example call would look like:

analytics.page()

When you call page, we store it as a page event inside Hawkei. You can use this event to create your flows.


If you aren't familiar with the Segment Spec, take a look to understand what the Identify method does. An example call would look like:

1
analytics.identify('userId123', {
2
email: 'hans.solo@hawkei.io'
3
});

Identify calls will be sent to hawkei as an identify event. The associated user data will be stored in identities and all the relevant flows will be attached to this user.


If you aren't familiar with the Segment Spec, take a look to understand what the Group method does. An example call would look like:

1
analytics.group('groupId123', {
2
name: 'Millenium Falcon'
3
});

Group calls will be sent to hawkei as an group event. The associated group data will be stored in groups and all the relevant flows will be attached to this group.


If you aren't familiar with the Segment Spec, take a look to understand what the Track method does. An example call would look like:

analytics.track('Clicked Login Button')

Track calls will be sent to Hawkei as a track event. Use the method track anywhere you want to create an event in your code.

You'll want to create events that are part of critical paths in your application that you intend to add to the flows you want to monitor.


AnonymousId

anonymousid page anchor

All requests to Hawkei require an anonymousId to be set. Segment sets this automatically on client-side libraries, but for server side libraries (php, Ruby etc) this needs to be explicitly set.


Segment lets you change these destination settings from the Segment app without having to touch any code.

Property nameTypeRequiredDescription
API Keystring
required

You can find your API key under Settings.


Environmentstring
required

The name of your environment


Workspacestring
required

The name of your workspace