I really appreciate that CM tries to match my CSV columns with their corresponding custom fields when importing subscribers, but I've always wondered why often it's so... bad.
Sorry to be harsh, it's just funny how inconsistent the automatic matching can be. Thankfully it's not mismatching columns, but all of my column headers are named exactly the same as their corresponding custom field, yet "Skip this column" is the default in 5 out of 6 columns I just imported.
I don't mind double-checking on this step, but my concern is for clients that might overlook it in a rush, or worse, accidentally choose the wrong match.
Any way to improve this? Thanks!
Hey there enfueggo, thank you so much for your feedback here. We're very keen to improve this step, so just to be certain, would you prefer that if a custom field name matches a column name, the data is automatically added to the custom field? Or do you have another process in mind?
Let us know what your preference is here and we'll certainly take note internally. :)
Hey enfueggo, I just wanted to check with you if this only seems to happen with columns where the first 3 lines are blank?
If so, it is indeed a bug that our developers are aware of, and that should be fixed in an upcoming release. It's still a while off unfortunately, so in the meantime, it's best to pay an extra bit of attention to the custom field matching.
Hi Ros and Stig, apologies for the delay, I forgot to hit the 'subscribe via email' button!
Stig is right, I never noticed that before. Sadly, though, it occurs if the first entry (after the header) is blank. Glad to know it's a known bug and look forward to having it fixed. Here are screenshots of my CSV and import page to help illustrate what's happening:
Thanks enfueggo, we really appreciate your help with this. I'll add your screenshot to our notes, as they'll certainly help our devs out. As always, you've been very helpful!