Vega Attributes are “metadata” about your contacts. That is, they combine the functions of segment codes, user-defined fields and rules-based data to give you a powerful tool to manage your supporters.
You can use Vega Attributes to
- Record Contact Preferences or Activities
- Volunteer or Contact Skills, Interests, Availability, Health and Safety and much more
- Record Journeys and Opportunity Pipelines
- Record Memberships
- Record Survey Responses
- Record Campaign Type or Event Preferences
Think of anything you want to count; target or group and you probably have an attribute. Obviously target groups like “Current Donors” can be discovered from financial data. Respondents to campaigns can be discovered through the engage module. So, you have lots of places to discover data and target contacts. However, attributes can be flexible and easy ways to group or manage your contacts. Attributes also can trigger workflows. (More on this later)
All attributes can have a START DATE, END DATE, VALUE, STATUS (Open or Closed) and an Auto-Renew Flag. These will be explained later.
If you want to be able to find a group of contacts easily then, do you have an Attribute that defines that group? For instance, I want to find all my Volunteers. If all contacts who are volunteers have that attribute, then I find them reliably by a one-click query.
If I want to find all Volunteers with a skill and available on Wednesdays, the likelihood is I will use two attributes in a simple query to get a reliable answer. I will search for the skill and I will filter that by an availability attribute for Wednesday. If any of these attributes are missing, my query becomes harder or I must search through a bigger list to find the right people.
I want to find all contacts who are interested in an issue. Do I have that issue coded as an Attribute and have I either added that attribute to the Contact or had Vega add that attribute for me as a result of campaign activity? If so, my query again is simple. (the alternative is to query everyone who responded to any campaign that featured the issue.)
Again, what is it I want to count in my database, target in a communication from my database or create communications based on some trigger such as a new registration through the website.
If you know the answer to those simple questions you have the basis for an attribute structure.