• User goal: Not only do I want to send requests, I would like to save them for later in an organized way so that I can easily reference them when I need them later. (Qualitative data gathered from a user survey)
• Business objective: Increase % conversion of users who sign-up and create a collection
• Hypothesis: If we can nudge users to save requests from their history to a collection, then we can increase the amount of users who have meaningful collections, thus increasing retention.

Past experimentation

Control

Variation

In a past experiment, users who did not have collections in their workspace but had at least 5 requests in their send history with the same domain would get recommended to save those to a collection via a nudge in the History sidebar.

Experiment results

Primary metric: % of users creating collections within 7 days

The variation design caused a drop in users creating collections within 7 days of seeing the nudge.

Secondary metric: % of users creating collection history within 7 days

(Collection history at Postman is defined as requests sends from those that are saved into a collection)

We also saw a drop in users sending requests within collections, which makes sense given the decrease in the primary metric.

What happened?

Because users were dropped into the History tab instead of the Collections tab, they could send requests and see their requests getting added to their history, thus not seeing the need for saving them into a collection.

Revisiting the problem space

Now that our strategy as a team has been more focused around increasing the amount of users who have meaningful collections, we thought that it would be interesting to iterate on this original idea and see if there is a more contextual time to nudge users into saving their related request history into a collection.