Sat, Jun 27
Option #2 shouldn’t be a possibility... we want it to be easy for someone
to switch their opt-in preferences, which means we handle them on the
Acoustic side. If they are added to the suppression list, how will they get
removed from the Acoustic list if they opt back in?
Thu, Jun 25
I'm fine with using the Acoustic link as long as it works for y'all in
Yeah to put a fine point on it, we *can't* map to a field that doesn't yet
exist in the import. We need you to add it before we can map it.
Tue, Jun 23
Can she provide a sample Zendesk ticket? It should be easy enough to tell
what type of email this is.
Which email was this from? I read the title of this task and thought it was referring to a Civi TY email.
Mon, Jun 22
Jumping in since Katie is having a busy week. I want to add a response to
your question along with a few process notes:
Wed, Jun 17
Thank you, Moska! Re your last comment, we are on Pod 4 so we will be affected.
Tue, Jun 16
I can't think of anything else! If fr-tech thinks this still works, can
y'all perform your own test or jump on a screenshare with Katers to
show her how to confirm it works? Seems like something might not be working
Thu, Jun 11
I think I still want to defer to Nora here :) I don't know what is in each
of these fields.
I think I want to defer to Nora for what fields we need, as I haven't seen
the HEP data and don't know what all is at our disposal. The purpose of the
emails we're going to send is to connect donors to their relevant matching
Tue, Jun 9
Please get us the column headers and demo data whenever you can! That will allow the email team to get to work while y'all do your side.
Wed, Jun 3
Thanks so much for catching this, Katie! This seems like a big deal so I am setting the priority at High.
Per my comment on the parent task T228765, I don't think fr-tech owns this portion of the task. Should we keep it open and have someone from my team claim it, or close?
Per my update on the parent task T228765, I think this task description needs to be updated to instead Create a job to export HEP data to Acoustic on an employer-ID level.
Adding my notes here from our meeting just now with fr-tech and MGF to confirm next steps for email integration. I'm adding @MNoorWMF and @KHaggard to this task as I'll need their help with implementation.
Tue, Jun 2
@MNoorWMF will be taking the lead on this! We will need to make a change to all urls in all templates which will take a bit of time. We are committing to wrapping this by EOQ.
May 27 2020
Seems like we can resolve this on the email side by adding the contact_hash, along with contactID, to all urls. Will discuss this with the email team next Tuesday and confirm when we implement
May 6 2020
This seems like a great idea! Monthly makes sense to me unless @EYener sees
a reason to do it more frequently.
May 5 2020
Checked in with David and Dylan today and bumped Mariana's question above
re: hosting multiple versions of the form for small dollar and major
donors. Dylan said fr-tech was aware this was a desired feature and are
hoping to be able to support it. fr-creative will proceed assuming we can
maintain multiple versions of the form, and fr-tech will let us know if
Apr 6 2020
I just updated the url for "starter text" in the task description. The copy is actually the same as it was in the original link, but I've stripped out some confusing bits from the OG doc.
Mar 18 2020
Thanks, Nora! This is a good argument for the preference center for sure.
Mar 3 2020
Ccing @KHaggard so she can track changes to the imports as a result of this
task (when completed).
Ccing @KHaggard so she can follow changes on this task.
Feb 21 2020
Feb 12 2020
Feb 6 2020
Thanks so much for jumping on this, Peter :)
Feb 5 2020
Fine with me!
Okay thanks, English-only seems super doable. Does it seem fair to update
the task description to reflect that?
This *could* be a big translation ask and we're running a little low on budget for that. Just checking, what's the priority on this? Would it be good enough to address for the next TY, or does it need to be changed now?
Jan 16 2020
Ooh thanks for all the digging, Eileen. That copy is from an RML email for
Dec 17 2019
Hmm, that mailing is a remind me later mailing. Those are special cases
because they're sent as automated programs on timers based on user
behavior, rather than as bulk sends. We use different reports to get the
performance data for automated programs. Maybe that's why you can't see the
Dec 6 2019
Dec 5 2019
Thank you! That looks good to me.
Dec 2 2019
Ah, there must be duplicate rows on that import or something. We show
3,065,196 in IBM now. Higher than when I last checked :)
@Ejegg nope, that sounds really high. We have a total suppression list of
about 2M -- 426k would be a 25% increase in our total suppression list.
Nov 27 2019
Thanks so much for all the digging, Eileen! Looking forward to seeing how
things look tomorrow. I'll be happy to research the mailings that you think
may be deleted or do any other QA on the ESP side. Let me know how I can
Nov 26 2019
Wonderful, thank you!
Nov 25 2019
They should be... we aren't able to access the files after upload.
And the file we upload has no duplicate email addresses?
Nov 20 2019
Okay thanks for digging into this and explaining the current prcess! @MBeat33 please have your team chime in if they have other examples they wanted us to look at. It sounds like these were cases of email address typos.
Nov 19 2019
Some sample CIDs:
The new copy has been reviewed and approved by Sam, Michael, and Camille as well. This should be ready to go live :)
Nov 13 2019
Cool suggestion! I like it.
Nov 12 2019
Nov 9 2019
Here are the API details!
Nov 8 2019
Fwiw, I don't think the problem is the filtering scan, I think it's the timing of when this stripe donation got added to Civi. If I'm reading their contribution record right, their contribution was Enqueued At Timestamp Oct 24, 2019 16:10, which was 2 days after the email went out and 7 days after they donated.
Thanks for opening the ticket! If there's an API call to IBM to remove
people on the suppression list, that would be our best bet, though I don't
know if that exists. Should I ask our consultants?
Nov 6 2019
Ah, I see. Here's the current login page:
You don't have to actually reset the IBM id, IIRC, only the campaign
automation login. Let me know if you need us to check with our consultant
Thanks, Elliott! We didn't realize this was a requirement with the system.
We learned our lesson ;)
Nov 4 2019
Wonderful, thank you all for the help!
Okay, I saved the pw in a file called silverpop.txt as suggested.
Nov 1 2019
I just reset the password on the account so Katie could get in and try to re-run the file imports, but now y'all need to reset the pw again on your side. I'm going to update the task title to reflect that.
Oct 31 2019
Okay, then we need to find a way to use the silverpop API to remove people
from the suppression list when they opt back in.
That looks right to me! I want to note that from a silverpop perspective, scenario 2 would require an extra step of us removing a contact from the Suppression list. I think that has to be done manually, though maybe there's an API call for it.
Oct 24 2019
I think my preference is option 2. I know we were concerned about people
who opted in NO and some point and changed their response to YES in the
future. It seems easier to me to set up an annual workflow where we remove
anyone from the unsubscribes list who has changed their response to YES.
Does that seem sensible?
Oct 23 2019
So awesome! Thanks, everyone :)
Oct 16 2019
Huh, I remember us discussing that latest_optin_response field but I
thought we settled on opting these people out. I think that's what we need
to do--turn the opt out on the banner into a hard no.
Oct 8 2019
Definitely, the expected behavior is if someone opts-out of bulk email
while donating, they should be marked as opted-out in Civi and added to the
unsubscribes file that gets sent to IBM each night.
Oct 4 2019
Thank you all so much.
Oct 3 2019
Yeah, you'll need a CiviCRM cert to access the dash (
https://dash.frdev.wikimedia.org) at the least. Sorry, I take for granted
that we just set this up for fundraising people :)
Cool, we must've missed the cutoff time. Thanks, Katie!
Never manually add if it's data we're importing from Civi :) You should see
it when setting up the import. If you don't, just hit run on today's import
and we'll try again tomorrow.
I'm optimistic we caught it in time :) otherwise we'll try again tomorrow.
Hey Eileen, my mistake, I thought it had been deployed! We had already put
the import on pause last night so we could import the new data today. Is it
possible to squeeze it into today's import?
Oct 1 2019
Ooh awesome, sounds like hardly any lag at all, even in the event of a
Thanks so much for this! Just one last question--how often will this be
updated? Daily? Will there ever be a lag?
This is ultimately up to Michael, but I'm wondering if it'll be easier on
DS to send these in a few isolated batches so their team knows when to
expect them. Like 4 batchs of 10k, one per week?
We can use birth_date.
It would be great if she has access to all the same databases that I do,
but these are the ones on my mind:
Sep 24 2019
Okay, from meeting with Elliott, it sounds like the multi-currency
formatting is not a concern. I'm down with Michael's suggestion! Noting as
well that Michael confirmed it's good to remove endowment donations.
And @MBeat33 's suggestion above is fine for me, though I am skeptical as to how much sense it makes to support the annual totals in multiple currencies. Is that easy enough to do, or should we scrap the annual total?
Yes, omit endowment donations @Ejegg!
Sep 23 2019
Ah yessss this is so awesome, Eileen!! Would be good to rename that hash
field if possible to utm_source or mailing_id or something so it's easier
to find and join across tables, but I think this is exactly what I wanted
:D And just in time for our new analysts to use.
Sep 18 2019
Thanks, Eileen! We're going to set up a new recurring import tomorrow. I
think you can close this on your end.
Sep 11 2019
Thanks, Eileen! Let us know when that new data gets added. We didn't set up
those new fields to import on a recurring basis because we didn't want to
slow down import runtime, so we'll need to do another manual import to add
Sep 6 2019
Oh sorry! If we're talking exact matches, yes, I think they should be opted
out until the donor tells us otherwise. My bad 😊
Great, thanks @Eileenmcnaughton! I just told IBM to skip today's import so
I think the file should be around for Katie and me to import later. We'll
update this task with how it goes!
@Eileenmcnaughton let me know if I should pull in Trilogy for help!
Hm, I would disagree here. I might expect a donor would unsubscribe their
old email address knowing that they only check it for certain purposes and
only want to receive emails from us at a different address. I think we
should let donors specify communications preferences on a per-email basis.
Sep 4 2019
Sounds good! Thank you :)
It runs daily at 9am UTC.
Okay! Would be great to do this on the Friday morning UTC export since we
aren't sending emails on Friday, just in case something goes amiss with the
Aug 31 2019
Thanks, everyone, for jumping on a very unexpected task. I appreciate all
the follow-up and feedback.