Mailchimp backup not containing group & static segment memberships lists

  • 75Views
  • Last Post 24 April 2018
  • Topic Is Solved
0
votes
Nico Veenman posted this 09 April 2018

Dear all, 

Short question on the Mailchimp backups. I'm backing up Mailchimp, which works fine for most part.

But, we also got important list of memberships per email address in groups, plus we're using static segments. But, in the backup I don't see these memberships. So from the backup there is no way to know which email address is member for which group or which static segment.

Either i'm missing a detail, or it's not in there. In either cases I hope you guys have a good solution to do include these group & static segment memberships.

Looking forward,

Nico

Order By: Standard | Newest | Votes
0
votes
Mariia Zaharova posted this 10 April 2018

It seems, you are using MailChimp API 2.0. Skyvia supports connecting via both MailChimp API 2.0 and 3.0. Please note that some tables and fields, like Automations, ListMemberNotes, ListMemberGoals, and others are available only via MailChimp API 3.0, and some - only via MailChimp API 2.0. By default, Skyvia uses MailChimp API 2.0. You can change this at any time in the connection editor.

 

The information you are looking for can be found in these tables:

 

These tables are available only for MailChimp API 3.0. Please check this and tell us if this what you are looking for.

0
votes
Nico Veenman posted this 16 April 2018

This works, thanks!

0
votes
Nico Veenman posted this 16 April 2018

One question though.... how can the amount of records differ so much throughout the days?

 

0
votes
Mariia Zaharova posted this 17 April 2018

This difference in the number of records is due to the fact that there are errors for some tables in different backup copies. Errors occur at the MailChimp side when numerous requests are sent to their server. We recommend you to try splitting your backup package into several ones and run them not at the same time.

 

0
votes
Nico Veenman posted this 23 April 2018

Hi Mariia,

Is there no other way to cover that? So this error below is also because of that?

 

0
votes
Mariia Zaharova posted this 24 April 2018

Yes, the reason is the same. We still recommend you to try splitting your backup package into several ones and run them not at the same time.

Close