Inleads AI Destination

1. From the Destinations catalog page in the Segment App, click Add Destination.
2. Search for Inleads in the Destinations Catalog, and select the Inleads destination.
3. Choose which Source should send data to the Inleads destination.
4. Go to the Inleads dashboard and find the API Key in Settings API Keys tab.
5. Enter the API Key in the Inleads destination settings in Segment.

Inleads supports the following methods, as specified in the Segment Spec.

Send Identify calls to create new user profile or update existing users with new trait values. For example:

1
analytics.identify("inleadsUser123", {
2
  email: "test@example.com",
3
});

Segment sends Identify calls to Inleads as an identify event.

Send Track calls to record user behavior in your app. For example:

analytics.track("New lead created");

Segment sends Track calls to Inleads as a track event.

Send Group calls to associate an individual user to group. For example:

1
analytics.group("0e8c78ea9d97a7b8185e8632", {
2
  name: "Initech",
3
  industry: "Technology",
4
  employees: 329,
5
  plan: "enterprise",
6
  "total billed": 830
7
});

Inleads AI has the following presets

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

• Group
• Track
• Identify

Send group calls to Inleads AI.

Group is a Cloud action. The default Trigger is type = "group"

Send track calls to Inleads AI.

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

Send identify calls to Inleads AI.

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

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.