Skip to main content
Datadog gives Superhawk the experience side of product usage: not just what a customer did, but whether it worked. Errors and failed sessions are direct evidence for the friction that shows up on the account.

​
Prerequisites

  • A Datadog API key and Application key with read access
  • The integrations permission in your Superhawk workspace

​
Connecting

1

Get your Datadog keys

In Datadog, go to Organization Settings and create (or copy) an API key and an Application key. Both are required.
2

Open Integrations in Superhawk

Go to Integrations and find Datadog under Errors & Observability.
3

Enter both keys and your site

Paste both keys and select your Datadog site. Superhawk verifies access immediately.
Select the right Datadog site. Datadog runs several regional sites and the API endpoint differs for each. A valid key against the wrong site fails to authenticate, which is a common reason correct credentials are rejected. Check the domain you log in at.

​
What Superhawk pulls in

  • Session replays — how users moved through the product
  • Errors — what failed, and in which sessions
  • RUM analytics — real user monitoring data

​
What it feeds

  • Friction on the account — where the product got in the customer’s way
  • Hawkeye View — sessions with errors, and the friction penalty
  • Account health — experience quality as a health factor
  • Signals — error spikes and repeated failures
Error evidence is unusually persuasive in a customer conversation. Raising a problem before the customer does, with the specific sessions in hand, changes the tone of a renewal discussion considerably.