Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Check Mailchimp interest groups — not just the audience — to know if a user is a newsletter subscriber #681

Open
aschweigert opened this issue Nov 23, 2021 · 1 comment

Comments

@aschweigert
Copy link
Contributor

Currently we check to see if a user exists in the organization's Mailchimp audience. This is overly broad because the audience encompasses every contact a given publisher has an email address for.

Instead, using interest group membership as a clearer signal should help eliminate false positives.

This would likely need to be configurable per publisher with an optional fallback to using the mailchimp audience if a publisher has not specified the interest group(s) they want to use.

Asana: https://app.asana.com/0/1200942827698993/1201001433518015
Details: https://docs.google.com/document/d/1s83l3e_kwYnMziNjN4Fhju3lwlrKEMbX6eUuPpZrb7U/edit#heading=h.ku48aywjozy7

@aschweigert
Copy link
Contributor Author

aschweigert commented Aug 10, 2022

Another example use-case from Cityside: they have a single MC account that has multiple audiences for Berkeleyside, Oaklandside and Cityside. They need the ability to target campaigns per audience/interest group in order to make this work across the different sites in the network.

We have one account for Cityside, and then have multiple audiences within our account, including ones for Berkeleyside, Oaklandside, and Cityside.
Then we have groups within each audience for the different newsletter products we send out. For Berkeleyside we have four different newsletters that subscribers can choose from: Daily, Saturday, Nosh (food), and Alerts. For Oaklandside: Daily, Saturday.
But we also encourage people who read Oaklandside to subscribe to Nosh, which is a Berkeley product. But if there isn’t a way to distinguish between Oakland and Berkeley audiences, we can encourage target Oakland readers who aren’t subscribed to Nosh.
We would also like to target readers of one publication to subscribe to newsletters on the other, but that’s not possible either.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant