Good afternoon -
We use the triggered email functionality in WordFly to sent out our pre- and post-show email campaigns. As we upgraded to v12, I had the opportunity to take a closer look at the set up of our accompanying dynamic lists and realized there's nothing in our criteria that's suppressing the constituents without email addresses on file. Ticket history and permissions, we're good, but not empty fields. This "bad" data causes discrepancies in coding promotions and errors in WordFly, so I'd love to correct the list.
The current set up for the pre-show ones is this:
Ticket Performance Date >= DayRunDate +3Ticket Performance Date <= DayRunDate +3Ticket Season IN (1 value selected)E-Market Restriction IN (1 value selected)Ticket Venue IN (1 value selected)Electronic Address Purpose IN (2 values selected)
We tried adding "EAddress Like %@%", and while it does change the count, there are definitely still records without email addresses on my list.
Short of doing a complete database clean up to make sure we've tagged every email address with exactly the right primary statuses and purposes, any recommendations as to what I can try next? Manual/SQL editing is ok, though I'd prefer to keep using the Graphical Edit if possible so that the query logic is accessible to anyone who needs to look at it.
Thanks very much,
Jamie O'BrienAssistant Director of Digital ServicesThe New 42nd Streetjobrien@new42.org
Jamie -
Not sure if this will help in your specific situation but just in case...
We also use Wordfly for pre/post-show triggered emails, but use custom local tables and output sets to pull the data to send to Wordfly. However, I do know that for other emails, we generally use an output set that pulls the primary email address to send to Wordfly. Could the issue be with what your output set is pulling (regardless of your list setup?)
It may also depend on who "owns" the email addresses, and who "owns" the ticketing data. In our case, tickets are sold to the household, but emails are on the individual, so that can also pull in incorrect or missing email data. So we like to create TWO lists whenever we are sending an email - one to grab the accounts with matching criteria (whatever that may be) - then a second list to "convert" the first into an "email list".
The first list is created, using whatever business criteria you need (except eaddress, that comes later), then "Replace with Household" is checked at the bottom, so we roll up to all households. Save that list.
For the second list, we reference the first list using the criteria element "Other->List", and check the "Search Household" box next to that. Then we add the criteria element "EAddress Primary Flag" In "Yes" - leaving "Search Households" unchecked - and this effectively gets people with primary AND active emails on INDIVIDUALS all in one swoop.
When Wordfly uses this list and an output set pulling primary emails, they only receive customers with active, primary emails. Then the only discrepancy is that they will still receive the promotion in Tessitura, when they may be "unsubscribed" in Wordfly. (But that is a different discussion...!)
Hope these details might help. Now you see why we use a custom procedure for pulling 140 different pre/post-show emails every season. :)
Beth
Wow, Beth.
My brain hurts just thinking of all the work that must go into pulling those lists.
When you say wordfly only pulls the primary email address, are you referring to the check box ind(with the star) or are you referring to the primary email address type? I think we are having issues with multiple primary email address types existing on one account and not knowing which type is used for what. :(
The setup at UMS pulls the "starred" primary address. That is how we setup the Output Set for Wordfly to use. As long as your output set only pulls one row per person, it will work for Wordfly, I believe. If you have multiple email types on one person, and your output set pulls all of them, I'm not sure it will work.
VERY looking forward to version 12 and contact points - likely we'll move people's interests there so we know exactly which email gets what. Hope that helps!
Sure does! :) Thanks Beth!