We have established that it is possible to tag a mailing in Acoustic & there is a desire for these tags to be brought into CiviCRM - probably as a custom field extending the Mailing entity, although a tag is also an option.
Description
Details
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T394089 Acoustic fields wishlist - discussion | |||
| Open | None | T400112 Bring Acoustic mailing tags into CiviCRM | |||
| Open | None | T400114 Acoustic stats don't seem to be updating OK |
Event Timeline
Change #1171311 had a related patch set uploaded (by Eileen; author: Eileen):
[wikimedia/fundraising/crm@master] Pull mailing tags into Civi, add option to make omnimailing.et less verbose
Note I established that it is possible to pull down these tags - command is (with the patch submitted against this phab)
wmf-cv api3 Omnimailing.get start_date="2025-06-15" end_date="2025-06-17" is_include_text=0
@MSuijkerbuijk_WMF I can't fully recall how you were planning on using them once we got them into Civi
If I'm not wrong we wanted to start categorising mailing events (e.g. cultivation, solicitation). I see you authored this task, was this after a conversation with Natalie or Catilin? If not recall, let's wait for us to meet and will come back to you
This came from an Acoustic wishlist conversation! I'm pretty sure this was intended to be a Springlish tag, fulfilling the wishlist item for the field springlish_previousyear_receiver.
Change #1171311 merged by Ejegg:
[wikimedia/fundraising/crm@master] Pull mailing tags into Civi, add option to make omnimailing.et less verbose
@NNgu-WMF Can we continue this convo at the next fortnightly (or sooner)? While @Eileenmcnaughton has enabled the passing of this tag we haven't identified where we'd like to expose it in Civi and how to pass it back it back to Acoustic.