How to integrate Unify with Amplitude

Before connecting

• A Unify Play with a Webhook action and a controlled record for testing
• Access to the intended Amplitude environment and the permissions required by the cited API or trigger
• The destination identifiers, credentials, and schema used by the request below
• An agreed record identity, duplicate policy, and owner for failed handoffs

1. 01

   Prepare the Amplitude destination

   Choose the Amplitude project and its data residency. Define a user_id consistent with the project’s existing identity strategy.[3]

2. 02

   Configure the destination action

   Send the HTTP V2 envelope with api_key and events. Use an event_type that describes the actual Play action rather than a guessed customer outcome.[3]

3. 03

   Configure the Unify request

   Use POST, the endpoint and authentication below, and JSON body format in the Webhook action. Replace setup placeholders, then inspect Expand preview with a controlled record. The receiver must respond within 8 seconds; webhook response bodies are not exposed to later Play steps.[1][2]

4. 04

   Validate the complete handoff

   Run the success and edge-case scenarios in Explore the scenarios with a controlled record. Save the request identity and destination evidence, then apply the completion check before enabling live traffic.[3]

{
  "api_key": "YOUR_AMPLITUDE_API_KEY",
  "events": [
    {
      "user_id": "example-person-001",
      "event_type": "Prospect handoff",
      "event_properties": {
        "company_domain": "example.com",
        "source": "Unify"
      }
    }
  ]
}

Illustrative JSON for the documented receiving operation. All prospect values are fictional. Replace credentials, identifiers, schema-specific fields, and fixed example values before a controlled test. Use the field mapping to distinguish record data from fixed settings. Select available fields in your Play and inspect Expand preview; do not replace configuration values with prospect data.[1][2][3]

The project key is a credential, not a prospect field. Put business context in event_properties and retain the agreed user_id.