Hello! Our team has a few tabling events coming up, and would like to use ipads on site to sign patrons up for our email and create Tessitura accounts.
I believe Create Account Brief is the best mechanism for this, but I'm not sure how to associate those accounts with the on-site activity. We don't see a way to add an Original Source or Activity in the TNEW pathway for this. Is there a better way to approach?
I do know how to add an Activity after the fact, but I'm not sure how I would isolate the list of just those people who opened the accounts on site.
Thanks for any advice!
Hi Jean!
I can get you more info on this from the folks that do it on a regular basis here, but you may want to consider having a simple sign-up form through something like Typeform at the event, then doing an import afterward that creates Tessitura accounts for everyone. Again, I don't know if there are any pitfalls to this in your scenario, but this is how we create accounts for artists that need an account to buy their discount tickets online. You can definitely assign a source en masse to the imported accounts - for example, in the project I mentioned, the original source on all the new accounts is Import - Artist. You could then use a custom field in P2 to thank them for setting up an account and send everyone their temporary passwords.
Let me know if you're interested and I can dig up more info.
Jenn
Jenn!! Hiiiiiiii! :)
Thank you, this is helpful. I've done List imports, but I am not familiar with the Create Account import. It does seem like that might be the easiest way, at least initially, so I will research. If you (or anyone else reading!) can share more details on how that works, I'd appreciate it!
We don't use P2, but I'm less concerned about them actually having accounts they can access. It's more to get them into Tessitura for future list-pulling and Analytics tracking.
Hi Jean,
Here is a link to the Constituent Import utility that Jenn is referring to: www.tessituranetwork.com/.../Tessitura.htm
HI Kevin! Quick question on this - I see how the utility works, but I'm not sure I see a clear way to add this data to a list later. There's no identifier for this group of people.
For example - we'd want to be able to run a Manage Activity utility to drop in "Fall Festival 2023" in their account. But it's not a permanent attribute or anything... so if I import these constituents as a group from the Fall Festival, how would I then create a Tessitura list of just these people?
You can include an attribute in the import and then you can pull a list based on that attribute. Or you can create an Original Source value specific to the event where you are capturing these people, and then select that original source in the utility parameters when you run the import. Then build the list based on original source. Original source is easier to set up, is pretty much intended for this kind of thing, so I would probably go that route. You could always inactivate the Original Source value after you run the import to prevent it from being used manually in the future.