Thanks @Ejegg - looking good.

This task is completed @Ejegg

@Ejegg I'm talking to Anil in detail next week, but just thinking about these options, number 3 might not be too clear for donors, they might not be aware that they are re-snoozing themselves again (unless we tell them). That is my view, but open to see what is doable and the reasoning behind this.

@AKanji-WMF happy to meet to review these.

Phab created https://phabricator.wikimedia.org/T363433
Thanks!

@Ejegg Thanks for explaining. Just a follow up questions:

Thanks @Ejegg -- what do you mean with exclude all donors when they have 'Update recurring contribution'? Do you mean all those who receive the email?
We do not want to do that. Many donors did not open, but that doesn't mean we don't want to reach them again with an upgrade ask and be successful.

@Ejegg Adding Elliott to investigate as he developed the tool

Thanks both, cross-posting from Slack. Great progress to finalise the adjustments (notes doc)

The right URL for a new recurring donation should be a direct link to donate.wiki. This improves donors' experience, instead of having themlook for the link in Ways to Give.

@Ejegg wording looks good to me, I'll leave @AMJohnson to chime in too!

Flagging a couple of issues and questions:

Hi @Ejegg and @ehughes I need to QA these pages and share with email, please could you share the links?

@Ejegg could you share the link with me for testing and @PPenloglou-WMF to add it to the email, please? Thanks

Yes from my perspective good to activate for post MC for now (until I work with Sam and team on how to roll out ACH in the donation form = organic and pre MC)

Hi @Ejegg thanks for your time earlier and your support with this emailing. Here is the updated doc for the renewal emailing.

Yes, thanks. Even if the issue were card declines, I am fine sending this email but I've asked @krobinson to amend it to include the right reason and a renewal link (in case the donor needs to add a new card).

Thanks Elliott.
@krobinson @SHust and @AKanji-WMF tagging you three as per recent conversation. How do you suggest moving forward with this send?
Pasting the copy here again

Sounds good, thanks!

@Ejegg do you have a link to see that flow? And I'm tagging @ehughes as she works on the TY pages (no Panos)
About the format, in my opinion we should follow the same as in the first landing page

@Ejegg you mention a success page above. We are working on Thank You pages (old drafts) for this campaign, but I want to confirm if these are what you are referring to when you say success page, and if so if amount can be passed to it. Or is there going to be a different page in the environment you are developing?

@Ejegg the text change makes sense to me too, thanks

Thanks all, yes we want to also inform them after the 4th attempt that we are restarting. Here is the content and I agree with the exclusions above @Ejegg

@Ejegg We are working with email team on the email push. The delivery date is March 20th, and I'm adding @PPenloglou-WMF here so he can tell us the latest date to receive this URL. Note: Sam and I will need to QA.
@PPenloglou-WMF I suggested to the team that URL will be ready for the Tech QA dates (~March 15), I hope that's possible. Please let Elliott and me know.

@Ejegg Here is the copy for the confirmation email once the donor upgrades. Please loop me in for QA of this piece once ready on Civimail. Thanks

Thanks @jgleeson I understand now. Tested and working for me.

I agree with a 4th attempt. We are ready to do so and DR has also prepared this email to be sent through CiviMail.
@Ejegg last week Anil confirmed FR Tech can support with this email to this small group of donors through CiviMail, could you confirm? FYI Content not final, as there is an open question.
@Ejegg and @EMartin open question about charge date: will it bill on the same date as previously, or will they all now bill on the new reactivation date?
Once we have this answer and DR finalises content, we can go ahead.
Thanks all

@Ejegg The team is working in the content now and will take a couple of weeks to deliver it. Can we work with placeholder copy?

Thanks Elliott, the variant parameter sounds smart.

Thanks, noted

@Cstone
Yes, sp73859020 had a PS added with a donation link. sp73859018 did not have donation links

Only sp73859020 (lapsed recurring) had a donation ask in the PS, this is the data I'm not seeing.

These are the parameters

Is there a way to bring that information into Superset? @JMando @Cstone
Or could you share final numbers for sp73859020 and sp73859018, if possible?

@Eileenmcnaughton Thanks for this. I see the new URL in the template but when I test the email with my record (English US) I still get the Old URL.
Do you know why this might be happening?
For the rest of languages if we remove '&uselang=en' the URL will geolocate, do I need to request this change to Tomasz?

@Cstone and @NNgu-WMF I'm sharing below the copy needed for cancelled recurring, although we might not be able to deploy it on time for this week's receipt send (@NNgu-WMF to confirm)

Thanks for this task. @Cstone once you have information on when this could be released, could you share a timeline with me, @krobinson and @NNgu-WMF so we can agree on send date for the receipt? If this patch will take too long, we might not be able to have it ready for English language recurring donors, but ideally we should. For other languages we can wait and implement next year.

