Mailchimp Ecommerce Data Issues

[ashlinixon]

I am using the Mailchimp module to send promotional and transactional emails. After installing the module, I am able to see the customer data flowing into Mailchimp, but none of the e-commerce data appears in Mailchimp. This means I am not able to dynamically recommend products or send abandoned cart emails through Mailchimp to subscribed customers.

I can't seem to figure out where the error lies. The only thing that might be a clue is that after running the Mailchimp Full Synchronization task in Miva, I am getting a warning that reads "Error synchronizing batch for all customers: MER-FUF-MLCP. We encountered an unspecified JSON error."

Has anyone ran into this and found a resolution? Thank you!

[dcarver]

You should open a support ticket and have them turn on MvCALL logging so they can see the data being sent to / received from MailChimp. The message "We encountered an unspecified JSON error." is a response coming from MailChimp, so we'd need to see what is being sent to try and figure out what is going on. You could also contact MailChimp's support and see if they see anything on their end related to your account.

[ashlinixon]

After chatting with Mailchimp support, they feel a piece of unclosed code is what is causing the issue. See this note from Mailchimp below:

So from the call that is being made by Miva to Mailchimp, I'm seeing that the end of the API call is ending with:
"body": "\u007B\n"id":\t"f092271578996b1da8fa37899666ee2dc 72cd5fa",\n"email_address":\t"[email protected]",\n"opt_in_status":\tfalse,\n"company":\t"",\n"fi rst_name":\t"Daniel",\n"last_name":\t"Lev

The body of the call should be closing with this: }

That being said, you will need to reach out to Miva about the syntax of the JSON that is being passed over, because how the calls are written is resulting in an error.

I have a ticket in, but thought I'd post here too in case it helps others.

[dcarver]

You should open a support ticket with us so they can turn on call logging and we can see exactly what is being sent. Can you reproduce it every time? If so, we should be able to track it down pretty quickly.