Importing Wifi Email Capture

Hello, 

For the last couple of years, we've been capturing customer email addresses for those people who wish to use our wifi whilst on site. We are then sending marketing emails to those people. At the moment, we're managing those email addresses outside of Tessitura and importing them as a separate list into Wordfly but it's starting to become an issue as the numbers grow. 

Is anyone else capturing email addresses via wifi, and if so, are you importing those into Tessitura and creating accounts for them? 

We have a concern that by creating accounts for people who have not gone through the full sign up process may be a barrier for ticket sales as they won't realise they have an account and will try to set up a new account with the same email address and then get an error to say that an account with that email address already exists. 

Many thanks
Gemma 

Parents
  • Hi Gemma, 

    We are looking at the exact same thing here! We are looking at making a API call at the time the email is added, if they are already in Tessitura it won't create a record if they are not it will. We are still ironing out the details with this so can update once we are confirmed. 

    Now dealing with email only records... This is a bigger hurdle! I think we are going to look at creating a procedure that will add a temp login to those emails so when/if they do go to book we can get them to their already existing account.

    We are also intending to update our merge procedure to identify dups based on email addresses. We are of the feeling that is a pretty good unique identifier.

    There are quite a few intended/ifs/looking tos here, we still have a lot to discuss internally but is good to know someone else is also looking at this. 

    Kelly 

Reply
  • Hi Gemma, 

    We are looking at the exact same thing here! We are looking at making a API call at the time the email is added, if they are already in Tessitura it won't create a record if they are not it will. We are still ironing out the details with this so can update once we are confirmed. 

    Now dealing with email only records... This is a bigger hurdle! I think we are going to look at creating a procedure that will add a temp login to those emails so when/if they do go to book we can get them to their already existing account.

    We are also intending to update our merge procedure to identify dups based on email addresses. We are of the feeling that is a pretty good unique identifier.

    There are quite a few intended/ifs/looking tos here, we still have a lot to discuss internally but is good to know someone else is also looking at this. 

    Kelly 

Children
No Data