Closed kwussow closed 4 years ago
Where we are today November 12, 2019 Email template with dynamic content blocks is created Need to validate content is correct Add member desk links to content
DE spreadsheet template is built, but not populated
SQL script is needed to automatically populate the DE
Webinars are populated in SFDC for the past year
Blogs are in progress, will populate in SFDC week of 11/11/19
KCSP and KTP are up to date
Logo URL is up to date
Interviewing contractors to complete the above work.
Marijana to provide feedback on technical skills outlined in the requirements document
@dankohn and @KimMcMahon We've made great progress in building the DE. @dheerajkottali has the DE almost complete which contains all of the data needed to populate the email correctly. He should have this ready for testing soon and is beginning to build out the email template today. We are working to test the email later this week with an internal list. Then we'll move to test with a small member subset to validate the data is pulling correctly. Our goal is to send the email to all of our members (primary, marketing, and technical contacts on file) on January 6th, once everyone has returned from the holidays.
Documentation of locations of custom DEs, SQL queries and email template in SFMC is here: https://docs.google.com/document/d/1NubMrf8DuZMCDbtDP6RCzhbd-T-qIDtONJwjhn9VMic/edit?usp=sharing
Update: The first member engagement email went out on February 12, 2020 to 706 contacts! We did uncover an issue with subscriber keys, which caused 188 contacts to not receive our email. Marijana is working to fix this as it's a global SFMC issue. This ticket is where we are tracking the progress: https://jira.linuxfoundation.org/browse/DMO-77
Luckily, Dheeraj pulled all reports needed last Friday to determine who received our email and who did not. Today, all subscriber keys were deleted and with this, the tracking on an individual level. We still have overall open and click rates, just no ability to see individually who engaged or did not engage with the email.
Dheeraj is creating a report and DE to capture the contacts that we missed. However, we are in a holding pattern until the subscriber key issue is fixed to send out to the missing 188 contacts.
Planning for future emails Frequency: Email 1: Delivered 2/12/2020 showing data from 6/1/2019 to 12/31/2019 Email 2: Est delivery 4/13/2020 showing data from 10/1/2019 to 3/31/2020 Email 3: Est delivery 7/13/2020 showing data from 1/1/2020 to 6/30/2020 Email 4: Est delivery 10/12/2020 showing data from 4/1/2020 to 9/30/2020
Planned Items to include in Q2:
Still waiting for KCSP, KTP and Certified Kubernetes drop down fields to be created in SFDC. See Jira ticket: https://jira.linuxfoundation.org/browse/PG-546
Closed as Q1 was completed, see Q2 for the next phases of member engagement email quarterly. #16 #15
Deliverable: Develop quarterly member engagement email. Detailed requirements are documented in this google doc.
Technical requirements to execute using SFMC and SFDC:
[x] Build a custom data extension to populate dynamic content blocks
[x] Build and manage SQL queries to automatically populate DE every quarter
[x] Fix any mapping issues/logic with the DE and dynamic content blocks as needed
[x] Create new fields in SFDC to be able to populate the DE as needed
[x] Build a custom report and dashboard to track engagement with the email
[x] Build email in such a way that when we get feedback from the member EG: I do not want to become a KCSP or KTP. Ensure this content is not displayed in the next quarter.