Issue with EMAIL Addresses in RE

Jessica Mavaro 2 · April 2013

Hi All,

We just purchased Bronto to handle out email marketing, and this system does not speak to RE at all. I have Importomatic (thank God!) and I plan on using this tool to assist in bringing information from Bronto into RE. The most important piece of information to get into RE is the unsubscribes/bounce-backs. Importomatic does duplicate checking based on email, which is the primary reason I purchased it. However, it does not check non-constituent contact emails. The way I understand it, organization records' Org1 tabs are not meant to house contact emails. For example, I have one company with 10 contacts, each having their own email. In order to properly personalize correspondence, I keep each email in the appropriate contact record and perhaps if there is a general email for the company, I'll put that in the Org1 tab. If I have an unsubscribe/contact loss for any of those contact emails, Importomatic will not catch this and I forsee this becoming an issue as I will need to import this data on a regular basis and want it to be as automated as possible. It can get dicey with IOM not catching these and spitting them out as exceptions.

One solution I've thought of is to create a full constituent record for all of the contacts I know we'll be corresponding with on a regular basis, that way IOM will catch their email. I don't want to clog the system up with so many unnecessary records, though.

I figure I'm not the first person with this issue so I'm hoping someone came up with a brilliant solution! [H]

Thanks all!

Melissa Graves 2 · April 2013

Jessica Mavaro:
Hi All,

We just purchased Bronto to handle out email marketing, and this system does not speak to RE at all. I have Importomatic (thank God!) and I plan on using this tool to assist in bringing information from Bronto into RE. The most important piece of information to get into RE is the unsubscribes/bounce-backs. Importomatic does duplicate checking based on email, which is the primary reason I purchased it. However, it does not check non-constituent contact emails. The way I understand it, organization records' Org1 tabs are not meant to house contact emails. For example, I have one company with 10 contacts, each having their own email. In order to properly personalize correspondence, I keep each email in the appropriate contact record and perhaps if there is a general email for the company, I'll put that in the Org1 tab. If I have an unsubscribe/contact loss for any of those contact emails, Importomatic will not catch this and I forsee this becoming an issue as I will need to import this data on a regular basis and want it to be as automated as possible. It can get dicey with IOM not catching these and spitting them out as exceptions.

One solution I've thought of is to create a full constituent record for all of the contacts I know we'll be corresponding with on a regular basis, that way IOM will catch their email. I don't want to clog the system up with so many unnecessary records, though.

I figure I'm not the first person with this issue so I'm hoping someone came up with a brilliant solution! [H]

Thanks all!

Our policy is that if they are to receive email from us - they get a full record. From org contacts to spouses. Not very brilliant but it is what it is.

Nicole S · April 2013

Melissa Graves:
Our policy is that if they are to receive email from us - they get a full record. From org contacts to spouses. Not very brilliant but it is what it is.

It isn't brilliant, but in many ways necessary. With BBNC, for example, you can only mail to full constituents unless you use a CSV file to import addresses of each email you sent out.

Jessica Mavaro 2 · May 2013

Nicole S.:
It isn't brilliant, but in many ways necessary. With BBNC, for example, you can only mail to full constituents unless you use a CSV file to import addresses of each email you sent out.

The knowledgebase doesn't really have much. We have Patron Edge integrated with RE so it dumps every ticket-buyer into RE. It's a good thing, and necessary, but is making our database grow quickly. I'm trying to avoid having full records unnecessarily as much as possible to keep our server clean, but I may have to create one record per email address after all. Thanks for the input!

Jessica Mavaro 2 · May 2013

Jessica Mavaro:
The knowledgebase doesn't really have much. We have Patron Edge integrated with RE so it dumps every ticket-buyer into RE. It's a good thing, and necessary, but is making our database grow quickly. I'm trying to avoid having full records unnecessarily as much as possible to keep our server clean, but I may have to create one record per email address after all. Thanks for the input!

Also, just curious - do you manage those dupes with solicit codes for snail-mailings?

Melissa Graves 2 · May 2013

Jessica Mavaro:
Also, just curious - do you manage those dupes with solicit codes for snail-mailings?

Jessica - what dupes are you referring to?

Issue with EMAIL Addresses in RE

Comments

Categories