Data in the website (like your contacts) is not in real-time, and sometimes it is inconsistent, when if you're adding contacts via the API. We have to keep refreshing and refreshing to get accurate data. Now we know it's not easy to make the software real-time, but there's a huge gap in the contact count between refresh (reloading the page for instance). And it doesn't always show the latest data after you refresh too- sometimes the count goes lower, higher, and then back lower. We realize this might be a cache issue, but we tried clearing the cache and reloading the page. It takes a long time for the accurate data to fully settle.
This also happens when you make a campaign and create a custom new group/segment as the recipients. Even when you click 'update recipient count', it gives inaccurate data. This has made us lose about 30 mins cross-checking ourselves to not make any mistakes when we're sending a campaign with the website.
The automation feature wasn't what we we're expecting when we first tried it. The idea of the automation feature good, and we used it a few times, but we stopped because once the automation flow reached the last queue, it just stopped. We had to manually keep adding more emails to the bottom of the automation. We thought this feature would eliminate any manual work for us. It just wasn't what we were expecting when we tried it. We hoped there'd be an option to loop the automation.
The developer reference website doesn't fully cover all documentations and fields/properties when explaining how to make a request to the mailchimp API. Some properties were pointed out, but in reality, those properties also have sub-properties in them. And not all of them are present in the documentation.
- For example, in the Add Campaign docs, you have body parameters to provide in the request, like:type, settings, recipients, etc. Each of these params might have additional properties in them, and the data type required for each one. For the recipients, it's an object containing two properties: list_id and segment_opts. List ID is straight forward, but the is segment_opts also an object that has properties, every one of them was explained to the fullest, besides "conditions" property, it just says the data type, which is an array- but an array of what? strings? objects? integers? it was just left shallow, we had to research and contact support again and again to finally get what we wanted. This was the only one we had to deal with. We can only imagine there's more our there too. This was especially crucial because we don't want to send the wrong emails to the wrong customers. Review collected by and hosted on G2.com.