Thanks @Cstone. I've received the email and reviewed it (from a Lapsed recurring perspective). I've suggested adding a renew option shown dynamically for lapsed recurring,. and I've tagged you and Natalie (pending for DR to confirm it's good from their side to add it)

Can the typo in the email get fixed? If not, what options do we have to review how to reactivate Venmo for recurring?

@Cstone
I found it but while I was looking for my recurring contribution (with my personal email CID 62492393) I found my record empty, not reflecting my 2023 recurring donation that recently lapsed. Do you know why that might be happening? I did receive the retry email in October.

@Cstone thanks for sharing this information. Could you send me a test email of this?
Thanks

Hi @Damilare as far as I recall, this is a known fact. During the first conversations with FRU, we already talked about the fact that they don't collect postal address information. Am I correct about that? I don't recall though if we flagged to them that we wanted the postal address (and if it can be done). Do you have that info?

Hi @AKanji-WMF what are the options? I want to avoid suggesting something that might cause issues.
The ideal option would be separate under donate.wikimedia.org (like https://donate.wikimedia.org/wiki/Ways_to_Give) for example donate.wikimedia.org/wiki/campaign-page.
If that is not possible, are you suggesting for example giving.wikimedia.org?
FYI @Pcoombe

Tagging @Pcoombe who might have input here

Thanks @EWilfong_WMF
Please team, could you update us once this change is live?

@Damilare and @AKanji-WMF does this task also cover the case when DR updates a record of a donor who gave through FRU on Civi? This can happen when a donor contacts DR directly, and the team will only update manually on Civi.
As we don't have a two-way sync, how is that update going to show on FRU? Should we check the FRU team again on the API/Webhook or are there alternative solutions being considered?

Hi @Ejegg would you mind pinging me once this is deployed so I can check if the searches show the description?
Thanks!

Hi all, coming back to this task to check on an update. Is this dropdown menu already on Civi? Are we thinking of when to connect it into Acoustic?
As an FYI - we have donation reasons showing in the Recurring dashboard in Superset (Monthly Cancellations tab).
Thanks

Here's the copy from Sophie:

Hi all, jumping in with more detail on this request linked to the work on SEO I am doing with Comms.

@sbassett Thanks for your prompt answer, I have a follow up question: when does the production config deploy happen? Is this also under your team? Apologies for the ignorance, I'm looking at how to help coordinating.

Hi @sbassett -- I'm following up on Peter's note, is there an update to the CSP change? Thanks

Thanks @AKanji-WMF, setting up a call with you to review this task.

Hi @Cstone thanks for this, could you confirm also here that we are good to go with France banners starting this Thursday with the recurring issue on PayPal fixed?
Please share any details needed.
FYI @AKanji-WMF @spatton

Hi @Cstone will you be able to give us a number of donors affected by this issue? Not sure if we know total affected, and total that managed on a second attempt and those that we lost? Is this still only happening in France? Thanks!

Hi @AKanji-WMF acknowledging your note, let me know if you want to share an update. Thanks!

I'm not familiar with the naming conventions in this case, please share more details if you need more input. I'll leave it though to Joseph to decide

Do we have an update on this task confirming that Lapsed/Cancelled Recurring donors have the %AF_recurring_latest_native_amount% populated?

@Ejegg and @JMando I wanted to share here that although upgrading is the main focus, we will work also on features to allow downgrades, pause and cancellations (donor managed). FYI @AKanji-WMF
Hope this is being taken into account, thanks

Hi @Ejegg Please let me know once this field has been implemented also for lapsed recurring as agreed in our call.
This allows us to move forward with those options mentioned in the task description in the upcoming reactivation email (scheduled for July 26)

Hi @AKanji-WMF and @greg
I'd like to share this SEO audit link we've received from Comms agency as it might be helpful for this task
https://app.surferseo.com/audits/s/LAzOtfSx5me5tj6XybqvUZDRb16K09XW

Great, thanks @Cstone

Hi @AKanji-WMF we agreed with Elliott that we can have 2 different ones (one for the Email Pref center and one for the Recurring self-serve/upgrade). For the recurring one I've suggested donorpreferences.wikimedia.org. Is that fine with fr-tech? Do you think that'll have security issues? If yes, the alternative might be recurring.wikimedia.org.

@Ejegg as per our conversation yesterday, I'm waiting to gather information from Evelyn on Ingenico and from Joseph on overall recurring donors per processor before deciding if we launch first only having Adyen recurring as 'eligible for upgrade' (my preferred option right now). I'd need final numbers for that too
Additional detail: we are thinking of targeting donors who signed up 10 months or earlier (10 months is an industry standard, that we'll test on)

Hi @Ejegg
For the Recurring donor self serve portal, I've checked with the team and here's the suggestion: donorpreferences.wikimedia.org
Note that this is not the Email pref subdomain, that should be briefed by the Email team (e.g. emailpreferences.wikimedia.org)
Thanks

This is the last updated flow with the details from the last calls:
https://docs.google.com/presentation/d/1zmLjWW38EfudJEtQYooayjQJICRnossBjuiJmrigQnQ/edit#slide=id.g1dd5ef47764_0_1
And this is the notes doc for the landing upgrade page and the TY pages
https://docs.google.com/document/d/1o1O6SSl05LD5NvIjrgOOHcFp0mi5gW9ak89iQOcisTE/edit#

Thanks @Ejegg this makes sense. We will exclude PayPal donors from upgrades (we can talk if this can change in the future -- I need to gather final figures from Analytics but PayPal is a big size of the recurring base if I'm not wrong).

Hi @Ejegg and @AKanji-WMF
We need to discuss this first, as the Email preference center and the Recurring self-service/upgrade have very different goals.
I don't want the Email Pref center to be always visible, at least not for now, for Recurring campaigns like the upgrade or other.
So, could you give an example of the subdomain structure you'd suggest to avoid this? We can then decide on the best public facing name.

Hi @Ejegg
I need to understand a bit more the domain structure you are suggesting. Will one main domain then have 1/ a sub domain for the Email preference center and 2/ a sub domain for recurring self-service wiki? Is that self-service wiki only recurring or also one-time? Or how are you thinking of this.
This clarification is important as the names for each in my view should be different.
Adding @DBu-WMF

Hi @Ejegg I'm not sure I understand what the implications of not exporting Yes/No are, but if that applies to AF_has_active_recurring I want to clarify that it will be needed as we'll target active recurring that we want to upgrade (in a certain amount range). Because if that field is not there, how will we create the query?

Yes, I updated this doc. You can see there that the email will have 2 CTAs: No, I'll keep as is / Yes, I'll change my monthly amount

The team is reviewing now the Acoustic fields list for the segmentation project so the agreement on field creation-deletion should be linked to that project. I don't have now a reply to this answer. We should work with the Katie and Danny for this.

I have two questions before confirming those are the criteria for upgradable:

• As we will be creating target audiences to upgrade grouping them per current monthly amount, can you confirm that AF_latest_native_amount in Acoustic is equal to the current monthly amount for current and past recurring donors? That field is applicable for one-time donors, but we don't have a specific current_monthly_amount field so we need to triple confirm that'll be the criteria to filter them.
• Once we ran an upsell campaign, we'll need a field that automatically marks if the donor declines or accepts the upgrade (this will allow us to exclude from future upgrade asks). Is this scoped?

Thanks @Ejegg -- Anil and I just talked about these questions, and we have some initial direction but I'll run it by the team to confirm that what we see as the overall direction is good.

Adding a note in case in helps: initially, the recurring upsell will be mainly targeting the U.S. so we will work on recurring upgrades for this market first.

Thanks Evelyn! Noting that the above workflow is a draft open for discussion with fr-tech and other teams involved.

As per Evelyn's last point, it'd be great to confirm if the current Acoustic field 'AF_latest_native_amount' reflects the recurring amount for active recurring donors, or if there's an additional field required. Also, is there a way for us to check on Acoustic or Civi for those recurring cancellations that were due to their card expiring? Thanks

Yes, this probably needs to be reviewed in Q3 as it'd be a great improvement for our growing RML program

@EWilfong_WMF adding you to review these details
@Eileenmcnaughton I agree that any change or fix we do now should have the lowest impact on the data, or else we'd need to delay it to future quarters

Hi @Eileenmcnaughton -- just wanted to check if there is an update on this task. I've talked to Eric yesterday and we'd need to know if this is feasible and doable for December banner campaign. On my side, I'd need to update email templates if yes. Thanks so much for your help!

Hi @DStrine
Here's the link to the RML program documentation
Let me know if you need any clarification.

Thanks @KHaggard for the note about timelines for recurring amounts -- makes total sense.

Thanks @Eileenmcnaughton for explaining on reactivations, no issue there.

Thanks @Eileenmcnaughton -- these changes are a good step and will allow us to enrich recurring donors segmentation.

Thanks @Eileenmcnaughton -- The start and end date will allow us to see the recurring donation duration which is a great improvement, thanks again! I'd just want to clarify how can we accurately segment Active recurring donors.

Thanks for the update.

Hi @DStrine -- could I ask if there's any update or info needed on this task? Thanks!