@Ejegg as per above, can you confirm it's all set? Thanks!

Thanks @Ejegg does this mean this issue is fixed? @Cstone I believe the data is correct in Superset right? I recall that work was done too. I mean here: https://analytics.frdev.wikimedia.org/superset/dashboard/175/

Done https://phabricator.wikimedia.org/T377438
This one can be closed.

@AKanji-WMF Google Ads run mainly in the U.S., where most of the volume comes from. We also have UK, CA and AU but not a priority to relaunch.

Thanks, this is with @RLopez-WMF for updating.

Hi @AKanji-WMF could we look into this? We are talking to the Legal team and they'd need some information from us like where we add the pixel and what info we gather.
Is it possible? Thanks

Hi @Ejegg as we approach the final QA before testing Annual recurring, can you please confirm that the Thank You email and Thank you pages have been updated for annual recurring sign ups?

Thanks for that example @Eileenmcnaughton. Such cases can be tackled on our end with exclusions/inclusions of active annual recurring. I'll be in charge of adding it to our campaigns and data briefs.

@Eileenmcnaughton - thanks for following up on this. To your question, yes, we are going to target Delinquent monthly recurring in the reactivation series. But I don't understand the overlap or issue you mention with Annual recurring, do you mind sharing an example?

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

@Eileenmcnaughton Yes, I agree. One way to fix this could be: while segments keep Monthly prioritised over Annual, in the statuses we should work on specific order to account for such situations. Do you agree? Should we set a timeline to work on this?

@Eileenmcnaughton Overall, our logic should reflect that Monthly recurring will take priority.

Thanks. I'm planning a new upgrading push in Q3 (February-March). Great to see this work in progress

Any changes needed for this in timing of email?
The Failure email is important to be kept and optimised (fyi - we are looking with Christine and Anil at adding a second one).

There's a possibility we might in the future, let me explore. Thanks

Adding a follow up question as per Slack @AKanji-WMF -- would it be possible to add the Google tracking pixel to the FRU donation form in Wikipedia and use that for the Google ads activity? This would be a solution and simplify the internal steps related to privacy

Confirming 450 for annual recurring can be used. Additionally, we need to review the statuses and create new ones for annual recurring. Important: the monthly donors statuses do NOT apply to annual recurring. @Eileenmcnaughton

@Cstone We should show the numbers and decimals in the same way we do in control, so no need to change, just make sure we are not changing amounts or how we show amounts. Thanks

Hi @Eileenmcnaughton So to clarify, the annual recurring fields and tagging are already in Civi?

@Ejegg Cross-tagging you in reference to the dynamic fields, please confirm those are still correct for annual recurring
https://app.asana.com/0/1130715260221313/1208066022237986

Do we also need no mailing weeks to implement the fields in Civi? If we could have the fields in Civi, and run the test in banners, we should be fine because in email we exclude active and new donors so we don't retarget them.

Hi @Cstone and @AKanji-WMF Do we have an update on this second email? I can help with the rules and edge cases.
Could we agree on a timeline for this? Thanks!

@Ejegg Emma is working in the TY page variant and the email team in the Email receipt (timeline for this August 29).
Posting here @ehughes question, could you support on this?
CCing @AKanji-WMF

Hi @Ejegg It looks good, the only change I don't see implemented is the rounding up to $2.00 note that Sam had in there. Let me know if there is any issue with that.
Please once done, let me know and I'll share it with the team.

Cross-posting this request. If this is in progress, would you mind adding the Civi fields for reference and when could we add those to Acoustic?
https://phabricator.wikimedia.org/T372378

I'll brief the team on this, do you have a timeline?

@Cstone We should keep it as control. If I'm not wrong, we show decimals (2.00, 1.75)

@Ejegg I've updated the copy https://docs.google.com/document/d/121zeT8zm_odXcGwPA01FJIyvr7yw7kuGad-OAeiI3Vs/edit#heading=h.svp7ls6ziyoj

Posting here the final variant we have discussed with notes on second screens too.
https://docs.google.com/document/d/121zeT8zm_odXcGwPA01FJIyvr7yw7kuGad-OAeiI3Vs/edit#heading=h.svp7ls6ziyoj

@AKanji-WMF Thanks! This is clear. We can send the second email 7 days after the first one. @Cstone would that work for you?
Also, I've added the correct URLs in the content document here (e.g. updating the FY). We need to make sure those are correct in both the updated current first email and the new second email, I can QA those test emails when ready.

Apologies I missed this ping. I agree with grouping if @EMartin considers it's a good approach and the team doesn't foresee issues with this option.

@Ejegg Yes, we need to offer both annual and monthly at the same time, as well as 'No thanks', and we will ideally test several variants. For now, we want to test the one shared in the description of this task.

@Ejegg Yes, we will test the variant that Sam prepped in that link, removing the option to give a different monthly amount. We should explore though options to let donors change the amount if they need to. But I'd prefer if we did that with Sam and the team. Thanks

Thanks

@AKanji-WMF confirming that the content doc is now ready with the right sender (Sandra) as per above details

@AKanji-WMF Yes, let me add more detail

@Eileenmcnaughton @KHaggard @ERoden-WMF
Hi all, jumping in with a suggestion in case it helps: in the past we've only targeted recent RML non donor sign ups, so we could explore adding a time range (past 2 or 3 years sign ups).

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