• Replies 10 replies
  • Subscribers 413 subscribers
  • Views 300 views
  • Users 0 members are here
Related

Constituencies vs Attributes

Grant Offermann
$organization

Hi All,

We are getting ready to do some name captures (with contact information) and are trying to decide if it's better to apply a Constituency to them or an Attribute.  Any advice?  We most likely will be using list manager to pull the info but want to make sure we know all the pros/cons before we decide.  Here is what we have:

 

Constituencies:

 

Pros:

  • Can have it show up on constituent header
  • They have start and end dates
  • Can be controlled with different security objects (Add, change, view)
  • Just create it in TR_Constituency

 

Con

  • Lack of detail, no dropdown.  Their either have it or they don’t.



Attributes:

 

Pros:

  • Can add a subset to the attribute.  Eg: Dropdown to choose from.
  • Can be used with control group

 

Cons

  • A little more work creating them since you have to use multiple tables
  • No end date
Parents
  • $organization

    What kind of info are you trying to capture here?

    We've found Constitiuencies to be useful for labelling cohorts, audience segments, membership/donor status, etc. 

    We don't use Attributes much right now, but have used them in the past to tag program interest and subset info on their constituency (where that dropdown comes in handy).

    A lot of it comes down to what information you want to collect and what you want to do with it after.

Reply
  • $organization

    What kind of info are you trying to capture here?

    We've found Constitiuencies to be useful for labelling cohorts, audience segments, membership/donor status, etc. 

    We don't use Attributes much right now, but have used them in the past to tag program interest and subset info on their constituency (where that dropdown comes in handy).

    A lot of it comes down to what information you want to collect and what you want to do with it after.

Children
No Data