Importing new constituents in a group- can we make it so the group is not "opted in" to all emails?

I believe that anyone "opted in" to email is opted in to ALL emails if their gorup is included or not suppressed. I don't think you can do what you want without one of these changes:

-(clunky way) change your blasts to go to a "general email" or "blasts" group, and then add EVERYONE except the blocked gorups to that group;

-(clean way) suppress the "special interest" groups from blasts, as you mentioned;

-(squeaky clean way) make a query called something like "general email suppression groups query" and include whatever special interest groups you want suppressed into that query. use that to populate a group called "general email suppression." then you just have to suppress that ONE group from future emails and it will include everyone you want suppressed, as long as you have it rebuilt at runtime. The query would look something like:

-constituent is a member of [interest group 1]

-OR constituent is a member of [interest group 2]

...

-OR constituent is a member of [interest group n]

 

And as you identify new groups you want suppressed, you just add them to the query without ever having to change any email schedules.

Sarah Gasca:

Hi Bo. Thanks for your help. 



I tried the "clean" way on our last eblast. The problem is that there are duplicates in this list. I.e. John is on the special groups list and general email opt in list. When I supress the special groups list, he does receive our Newsletter email because he is on that list.

 

Hope that makes sense. I wonder if the query method would lead to the same problem? 

In Luminate Online, any email address that is in a group that is suppressed from receiving an email will not receive it, regardless of what other groups he's in. In other words, suppression group membership trumps inclusion group membership, so to speak. However, if a constituent has two different email addresses in two different groups, she will receive it at the address that is not suppressed.

 

Maybe things are different in Go!?

Kristin Johnson:

One additional element to consider depends on if you have identical-email duplicates. Convio's email sending system narrows down to the Constituent ID (not by unique email!). It is possible for their to be multiple Constituent Records, each with a unique Constituent ID, but that have identical emails. This is often partially avoided if you have some database settings that block identical-email records from being newly created; however, this is not perfect because of some big flaws in Convio's Events modules and some other sneaky routes. Because of those flaws, identical-email constituent records can and will still be created in your database, despite those settings (albeit, usually only in very small numbers).

 

Unless database has a large number of these identical-email multiple records going on though, this would be a small problem. As Bo noted, suppression supercedes the inclusion, so the constituent record in the suppresion group would be removed, whether or not they are in some of the inclusion groups.

Ah, yes! Always wise to do regular duplicate checking based on email address match. We get a few every now and again.

Kent Gilliam:

Sarah,

 

One thing I would ask is, if they gave you their email why not email them? This is a perfect opportunity to create a welcome series specific to these types of records. You can "welcome" them and tell them that through their event participation that their email address was captured and your organization would like to be able to communicate to them in the future. Give them examples of the content they can expect to receive and the frequency. Chances are more of them will want to stay opted in than be suppressed.

 

And to answer your question, yes, every record added to Cons360 is added to the "Any Registered User" group. Like Bo and Kristin said, you should really look at using specific groups to target and not just send everything to everyone using the "Any Registered User" group. 

 

Thanks Bo and Kristin for your input as well!!!

One more thought on this... :-)

 

One thing that you can do to address this problem is create yet another query.  I realize that it might start to feel rather winding, but per the above, you do run into the problem that if you have folks in the suppression group, that SHOULD be able to receive certain communications, the system is going to always honor the fact that they are in a group on the do not mail list, and so they are suppressed. 

 

If you create a new query that has two group clauses -- you could do the following.  Use the query to find all contacts that:

 

Are a member of the suppression group

AND are NOT a member of the target list

 

The results of that query will give you a new set of contacts that you can create a new group from.  That group will contain all contacts that should be suppressed because it's not going to include any contacts that are a member of BOTH groups.  By creating this new third group, you should be able to solve the problem of having contacts that are overlapping.

 

Hope this helps and doesn't muddy the waters -- post back if I can provide more detail to be helpful,

Adam

Hi Dustin,


Is your general newsletter interest group a default interest? You can see this by going to that interest and looking at the interest information. There is a row with the title: Default Interest.


If this is checked, constituents are automatically added to the interest.


You can always remove constituents from an interest using a segmentation import.


Here is more info on that:

https://www.blackbaud.com/files/support/helpfiles/luminate-online/help/luminateonline.html#../Subsystems/DataManagement/Content/Tasks/Admin_ImportExport_InterestSegmentUpload_RunningSegUpload_ToImport.html?Highlight=segmentation report


Let us know if that helps.


Thanks,


Phil