Suggestions on where to keep event survey data

Joanne Felci · October 2022

We are going to start sending a post-event survey to attendees and I'm trying to figure out the best place to keep this info in NXT

We have attendees that go to multiple events so I'll need a place where I can store information for each event on their record

Part of the survey are rate X, Y, Z from 1-5

Part are open ended questions

My first thought was attributes but that can get messy with all the individual events

Now I'm thinking have a participant record in the event that is Survey Results and keep the data there. Or maybe set up an event record for Survey Results-XXX event and then have participant records for each person who fills out the survey for that event and keep the information on that record

Ultimately we want to see what the ratings were for a specific event and then compare event to event

Anyone doing anything like this? Where do you keep the info?

Aldera Chisholm · October 2022

@Joanne Felci We haven't done this yet, but it's been on my mind. I think it depends on how you want to view the info. I'm thinking I want to be able to 1. Pull a list of constituents/participants who filled out a survey (for when I'm measuring their overall engagement) and 2. Pull a query/export so I can see the response scoring per event and see which did higher on “food” vs “speaker” or something like that. Thinking of it that way, I could go for your idea of putting the consolidated results for each event into a “survey" participant, likely using Custom Fields/Attributes, and then I would also be tempted to put a Constituent Attribute on everyone who filled out a survey, as a yes/no regardless of the results. But I feel like this would be cumbersome to manage. Looking forward to other folks ideas!

Faith Murray · October 2022

@Joanne Felci, I see this from 2 angles. If you want to go back to an event 5 years ago and view its success/performance, it seems most natural to include it as a participant attribute for the event itself. However, from the angle of a donor's satisfaction/relationship or for donor follow-up, it would make sense to include it straight on the donor's record.

Myself, I use an Action to record survey results, with Action attributes for each field. I can then pull consolidated survey results in an Action Query. My rationale is that it is an inbound communication from the donor, often including useful opinions and historical info. It also keeps my constituent attributes and event attributes (heavily used fields) clear from extra clutter. It requires manual entry or an Import though, where the Event participant attribute will download directly through an event form.

Dariel Dixon · October 2022

You know @Joanne Felci that we have to try to forecast how we will be reporting on the data, and how that often determines how we store the data. One thing that is consistent, from the responses below is that regardless of if it is stored on the constituent record or on an action record, it's going to be an attribute or custom field of some sort.

Will you need to report on the results of the survey? How well can you index them, and query on the results? In addition, how will you be entering the data? Import or manual data entry? All of these things are parts to consider.

Joanne Felci · October 2022

Great ideas and thoughts everyone!

This is helping me get my mind around it more and I'll have a few options to talk thru with my colleagues

Jenny Marquardt · October 20

@Faith Murray would you share how the "Event participant attribute will download directly through an event form."

We are starting to send out an event survey and would like to store them. Curious how you are doing this.

@Joanne Felci curious what you decided to do.

Suggestions on where to keep event survey data

Comments

Categories