AB Tasty Destination

AB Tasty lets you build end-to-end experiences that drive growth across all digital channels. Marketing, product and engineering teams work together to deliver seamless user experiences with AB Tasty.

AB Tasty maintains this destination. For any issues with the destination, contact the AB Tasty Support team.

1. From the Destinations catalog page in the Segment App, click Add Destination.
2. Search for AB Tasty in the Destinations Catalog, and select the AB Tasty destination.
3. Choose which Source should send data to the AB Tasty destination.
4. Go to the AB Tasty settings interface and navigate to Integrations > API Key.
5. Click Generate API Key (if the API key doesn't already exist) and copy the API key.
6. Enter the API key in the AB Tasty destination settings in Segment.

AB Tasty supports the following methods, as specified in the Segment Spec.

Send Identify calls to AB Tasty webhook. For example:

1
analytics.identify('userId123', {
2
  email: 'john.doe@example.com',
3
  trait1: 1,
4
  trait2: "test",
5
  trait3: true
6
  },
7
});

Segment sends Identify calls to AB Tasty as an identify event. The AB Tasty data engine then ingests the different traits associated to the identified user.

Traits received are then available in the AB Tasty segment builder.

Send Group calls to AB Tasty webhook. The AB Tasty data engine then ingests the different traits associated to the identified group. For example:

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

Segment sends Track calls to AB Tasty as a group event. The AB Tasty data engine then ingests the different traits associated to the identified user.

Traits received are then available in the AB Tasty segment builder.

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.