Hello WordFly users,
Has anyone ever had the problem of using a list in WordFly, making changes to the list on the WordFly side (removing subscribers), then having a promotion assigned to the record anyway? Ideally, a promotion would only be added to a record if the email was sent to them--or at least attempted to get sent to them. Do you have any ideas for how one might go about correcting said issue (short of hopping in a time machine and correcting the list on the Tessitura side)?
Thanks in advance for any insight you feel inclined to share!
Michael
Heath Wilder is correct - the promotions are added when the list or extraction is pulled in to WordFly. You can find more details in their support doc.
But yes Michael Dorsey you highlight a good point in that the promotion record is not a record of whether the constituent record was sent the email, rather that they were included in the list that was passed to WordFly. If WordFly doesn't send to them for whatever reason - unsubscribe, suppression, invalid email etc - then that data only lives in WordFly and does not end up back in Tessitura.
All this highlights that for email campaigns the only real source of truth is WordFly itself. Tessitura constituent records will have gaps.
Thank you, David Geoffrey Hall and Heath Wilder, for taking the time to respond. As I pondered this further today, I realized that some of this is inevitable. I think what it comes down to is we need to do our best on the front-end to weed out the gap points on the Tess side so there's minimal change made to the list on the WordFly end. I feel like it's easier to do with extractions, but one wrong setting in communication mgmt will put a source on a record that will not be included once it gets to WordFly. It's good to know I'm not alone in seeing this discrepancy. Thanks again!
Although this has mostly wrapped up, I'll add one reaction it prompted for me:
Depending on what work you are tackling when editing subscribers in WordFly, you might be able to do that same manual effort in Tessitura pre-import. You'd have to be using a List rather than an Extraction, and I only think this is is remotely practical if you're removing names because you're seeing them and recognizing them as candidates to remove--a small-ish and 1:1 exercise. But for situations where you are cherry-picking what to cut, doing it within the Tessitura List will avoid them getting the promoted source.