Hello!
As we approach our 2023 season, we are trying to market to our constituents based on their interests. We'd like to send them information on different shows that we believe they would be interested in based on their past ticket history, but if they've already purchased tickets for that show, we'd like them to fall into their next highest interest and get information on another show that they would also likely be interested in.
The problem we're running into is we can't look at both interests and ticket history for upcoming shows in the same extraction. The interest weight lives in one place (though it does calculate interest weight based on ticket history perf no's) and the ticket history is in another, so using the two criteria in a single extraction segment doesn't seem to yield the right results.
Is there a way to get ticket history pulled in so that we can evaluate both interest AND current season ticket history in one segment? We don't want to suppress buyers of upcoming shows, because then they wouldn't be able to be caught in another interest segment. Is there another way to accomplish this?
Thanks,
Michael Dorsey
Hey Michael,
So you are getting a customer segments using Extration and you want to pull Ticket History and weighted interest through you Output set?
I usually start with what list criterion do I need to get my list, through either Lists (or Extractions if it particularly complex). And then when I have the right people then plan out the data pull through Output Set elements. With the Output Set it souds like you'll have a single Max interest but mulltiple rows of performances/productions from Ticket History that you'll probably have to filter by something like Season (2023). There's a bit more info here.
Now if you want all the 2023 performances in a single Output Set row, like a comma delimited string (or built into a HTML table in the case of outputing to word fly), you'll need to make a local View, which a few of us I know have done before.
BestH PS: the weighted interest sounded great BTW
BTW, re: weighted interest, I can't take all the credit for this piece. I recycled some of the logic that our pre-built customer interest procedure uses (that I believe Tessitura made for us) to create interest (we're calling it "Affinity") weight, then changed the T_KEYWORD infrastructure that it's based on (different "affinities"), and made the procedure so it only looks at the past X number of seasons, as interests can change over the years.