Unwaffle Destination

Unwaffle helps SaaS businesses improve their Free Trial conversion rates. By tracking every action that your trialers take, Unwaffle can discover patterns that lead to successful conversions and provide actionable recommendations to boost trial funnel performance.

This destination is maintained by Unwaffle. For any issues with the destination, contact the Unwaffle Support team.

Getting Started

1. From the Segment web app, click Catalog.
2. Search for “Unwaffle” in the Catalog, select it, and choose which of your sources to connect the destination to.
3. In the Segment Settings UI “API Key” field, paste the “Public Key” for your Unwaffle Project, which you can find from your Unwaffle KeyPair list.
4. Familiarize yourself with the Basic Concepts section of the Unwaffle API Documentation, including the list of Stock Labels that must be implemented for the service to function.

Identify

If you’re not familiar with the Segment Specs, take a look to understand what the Identify method does. An example call would look like:

analytics.identify('12345', {
  email: 'john.doe@example.com',
  name: 'John Doe'
});

Identify calls will be sent to Unwaffle as an AddParticipant event and must include a userId. Unwaffle does not support anonymous activity and such activity will be dropped from sending.

Track

If you’re not familiar with the Segment Specs, take a look to understand what the Track method does. An example call would look like:

analytics.track('TrialStart')

Track calls will be sent to Unwaffle as an AddAction event.

IMPORTANT: Unwaffle does not support anonymous activity. Ensure that you have identified the user before calling Track.

Engage

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.

Settings

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