Hi Tommy! We recently returned to TM (with Mailgun as the email provider) for our eblasts and external mail list signups. I’m not familiar with WordFly, but our prior eblast process used a custom API-integration between TM and InfusionSoft. The integration was not overarching, but allowed incoming mail list signups to check the email address against the patron database before creating a new account and connecting InfusionSoft’s unsubscribe to a patron’s do-not-email flag. We managed the lists themselves in both programs independently, however, pulling and updating our essential “seed” lists from TM using relevant criteria, but also using InfusionSoft’s built-in grouping features for segmentation, etc.
It was not perfect, but far better data management than we had previously with manual unsubscribe imports and totally separate “email” databases for our general newsletter. I was only tangentially related to the day-to-day blasting process, but am happy to ask the folks on my end more specific questions if you have them.
It might be important to note, however, that in our new Covid financial reality, we decided to leave our InfusionSoft costs behind. And while I’m sure the Marketing department salivates for a few of the more advanced dedicated email marketing tools that InfusionSoft (and previously Informz) provided, we have easily and quickly been able to meet all of our fundamental email marketing and signup needs with TM’s existing features/services.
As for embedding ticketing pages into our main website, I’m not fully sure I understand the question. Our “buy”, “donate now” and “signin to your account” buttons link directly to the relevant webstore pages. If it’s relevant, however, we do still use a custom integration between TM and our main site for our ticketed event pages. The importer pulls event title, performance dates and times, etc to create an initial event landing page that we then “prettify” on Wordpress. The importer also allows for semi-automatic “buy” button appearance when the performance is set to go on-sale online.
Once again, we paid a local agency to write this custom code for us. I will note that this particular integration hasn’t been as flexible as we needed and as it’s complex coding, we don’t have the in-house skills to update it when we run into a new or unplanned use case. Some examples include alternative venues, performances we couldn’t delete but shouldn’t appear, accidental performance number node deletions from Wordpress, etc. Most recently, we’ve had to go around the importer and do manual event landing pages for virtual content that can be bought and viewed for extended time after the performance datetime. Obviously these are new needs and TM fields that we couldn’t have accounted for when we had the integration built, but our inability to continue customizing it cheaply and quickly is a factor worth noting.
Hope this helps a little!