Use this link to share with your colleagues:
CRM Snapshot Enhancements (June 2016): https://help.pm.leapevent.tech/a/547905
This article is old! Wouldn't you rather read something... fresher?
There may be outdated information or suggestions in this article that made sense at the time of the release, but no longer. For the most up-to-date information about this topic, use a keyword in the search bar above. If you're looking for more current release notes, you can find those here.
We made some improvements to CRM Snapshots so you'll get your results faster and have more options for targeting your messages.
Run Again: Re-run your completed Snapshots for the most up-to-date data
Clicking the new "Run Again" link in the Completed Snapshots list will... run the Snapshot again! You'll get a new report with updated data that uses exactly the same parameters as before.
This makes re-running an open-ended Snapshot (without a specific time frame) really quick and easy, since (for example) you won't have to select from a long list of events just to run the same query you ran last week.
Post-performance "Who was there?" filter
If you're scanning barcodes on tickets to check people in, you can now use that data to make sure you're sending post-performance emails only to patrons who actually attended the show.
Use the new "Attended" filter on ticketing-related CRM Snapshots to return a list of patrons who had their tickets scanned for specific performances.
Account Rollup
We also added the Account Rollup option to the "Patrons for whom a certain event was their first" Snapshot so that you can evaluate the ticket-buying history of an entire household when you run that query.
Often, one member of a household does most, if not all, of the ticket purchasing for a household, and you don't want to inadvertently target patrons as "non-attenders" if they've actually been attending your shows with their partner. With this new rollup, you'll be able to target patrons where none of the household members have made a previous ticket purchase, instead of just looking at the individual patron's purchasing behavior.
Improved CRM Snapshot performance
We improved the way larger snapshots (with larger numbers of patrons) are handled, which will prevent these Snapshots from occasionally getting "stuck" in the queue.
