This 'works' - although it is lacking on the UI front - @NNichols @RLewis @nisrael - does anyone have a group they want to push to Acoustic so I can test the performance of it
civicrm/a/#/omnimail/groupsync/?id=1

@RLewis
I have exported your group 1218 to Acoustic

https://engage4.silverpop.com/lists.do?action=listSummary&listId=42299852

I found that Acoustic rejected 4 email addresses because the localpart (before the '@') of their addresses was on a reject-list that we have configured at Acoustic - I've opened https://phabricator.wikimedia.org/T306582 for that - but in the meantime these 4 contacts have NOT been uploaded

support@ https://civicrm.wikimedia.org/civicrm/contact/view?reset=1&cid=22932907
marketing@ https://civicrm.wikimedia.org/civicrm/contact/view?reset=1&cid=54766195
service@ https://civicrm.wikimedia.org/civicrm/contact/view?reset=1&cid=4570757
admin@ https://civicrm.wikimedia.org/civicrm/contact/view?reset=1&cid=52234417

Notes about the job running ....

It seems to run at around 50 per minute but can be restarted in the browser - however if you go away & try again it creates a new queue & doesn't clean up the old one - I've added https://phabricator.wikimedia.org/T306855 for that

50 per minute won't scale so we will need to get it to run in the background - this will leverage the same approach (when finalised) to be used for imports

Note the url is https://civicrm.wikimedia.org/civicrm/a/#/omnimail/groupsync/?id=group_id to iniatiate a sync

@Eileenmcnaughton checking in on this and the sub-tasks; does it make sense for any remaining things here to be triaged/prioritized as part of our Acoustic 2025 push?

@AKanji-WMF yeah I think that would be good - users are not asking for it at the moment but it will give us a "here's one I put in the over earlier" moment

@Eileenmcnaughton You asked recently if we have a 'push groups up to Acoustic' phab, here it is.

Since nobody is currently asking for this, I'll move into "scoping" for a potential "acoustic 2026" spike.

@AKanji-WMF Ideally, I think we could get to this sooner as this plays into the audience builder question. I understand from @Eileenmcnaughton that this would not require a lot more work than what has already been done.

Great, thanks for the clarification - will move back into +1 for Sprint C or D consideration.

We now have https://gerrit.wikimedia.org/r/c/wikimedia/fundraising/crm/+/1247699, which pushes members of a group to the associated group in Acoustic.

@Eileenmcnaughton I think the next step here is to make this work more like a sync. Currently, it only adds and never removes, which is probably not what we want. It looks like the easiest solution would just be to use PurgeData to remove all the contacts from the contact list before we re-add them. Make sense to you?

@Lars Yeah that could work - to be honest there is probably a use case for both 'one off create' and 'keep in sync'