Question Status

Suggested Answer
MDS asked a question on 26 Mar 2015 6:15 AM

We have a requirement for some way of "tagging" an account with attributes that we can later report on.

Eg - We have an account. We need to designate whether this account is

  • Interested in mailshots
  • Interested in events in a certain area (numerous)
  • Interested in a whole host of different marketing activities
  • etc etc

We previously, in CRM 4, used a section full of such attributes and ticked them as appropriate. Is there a better way of doing this in 2015? There are probably 15 - 20 of these attributes we need to consider...

Reply
Suggested Answer
mscrmba responded on 26 Mar 2015 6:29 AM

The downside of this approach is that each one needs to be set up as a field.

The upside is that it makes it super simple to generate a dynamic marketing list / OOTB view.  Note: If you do go there I'd recommend using a 'Subscribed date' rather than a checkbox - that way you capture more information (e.g. you can see how long they've each been interested and tailor your mailouts accordingly - e.g. might be good to have different wording for people you're reminding about something rather than people you're introducing an event to for the first time).

Alternatives to this approach include:

1. A custom 'subscriptions' entity with a Lookup of subscription options (which can be added to without any further code/configuration changes).    (This would be created with a N:1 relationship to Accounts and could be displayed as a sub-grid on your Account form view. )

2. Using static mailing lists (one for each option).  An retrieving the hidden ListMember details with code if you need it for anything else.

Reply
Suggested Answer
mscrmba responded on 26 Mar 2015 6:29 AM

The downside of this approach is that each one needs to be set up as a field.

The upside is that it makes it super simple to generate a dynamic marketing list / OOTB view.  Note: If you do go there I'd recommend using a 'Subscribed date' rather than a checkbox - that way you capture more information (e.g. you can see how long they've each been interested and tailor your mailouts accordingly - e.g. might be good to have different wording for people you're reminding about something rather than people you're introducing an event to for the first time).

Alternatives to this approach include:

1. A custom 'subscriptions' entity with a Lookup of subscription options (which can be added to without any further code/configuration changes).    (This would be created with a N:1 relationship to Accounts and could be displayed as a sub-grid on your Account form view. )

2. Using static mailing lists (one for each option).  An retrieving the hidden ListMember details with code if you need it for anything else.

Reply