Currently when we begin an email promotion, I create an outside source code so I have an active source that we can use for building and testing the web promo code. This is also the source code we use for all ticket transactions.
Then I run the extraction for the email list which creates inside source codes that I have to mark inactive. I prefer running the extraction as close as possible to deploying the email message in order to capture the most recent data (new subscribers, unsubscribes, no email suppressions, etc.).
Does anyone do this differently or have a recommendation? It feels like a redundancy, but I'm not sure there's another way.
Thanks!Clint
Hi Clint,
The standard way to avoid that redundancy is to run your extraction first and use the source or sources created for your web promotion. These days it doesn’t take very long to set up web promotions and offers. You can add offers to multiple performances from season manager. And it only takes a few minutes to add an entry or two to TR_WEB_SOURCE_NO. I think in most cases the changes in your data between when you run the extraction and when you send out the email will be pretty small and worth accepting in exchange for better source usage and less redundancy.
Kevin Sheehan
Documentation & Learning Resources Specialist
Tessitura Network
1 888 643 5778 ext 329 Office
ksheehan@tessituranetwork.com