Hello,

I've started to use MailChimp API. I congirured it in ACP 5 but I can't see the option to use Mailchimp for transactional emails as I see on SendGrid integration.

Mailchimp also has transactional emails. Can't Mailchimp be used to send Bulk emails? Is there an option for that? Is it something that will be added?

I can only see SMTP and the cloud.

Thanks

Edited January 26Jan 26 by michimachi

The MailChimp integration is not for sending email but only for moving data of your subscribed users to your MailChimp list.

14 hours ago, Jim M said:

The MailChimp integration is not for sending email but only for moving data of your subscribed users to your MailChimp list.

Thanks a lot.

One question. I've configured and enabled Mailchimp integration by adding the API. So now, every new member is added to Mailchimp in the audience list I added? Do I need to do anything else? I can't find any documentation on how this integration works. Thanks

7 hours ago, michimachi said:

Thanks a lot.

One question. I've configured and enabled Mailchimp integration by adding the API. So now, every new member is added to Mailchimp in the audience list I added? Do I need to do anything else? I can't find any documentation on how this integration works. Thanks

Correct. Once you configure it, every new member will be added to your MailChimp list specified.

1 hour ago, Jim M said:

Correct. Once you configure it, every new member will be added to your MailChimp list specified.

Thanks a lot. And that's where exactly there is one thing missing. The email is added "naked" without a tag (mailchimp feature) to manage contacts in the list. So the new members are just lost in MailChimp's without a tag like: source:community or source:acp to distinguish them from other sources.

It would be sooooo nice to have that function in Mailchimp integration, otherwise new members are mixed with leads form many other sources, etc.

Please add a Feature topic for any new features :) .

1 minute ago, Jim M said:

Please add a Feature topic for any new features :) .

When one of the team members say "Add it as a feature", I have an internal "laugh" saying "what for?". They are never added, not even serious bugs that have been reported, taking months to be fixed. It's sad, to be honest. Because when you suggest and you see that many others suggest and no features are added, you just stop suggesting and then the community you created becomes a "megaphone community" where only those "at the top" dictate what is going to be done.

Sorry, I just had to say it. It's sad because that prevents me and probably many others (I read many commnets) from suggesting. Because you say to yourself, what for? They won't do it.

While I certainly understand your frustrations and thank you for submitting any feature request, a very large portion of our software comes from feature suggestions or conversations in that forum but it is important to understand it is not feasible to implement all of them. We certainly wish we could but in order to keep software useable for a large, varying client base, our strategy focuses more on what is most valuable to all our clients and maintainable by our limited resources.

I am not part of our product team but just as an example, the tags you mentioned here may be extremely valuable to you but the large portion of our client base may not use that feature in MailChimp so it is very much a balancing act of understanding and prioritizing what brings value to everyone. It would be a complete waste of resources to develop for one client (no matter how much we respect you) so we have to prioritize. Items which fall outside of this but extremely valuable for you are great candidates for custom development (Note: this example could be far from the truth in relation to the actual feature but I am just using this as an example to our process.)

Keep in mind that simply because you suggest a feature, does not mean it will be implemented :

• entirely

• exactly as requested

• immediately

but that does not mean it is ignored, forgotten, or valued. We often come back to feature requests at different points when new features come around to see how it may be shaped or used differently.

The number one way to completely ensure that your feature is not built into the software is by not bringing it up in the Feedback forum.

29 minutes ago, Jim M said:

I am not part of our product team but just as an example, the tags you mentioned here may be extremely valuable to you but the large portion of our client base may not use that feature in MailChimp so it is very much a balancing act of understanding and prioritizing what brings value to everyone. It would be a complete waste of resources to develop for one client

Hi,

Thank you for the honest and detailed response — I appreciate you taking the time to explain how feature requests are evaluated internally.

That said, I’d like to respectfully challenge one part of the reasoning, because it’s something I see repeatedly as a client.

You mention that certain features may be valuable to individual clients but not necessarily to a large portion of the user base. My genuine question is: how is that determined if clients are never actively asked or polled?

In all the years I’ve been using Invision Community, I’ve never seen polls or structured surveys asking customers what integrations they rely on, what features they actively use, or what would bring them the most value. From the outside, it often feels like those decisions are made internally rather than collaboratively — which naturally creates the perception that clients have very limited influence over the product’s direction, beyond posting feedback and hoping it gains traction.

This applies not only to feature requests but also to bugs. For example, I reported a serious issue months ago related to course bundles where prices become mixed and unreliable. That problem directly affects monetization and usability, yet I continue to see releases focused on fixes or additions that feel far less critical in comparison. From a client perspective, that prioritization is difficult to understand.

I fully appreciate that not every request can be implemented, nor immediately, nor exactly as suggested. My intention here isn’t to demand a specific outcome, but to highlight a recurring gap between client needs and perceived product priorities — and how the lack of structured client input makes that gap wider.

I value Invision Community and wouldn’t invest time providing feedback if I didn’t care about the platform’s future. I just believe there’s room for more transparency and client involvement in understanding what “brings value to everyone.”

Thank you again for the conversation.

Edited January 27Jan 27 by michimachi

11 minutes ago, michimachi said:

My genuine question is: how is that determined if clients are never actively asked or polled?

Good question. We find evaluating conversations and trends are a much more honest sense of the value/popularity of a subject. We also do factor in our other forms of communication with clients to evaluate those trends. We also do weigh-in when multiple clients write the same feedback or reply in the topic, etc... so there is a way of polling/popularity there. We don't always contribute things 1:1 in these scenarios.

Certainly appreciate your insights. I'll pass this over to our product team as well.

22 minutes ago, michimachi said:

This applies not only to feature requests but also to bugs. For example, I reported a serious issue months ago related to course bundles where prices become mixed and unreliable. That problem directly affects monetization and usability, yet I continue to see releases focused on fixes or additions that feel far less critical in comparison. From a client perspective, that prioritization is difficult to understand.

Certainly would be interested in the URL to that topic/ticket as I am not immediately familiar with the issue, I cannot speak on it. However, our triaging procedure is to try to address critical, widespread/high impact issues first and move down from there. It may also be the issue you're running into is hard to resolve or the fix is largely impactful so needs to wait for a different release to be issued. Getting the URL, I can take a look at where the issue is in our process.