Missing column mapping when using CSV by FTP import to Mailchimp

  • 179Views
  • Last Post 09 July 2018
  • Topic Is Solved
0
votes
Steven posted this 31 May 2017

I have a source CSV file via FTP that I would like to import into my Mailchimp List data. My Mailchimp list has additional fields that match the the columns in my CSV file.

When setting up my package the columns show up in the Source definition sceen:Source Definition

I am using the Upsert operation on the Target definition screen.Traget Definition

In the Mapping Definition screen however some columns are missing in the Source and Target that need to be mapped.Mapping Definition

What else do I need to do to get the missing columns mapped between the CSV source file and theTarget and subsequently run a successful import into my Mailchimp list?

 

Order By: Standard | Newest | Votes
0
votes
Mariia Zaharova posted this 01 June 2017

Please try performing the following steps:

- open your MailChimp connection and set "Merge Fields Behavior" to "Join All Merge Fields";

- save the changes; 

- open your package and edit the Task; if fields are still not available, try clicking Refresh button.

Note: if different lists have merge tags with the same name but different type, default value, required setting, etc., these merge tags are ignored regardless of the Merge Fields Behavior parameter; merge tags that have the same name for different lists must be the same in order to be available in Skyvia.

Refer to: https://skyvia.com/resources/docs/index.html?connecting_to_mailchimp.htm

0
votes
Steven posted this 01 June 2017

Great that has solved it thanks.

I have since run my package and have been able to import the CSV data file into my Mailchimp list successfully on first run. In this case the required ID was mapped to the blank ID column in the CSV and it appears that Mailchimp has then assigned an ID number.

I am now trying to run several other import packages to the same Mailchimp list but with CSV data files containing additional updated merge field data and also the same blank ID column.

I am having difficulty both mapping the required Mailchimp ID which is unknown in the CSV files and also getting new and existing list member data upserted successfully  When the new packages are run they seem to get stuck when importing rows and am unable to cancel the imports.

What are the correct steps to get multiple import packages to update/upserting a Mailchimp list?

1
votes
Mariia Zaharova posted this 02 June 2017

For you scenario, you can use Import package with the UPSERT operation. Here is the information how UPSERT works: if ID is set, package performs UPDATE even if ID is incorrect. If there is a NULL value instead of the ID, package performs INSERT and ID is generated automatically. Thus: the ID field must be mapped, but it could contain NULL value. I.e. if there is no such column in the CSV file or if it is a lookup that returns NULL, the INSERT operation will be performed. 

You can try the following solution:

1) Set the Lookup mapping for Id field (MailChimp): 

Lookup Object: ListMembers

Resulted Column: Id

Lookup Key Column: ListId

Column: ListId (or set it as Constant value)

Lookup Key Column: Email

Column: Email

2) Open Options and select "Set null when no match found"

3) Map ListId to Constant (set the necessary ListId value) and set mapping for the Email field

4) Set mapping for other fields, if necessary, etc.

Please also refer to: https://skyvia.com/resources/docs/index.html?performing_upsert_operation.htm

To get ListId you can use:

Please tell us if this information helps.

  • Supported by
  • Steven
0
votes
Steven posted this 21 June 2018

Hi Marila,

I've had an integration package set up to import a CSV file to Mailchimp as per the guidlines you provided. It had been running fine for just over a year but now has the following error in the run history: 

'Target object 'ListMembers' does not have column 'First Name'.'

I checked the Package Content and Import Tasks which now shows an invalid task. When i edit the task I am unable to progress to the Mapping Definitions tab and check the orginal source and target settings I had configured. I tried both Mailchmp Ver2 and Ver3 API versions.

Is this error potentially being caused by an update with Mailchimp?

 

 

0
votes
Mariia Zaharova posted this 22 June 2018

Hi Steven!

Probably, the issue is related to the fact mentioned above:  if different lists have merge tags with the same name but different type, default value, required setting, etc., these merge tags are ignored regardless of the Merge Fields Behavior parameter; merge tags that have the same name for different lists must be the same in order to be available in Skyvia.

Please check settings for 'First Name' field for all lists which have this field. Make sure the settings are the same, e.g. tags, required option, type, etc. After this, open your MailChimp connection "David Clulow - API V2 All Merge Fields" in Skyvia and click the 'clear' link for Metadata Cache parameter.

 

Notify me about the results.

0
votes
Steven posted this 04 July 2018

Hi Marila,

The task is now validating and running as normal. Please note the previous merge tags all remained unchanged after checking each list.  Each list however was updated to have GDPR fields enabled in its campaign defaults and the GDPR fields were all made identical. This seems to have helped.

0
votes
Mariia Zaharova posted this 09 July 2018

Thank you for notifying me! 

Feel free to contact us!

 

Best regards,

Mariia

Close