The DR team will start adding campaign preference tags to donors who insist on participating in specific campaigns to prevent them from being permanently unsubscribed from our database, starting in Q1. Currently, we have two tags: 'preference: End Of The Year Campaign' and 'preference: Spring Campaign Only'. As we prepare for upcoming direct mail, SMS, and other potential campaigns, we will be adding more tags. Erica suggested creating a field in Acoustic to automatically sync these preference tags with Civi nightly, just like the rest of the information. This would eliminate the need to manually pull and share lists of donors to exclude from non-preferred campaigns, which won’t be sustainable once we roll out the campaigns mentioned above.
Description
Details
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | Eileenmcnaughton | T365826 Acoustic SMS stage 1 Scoping: Supporting SMS campaign functionality in Acoustic | |||
Resolved | Eileenmcnaughton | T366212 Acoustic SMS stage 2 Civi Tag sync with Acoustic - feature request |
Event Timeline
I think the suggestion by Katie was to create a new field in Acoustic with the options specified.
The questions I have are
- who creates this field now Katie is gone
- what should it be named - probably either 'preference_tags' or 'tags' - depending on whether the preference tags will be the only ones pushed up. It's probably easier for the options to match the full tag name (ie 'Preference: Exclude from Direct Mail Campaigns'). Capitalization probably needs to match.
- what changes do we expect going forwards - will more tags be created - who will create then at the Civi & Acoustic end
@Eileenmcnaughton, Katers had a call with Natalie, Panos, and me where she explained to them what’s needed on the acoustic side.
Regarding the questions, "Will more tags be created?" and "Who will create them on the Civi and Acoustic sides" — these tags are campaign-based, and I’ve already created the ones for the current and future planned campaigns. I’m also happy to take responsibility for the Civi side if more tags are needed (creation, documentation, and communication across teams).
Here's the call transcript.
During our call today @NNgu-WMF created the new field preference_tags in Acoustic (todo - double check it's not preferences_tags) - the options are the same as the tag labels in Civi (which have changed since the screen shot) without the preceding 'preference: '
Adding a note here @SHust - our team will need to sync with DR to agree on how to use these tags. Please ping me once this request is completed by FR Tech
I did some testing with csv uploads manually & this looks like the right format for the csv - note
- semi-colon separator
- case-sensitive matching
- no additional spaces
- @NNichols had some concerns on slack so tagging Nora in
Change #1080091 had a related patch set uploaded (by Eileen; author: Eileen):
[wikimedia/fundraising/crm@master] Add preference_tags, per prod
Change #1080097 had a related patch set uploaded (by Eileen; author: Eileen):
[wikimedia/fundraising/tools@master] Export preference_tags as part of nightly update
Change #1080091 merged by jenkins-bot:
[wikimedia/fundraising/crm@master] Add preference_tags, per prod
Change #1080097 merged by jenkins-bot:
[wikimedia/fundraising/tools@master] Export preference_tags as part of nightly update
This is done - although not all tags will be pushed up as we have not done a full DB upload since this was deployed