772573 - Capture email addresses for surveys

Status: RESOLVED FIXED

(support.mozilla.org :: General, defect)

Description

[Matt Grimes [:Matt_G]]

We are implementing a CSat type of survey and we need a better way to solicit users willing to participate. To facilitate this survey, we will need:

1. Ask 1% of all users coming to the site if they are willing to participate in a survey. 
2. The user would input an email address if they are willing to participate.
3. The email addresses will need to be stored in the DB and easily accessible.
4. We will need to issue a cookie that prevents the same user from being asked to participate for 3 months.

Comment 1

[Bram Pitoyo [:bram]]

I wonder if we can use Ethnio for recruiting purposes? You would have seen them before and know how it works. Does that fit our purpose, or will we have to design our own survey recruiting solution?

Comment 2

[Ricky Rosario [:rrosario, :r1cky]]

(In reply to Bram Pitoyo [:bram] from comment #1)
> I wonder if we can use Ethnio for recruiting purposes? You would have seen
> them before and know how it works. Does that fit our purpose, or will we
> have to design our own survey recruiting solution?

Good question. Can we do that instead? Matt_G/Ibai?

Comment 3

[Matt Grimes [:Matt_G]]

I spoke to Ibai, Kadir, and Ricky during the work week. Here is our new plan.

1. We will use Ethnio to capture email addresses for the time being. We will need Bram or Crystal to help us to manage that.

2. There is already code in place on Kitsune to use Ethnio. If that code needs to be updated, Ricky will be on the hook for that. We will file that as a separate bug if needed.

3. We will use the Ethnio approach for a while to be certain that we are getting the results and experience we are hoping for. If we decide that we need a more integrated solution at a later point, we will integrate this process into Kitsune. 

Let's pull this bug out of the current sprint. We'll keep it open though in case we need an integrated solution down the road.

Comment 4

[Ricky Rosario [:rrosario, :r1cky]]

Moving out of sprint (See Comment 3)

Comment 5

[Kadir Topal [:atopal]]

Bram, do we need a new JS snippet for every campaign, or can we control the campaign from the ethnio website without touching anything in our code?

Comment 6

[Bram Pitoyo [:bram]]

(In reply to Kadir Topal [:atopal] from comment #5)
> Bram, do we need a new JS snippet for every campaign, or can we control the
> campaign from the ethnio website without touching anything in our code?

In the past, UX has done a sample size of between 30–80 people in one go, and direct users to a survey tool (e.g. TreeJack) after they are done with Ethnio.

Because we were able to get qualified users very quickly, we only needed to turn the Ethnio waffle flag up for a few hours at most.

Rather than use multiple Etnio campaigns—a different JS file for each survey—we use one campaign and one file for everything. Sorting out the resulting .CSV files is manual work, but it’s fairly easy to sort out the one we wanted, as the date/timestamp between the survey is usually far apart.

The short answer is, yes, we can control the campaign from the Ethnio website, if we elect to just manage one campaign, and separate the result from each manually.

Comment 7

[:ibai]

We are going to need a more automated process to do this. Should we reopen or create a new bug?