Skip to main content

Community

Please sign in to leave a comment.

Comments

4 comments

  • Official comment

    Hi George, Drew from the Product Team here!

    Thanks for submitting this request. I'm curious about how this data is used. Based on the endpoints you have shared, interests are tied to lists. Would providing interests associated with lists be sufficient here? Or are you looking for interests associated with a member?

     

    Hi Drew,

    We are interested in what the members are subscribed to, what each member's GDPR marketing preferences are.

    We also requested this feature a few months ago in a discussion with David through the support portal. I'll add info on our use case here if it can help move this feature request forward.

    We currently have 6 different newsletters, with all contacts stored in a single list, and users can opt in or out of these 6 through our website form. These newsletter subscriptions are saved as interests in Mailchimp.

    There are a few reasons why we use interests instead of tags.

    • We once used Mailchimp's embedded signup form and interests are the only way to allow a user to select multiple subscribing options. Tags can't be added from this form.
    • In our email templates, we use conditional blocks to show/hide blocks depending on the user's interests. For example, show a "subscribe to our Politics newsletter" only to those not already subscribed. Tags can't be used in conditional blocks.

    In our data warehouse, we need to know what newsletters members are subscribed to.

    Hi Sebastien Groleau, we're currently in progress on the request and it should be done around the end of April.