Dynamic constituent list - Only pulling one email address

Cammi Derr · November 2016

We have discovered that if we use a dynamic query for a list instead of importing the list, only the email address at the top of the email grid is used, unless there is one that is marked primary, which we do not have many marked that way. We want to send to all active email addresses on a record but have the capability to use a dynamic query so that if users response "Requests no email", we can use the integration feature in RE to update the record and also the ability to track the mailings to the constituent via the Netcommunity tab on their RE record. An imported list does not update the constituents in RE.

Is there anyone that knows about this issue?

Rachel Slager 2 · December 2016

I agree that query (not import) is the way to go to track the communications, opt-outs and bounced emails. My guess is that if you got this to work then on the NetC tab in RE each message would appear repeated, once for each email address.

NetC allows you to attach multiple queries to a single email message. If you're email addresses each have a different type, you could build a query for each type, then attach all of those queries to the NetC message. Normally, even if attaching multiple queries where the same address appears, NetC will ensure that the recipient won't receive duplicate emails. I haven't tested this solution, but the question that remains to answer if NetC is merely ensuring a specific address won't get duplicate email, or if it is ensuring a specific constituent won't receive duplicate messages - if it's the second one, then you may have to send the message multiple times using multiple queries.

Cammi Derr · December 2016

Rachel Slager:

I agree that query (not import) is the way to go to track the communications, opt-outs and bounced emails. My guess is that if you got this to work then on the NetC tab in RE each message would appear repeated, once for each email address.

NetC allows you to attach multiple queries to a single email message. If you're email addresses each have a different type, you could build a query for each type, then attach all of those queries to the NetC message. Normally, even if attaching multiple queries where the same address appears, NetC will ensure that the recipient won't receive duplicate emails. I haven't tested this solution, but the question that remains to answer if NetC is merely ensuring a specific address won't get duplicate email, or if it is ensuring a specific constituent won't receive duplicate messages - if it's the second one, then you may have to send the message multiple times using multiple queries.

Just got off a call with programmers via our project manager and one of them stated that using mulitple email addresses of the same type could possible affect their Spam ratings. This is the reason that a dynamic will only allow 1 email I supposed. We did find out that they are going to release a fix that will ensure that BBNC dynamic lists do not use email addresses marked with the DNC in the grid. We are going to continue to use the static lists until we implement profile updates from the constituents where they will have the capability to tell us what email address is the primary and not create additional email types. I have found that one email type prevents duplicates from being added to a record and so we only utilize 3 types, "Email", "Business Email", and "Bad Email".

Dynamic constituent list - Only pulling one email address

Comments

Categories