Unfortunately that was the answer to this question a year ago. Your API needs to be more agile for such a simplistic task. Its not like someone is asking you to create a brand new functionality. Your GUI allows things to be named "Phone" "street" "CustomerNumber" but the API forces you to use absurd generic naming conventions.
That means the end user has to have a cheat sheet to convert CustomFieldNN to "Street" address when using the custom fields in the body of their email.
The fact that this functionality was promised a year ago, and is being promised again, translates into it is not a priority for Constant Contact API developers and hence we'll be having this discussion in a year. Or I'll be using a different product. One of the two.
Certainly understand your frustration here. I will make sure to pass the feedback on internally.
Pretty crazy this bug was reported two years ago and still there isn't a way to create custom fields on the fly.
Is there a way to add custom fields yet?
Hi Justin - unfortunately this is not a bug. Today we still do not have the ability to create user defined custom fields in the API and we don't have any expectations on when that functionality will be available through the API. Appreciate the feedback and will continue to work towards making this happen.