Update! The link tracking domain removed support for TLS 1.0 and 1.1, so now score higher:

Is there a new task for backfilling the data? If not, can we keep this one
open?

Also, re: question A -- this actually helps point out a funny inconsistency in our unsubscribe rules. Because Legal has tested our forms more than once, the privacy@wikimedia.org contact record has inconsistent data:

• country = MX
• RML_country = IN

@MNoorWMF can help or delegate this to trilogy. Thanks!

Hmm, basing off what email does, I might do something like:
utm_medium=civi-mail
utm_campaign=FailedRecur
utm_source=FY2021_FailedRecur

Just adding a little more info from Acoustic--it seems like the API calls we're using with the old URLs are related to GDPR. This could potentially be problematic for France if we aren't accurately handling GDPR requests. The France campaign launches in two weeks.

Bump! See Moska's Q above.

Great, thank you!

Sorry, one more question: Will this data automatically be included in the
Acoustic export once it's imported? Or is there a separate task for that?

Okay great, thanks for the confirmation!

Awesome, thank you! Let us know your ETA so we can get our ducks in a row
and prepare for the next steps in our targeting projections :)

Cool! So are we expecting this will take a few days to complete? Should we
expect it in the email export by EOW, or what do you think?

Ah got it, I didn’t realize how the process worked. We may just have to
move some deadlines set for us to review the targeting strategy with
leadership. Pats said that’s fine so just keep us posted on an ETA.

Yay!! Thank you both, Katie and Eileen, for the great work and
communication this week.

Thanks for working on this, @mepps! Any chance we'll be able to resolve
this during this week? We're hoping to have all the data we need by Monday
so we restart our targeting work.

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?

I'm fine with using the Acoustic link as long as it works for y'all in
testing.

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.

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.

Makes sense!

Jumping in since Katie is having a busy week. I want to add a response to
your question along with a few process notes:

Thank you, Moska! Re your last comment, we are on Pod 4 so we will be affected.

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
here.

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
gifts portals.

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.

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.

@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.

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

This seems like a great idea! Monthly makes sense to me unless @EYener sees
a reason to do it more frequently.

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
that changes.

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.

Thanks, Nora! This is a good argument for the preference center for sure.

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.

Confirmed!

@MNoorWMF @CDenes_WMF

Thanks so much for jumping on this, Peter :)

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?

Ooh thanks for all the digging, Eileen. That copy is from an RML email for
sure!

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
sent numbers?

Thank you! That looks good to me.

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.

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
help!

Wonderful, thank you!

They should be... we aren't able to access the files after upload.

And the file we upload has no duplicate email addresses?

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.

Some sample CIDs:
24041039
30066653
5396632

The new copy has been reviewed and approved by Sam, Michael, and Camille as well. This should be ready to go live :)

Cool suggestion! I like it.

Here are the API details!

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?

Ah, I see. Here's the current login page:
https://www.customer-engagement.ibm.com/marketing/launch/

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
on this.

Thanks, Elliott! We didn't realize this was a requirement with the system.
We learned our lesson ;)

Wonderful, thank you all for the help!

Okay, I saved the pw in a file called silverpop.txt as suggested.

Hey y'all,

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.

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.

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?

So awesome! Thanks, everyone :)

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.

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.

Thank you all so much.

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.
Thanks!

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?