Hi all,
Currently, we are running Abandon Cart and Browse emails by working with Behavior Infuser which integrates directly with Tessitura, allowing us to create triggered emails based in WordFly. Does anyone have any other processes for this? I think a few years ago I remember someone saying they do Abandon Cart emails by utilizing a Tessitura script, but I could be wrong.
Would love to hear about how anyone else runs these campaigns!
WordFly have a set of Abandoned Cart local tables and StoredProcs (which I thinik was "My First Integration" all those years ago)
https://support.wordfly.com/hc/en-us/articles/204768604-Automated-Abandoned-Cart-email
It's relatively easy to set up with a bit of SQL/SSAgent knowledge.
You'll definitely want to adjust your stored values (eg: production season number, Perf ID, etc) and the criteria for "What is abandoned" (eg: Merch? Contributions?). Understanding the Web tables as separate to the Order tables I think is a very useful part of your Tessitura education - especially for marketing, ticketing and anyone web focused. I can tell you the times it's saved my life to get back abandoned cart form information out of web session tables, or rebuilding what people had in their carts when a server crashed.
Heath Wilder I am implementing the Abandoned Cart process from the WordFly support page. I encountered that joining LT_WF_ABANDONED_CART with T_WEB_LINEITEM to retrieve the zone, and the perf_no eliminates 99% of orders. Have you experienced similar behavior? Thanks!
Sabina from San Diego Symphony.
Do you know what orders it's clearing (is it the "Find abandoned carts for testing" script?). Do you mean that 99% of T_ORDER order_no.s don't have a corresponding analogue in T_WEB_LINEITEM? If that's historic orders maybe it's because your UP_CLEAR_WEB_TABLES is clearing out the data after 30 days (I think that's Hosting Services default).
hello.tessituranetwork.com/.../10730371
I don't think so. I used the script to build the LT_WF_ABANDONED_CART table. I have 180 records in this table for December 14, 2022.
When I join the LT_WF_ABANDONED_CART table with the T_WEB_LINEITEM, only one record exists in the T_WEB_LINEITEM out of 180.
Interesting. WordFly procedure[1] puts into the Abandoned cart table[2] values from the purchase pathway[3] that don't have an associated completed Tessitura order.
There could be a mismatch if you are joining on customer_no (as well as order_no). If the customer hasn't logged in before they abandon then the orders in the web tables may be set to customer 0 or the anonymous Constituent ID that TNEW uses (if you use TNEW).
To see why the abandoned cart table and the Web Table lineitems are not matching it'd be good to
For my money it's worth modifying LP_WF_ABANDONED_CART to capture zone and perf into into LT_WF_ABANDONED_CARTs detail columns so you don't have to do joins to pull out data after the fact. You might be doing this now but it's worth checking.
H
[1] WF abandonded cart Stored Procedure LP_WF_ABANDONED_CART
[2] WF abandonded cart Locat Table LT_WF_ABANDONED_CART
[3] Tessitura purchase path web order table T_WEB_ORDER are written to the Order Table T_ORDER when the purchase is completed. Entries are usually deleted in 30 days by the utility procedure UP_CLEAR_WEB_TABLES that runs on a schedule. Values coppied to the abandoned cart table daily are (order_no, order_dt, customer_no)
[4] The web order structure mirrors the completed order structure. As it is in the client orders in T_ORDER have values (eg: order_no), and may have line items in T_LINEITEM like performance number and zone, and they can in turn have values when seated in T_SUB_LINEITEMS like seat id, recipient, row and seat. The web tables are similar. Whilst you can have entries in the order table that haven't got lineitems (ie: a performance wasn't selected yet) 99% seems like a lot.
Thanks! I discovered that a high percentage of orders w/o associated lineitems in our environment happen when a new customer receives an order confirmation with links to download our app for mobile tickets. Then customers try to create an order from within an app to check if there are fewer fees or different prices altogether. We use a different MOS for buying through an app - that is how I discovered the trend.
Great detective work