Nudge (Actions) Destination

1. From your workspace's Destination catalog page search for Nudge.
2. Select Nudge and click Add Destination.
3. Select an existing Source to connect to Nudge (Actions).
4. Go to the Nudge dashboard, and navigate to the Settings page.
5. Go to the Secret Keys section and click Create new secret key.
6. Give an appropriate name for the key, then select the Backend API option from the permissions dropdown and create the key.
7. Copy the generated key and store it somewhere safe for future reference.
8. Paste the generated API key in the Nudge destination settings in Segment.

The Nudge (Actions) Destination currently supports the Identify and Track methods listed below in accordance to the core Segment Specs. Reference: Spec Overview

The Identify method lets you create or update a user in Nudge's backend. Every Identify call should include a userId. See Segment's Spec for Identify for any reference: Identify Spec

Example (using Segment's Analytics.js SDK):

1
analytics.identify('user123', {
2
  name: 'Alice Smith',
3
  email: 'alice.smith@example.com',
4
  company: 'Acme Corp',
5
  employees: 150
6
});

How Nudge handles Identify calls:

• If userId doesn't exist, the request throws a 400 validation error as it's a required field.
• If userId already exists, Nudge merges or overwrites profile properties with the latest values.
• Identify calls without userId, or with only anonymousId, are dropped.

The Track method sends custom events and their properties into Nudge. You must include event name in every Track call so events can be associated with the correct user. See Segment's Spec for Track for any reference: Track Spec

Example (using Segment's Analytics.js SDK):

1
analytics.track('Product Viewed', {
2
  product_id: 784,
3
  product_sku: 'SH#79817'
4
});

How Nudge handles Track calls:

• Segment ensures the userId is attached to the Track call for a previously successful Identify.
• Events without a valid userId or with only anonymousId are dropped.
• All other event properties are ingested as event metadata and can be used for trigger conditions.

Build your own Mappings. Combine supported triggers with the following Nudge-supported actions:

• Identify User
• Track Event

Identify a user in Nudge

Identify User is a Cloud action. The default Trigger is type = "identify"

Send an event to Nudge

Track Event is a Cloud action. The default Trigger is type = "track"

Events may not show up in Nudge due to one of these reasons:

• Missing or invalid API key: Ensure that the API key you generated under Settings → Secret Keys → Backend API is correctly entered in your Segment destination settings.
• Dropped Identify/Track calls: API requests to Nudge's servers without userId, or with only anonymousId, are automatically dropped. Verify your mapping includes the correct identifier field.

Nudge expects all date/time properties in UTC ISO-8601 format (Javascript Date object's ISO format). If you see failed events due to timestamp validation:

• Confirm you're sending dates like "2025-05-14T07:30:00Z".
• Remove any timezone offsets other than Z (UTC).

If requests continue to fail after checking your API key and payload:

• Compare against Nudge's specification from the documentation: Nudge's Documentation.
• Ensure all required fields (for example, userId, event name for Track) are present and correctly typed.

If you still encounter issues, please reach out to the Nudge Developer Team or email support@nudgenow.com.

You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.

For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it's been more than 30 days since their last order), Engage sets that value to false.

When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

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