How many custom fields should a newsletter use in Beehiiv for survey answers?

We once found a survey integration creating a brand-new Beehiiv custom field on every single submission. Roughly 80% to 90% of the fields on that brand were blank duplicates. It's an easy mess to make and an annoying one to clean up.

How many fields is right?

About 10 to 12 per brand.

"Cap total Beehiiv custom fields at 10 to 12 per brand, with the mapping fully automated so no end user has to click through manual configuration."

Should survey answers be tags or custom fields?

My working view is custom fields. Tag systems are built for grouping audiences, like "came in from the event ad." Zip codes, interests and open answers belong in custom fields, where you can search and segment on them.

Tags still have a job. Use them for the source a subscriber came from, and for routing people into sequences, like an "interested in buying a business" tag that triggers a matching email series.

How do you stop fields multiplying?

1. Reuse what's there. Almost all survey questions repeat across versions, and thousands of answers are already on file. Map new answers to the old fields.
2. Create new fields only for new questions. When I added pets and business owner, those got new fields. Nothing else did.
3. Automate the mapping. No operator should click through configuration screens.
4. Clean up. Delete test subscribers and junk fields. Duplicates usually show up with a trailing number on the name.

How did I find the bug?

I had an AI coding agent inspect Beehiiv live on my screen while I watched. It diagnosed the problem: the subscriber record and the custom fields were being written at the same time. We fixed that, verified the mapping, and cleaned out the junk.

One more detail

If you run more than one brand, show a masked publication ID in your integration settings, like stars plus the last three digits. Operators can confirm they're connected to the right newsletter without exposing the full ID.