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.

Atatus Destination


Destination Info
  • Accepts Page and Identify calls.
  • Refer to it as Atatus in the Integrations object
Connection Modes
Device-modeCloud-mode
Web Web
Mobile Mobile
Server Server

Atatus(link takes you to an external page) provides visibility into the performance of an application and its underlying infrastructure under a single dashboard. This visibility can help businesses identify and diagnose issues, and take corrective action to prevent or resolve application issues.


Getting Started

getting-started page anchor

Before you start, make sure Atatus supports the source type and connection mode you've chosen to implement. You can learn more about connection modes here.

  1. From the destinations catalog page in the segment web app, click on Destinations -> Add Destination.
  2. Search for "Atatus" in the destination catalog and select Atatus as the destination.
  3. Click on Configure Atatus.
  4. Choose which Data Source should send data to the Atatus destination and click Next.
  5. Enter the desired destination and click Save. You will be navigated to the settings page where you will have to add the API key to start receiving insights.
  6. You can find the API key in your browser project settings.
  7. Enter the API Key in the Atatus destination settings in Segment.

Identify

identify page anchor

If you're not familiar with the Segment Specs, take a look to understand what the Identify method does. An example call would look like this:

1
analytics.identify('userid_123', {
2
name: "John Doe",
3
email: "johndoe@example.com"
4
});

When you call Identify, the Atatus SDK calls atatus.setUser by passing in the traits you provided. Atatus maps the userId you provide as traits.id, which you can use to track user activity and gain a specific user's performance insights.


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

Property nameTypeRequiredDescription
Whitelist Urlsarray

Optional

Captures the page views, AJAX and JS Errors from the given domains or URLs and ignores insights from all other URLs.


API Keystring
required

To find your API Key, create a project in your Atatus dashboard. The key should look something like this: 16ae323d8b3244733a981215c9d66e67d


Disable AJAX Monitoringboolean

Optional

If you don't want to track the AJAX(XHR) requests in your app, then select this option.

Default: false

Disable Error Trackingboolean

Optional

Set this to true to disable error tracking.

Default: false

Disable RUMboolean

Optional

You can disable RUM metrics by setting this option to true.

Default: false

Disable Sessionboolean

Optional

You can set this option to true if you want to disable reporting of session traces.

Default: false

Disable SPAboolean

Optional

Set this option to true to disable SPA monitoring.

Default: false

Disable Transactionboolean

Optional

You can disable the collection of transactions by setting the option to true.

Default: false

Enable Offline Errors and Metricsboolean

Optional

Enable offline errors and metrics tracking when network connectivity is not available.

Default: false

Hash Routesboolean

Optional

Atatus removes the hash from the URL and if you're using hash based routes you can set this option to true.

Default: false

Ignore Errorsarray

Optional

It is an array of unwanted error messages to be filtered out before being sent to Atatus as either array or regular expressions or strings.


Ignore Urlsarray

Optional

Ignore capturing insights from a given set of domains or URLs.


Report Unhandled Rejectionsboolean

Optional

This allows disabling or enabling the unhandled promise rejection errors.

Default: true

Versionstring

Optional

Helps you in filtering the errors from the dashboard using the version.