Thanks for posting the details of this situation. First, I do think the right move was to ask people to join the new list. This not only will provide you with an interested and engaged list but will also follow Constant Contacts guidelines for what contacts you can email.
How are you collecting and storing the pass information? Is this in a custom field?
My recommendation would be to use a new custom field every year. You cannot upload a blank version to overwrite the contents of a field so you would need to manually remove the information to have it deleted. If you use a new field very year and name them to match you should just be able to delete the entire custom field from the year before and start fresh with the new one.
You can add as many custom fields as you want/need. To edit, add or remove fields you can just click My Account> My Settings> Manage my custom fields.
Hope this helps,
We're having the same issue. The thing is we've completely deleted the previous lists and reduced our contacts to zero. Now when uploading a new list, if a custom field has a blank entry it's populating with old information even though we've totally deleted all lists and contacts.
Is this information still stored internally with CC? This is not a behavior we wanted or anticipated.
The information for your contacts is still held for your account, even if your contacts are deleted. This is one of the ways we ensure that an unsubscribed contact remains unsubscribed, even if they are deleted and then re-added.
I would recommend deleting the custom field, deleting your contacts and then re-uploading the list, creating a new custom field. This process will completely remove the custom field throughout all of your contacts, and allow you to re-add the custom field back with only new values that you upload.
3 years later and this bug is still hurting users, making our communications appear unprofessional to our audience.
When a user deletes a contact record, ConstantContact tells them "The selected contact will be permanently removed from your account", and "THIS ACTION CAN'T BE UNDONE". Apparently those statements aren't true; ConstantContact resurrects deleted contact data and covertly pollutes newly imported data with it.
I see the value in ConstantContact permanently retaining the unsubscribed status of an email address, but that is inarguably the only data point that should be retained when a contact is deleted. Retaining other field values from deleted contacts is a bug, and one that we discover only when our audience informs us of mistakes in our messaging.
Thank you for reaching out to the Community! You are correct, if a contact is not marked as unsubscribed they will be recognized if re-imported. I apologize for any inconvenience caused from old information in fields being retained in this re-import. At this time, the ability to import a file with a blank column to overwrite or remove fields that were imported by accident is not a feature we currently provide. This is however a feature request I have submitted in your account in the appropriate teams. As a workaround we suggest manually deleting those fields under your contact's details. However if there is a lot of data in a field that is not feasible to delete one at a time, please let us know! We would be happy to help troubleshoot this further with you.
We need a feature to NULL old data from Custom Fields. If an upload list contains a blank cell under a named column, then that should empty the associated Custom Field.
Why store empty Custom Fields? Accuracy, data can be optional, and support of business model. Here’s our example…
SOLUTION, Constant Contact – Deleting and recreating custom field TEAMNAME
CONCLUSION: Adding and removing Custom Fields between emails is not feasible.
SOLUTION, proposed – Recognizing empty cells under a named column as NULL at upload
As of now, if I upload an empty cell under a named column, it refers to old stored (inaccurate) data. If I input NULL in the cell, it imports the word NULL, stores the word NULL and emails the word NULL.
We need to overwrite old data with empty data, when optional information is referenced. Will there be a way for your upload system to recognize empty cells under a named column as empty, and therefore store NULL (or empty) in their respective Custom Fields?
Thank you for reaching out to the Constant Contact Community. It's my pleasure to assist you today.
At this time, the feature you have described isn't currently offered. The previous workaround mentioned is the best option, although you may do this by removing the custom field from that contact only. I will certainly pass along your direct feedback. Thank you for choosing Constant Contact. Have a great day!
The Constant Contact User Community is hosting a sweepstakes. The more you participate, the more chances you have to win! Read on to learn more...Read More