Email Interactions

 Email Interactions :

YOU CAN WRITE SSJS TO RETRIEVE THE DATA VIEWS AND CREATE A DASHBOARD FOR THE MARKETERS. DEFINING HOW MANY SUBSCRIBERS INTERACTED WITH THE CAMPAIGNS AND GENERATE REPORTS FOR  KPIs


PRINT THE SUBSCRIBERS WHO RECEIVED THE EMAIL

<script type="javascript" runat="server">
Platform.Load("core","1.1.1");
try {
     var date= Now();
     var d = new Date(date);
    var dataRows = Platform.Function.LookupRows('_Sent','EventDate',d);
   if(dataRows && dataRows.length > 0) {
         for(var i=0; i<dataRows.length; i++) {
               Platform.Response.Write(dataRows[i]["JobID"]);
               Platform.Response.Write('|');
               //Platform.Response.Write(dataRows[i]["SubscriberID"]);
               Platform.Response.Write('|');
               //Platform.Response.Write(dataRows[i]["EventDate"]);
               
               Platform.Response.Write('\n');
            }
          }
    }
 catch (e) {
  Write("<br>Exception: " + e);
}
</script>

PRINT THE SUBSCRIBERS WHO OPENED THE EMAIL


<script type="javascript" runat="server">
Platform.Load("core","1.1.1");
try {
     var date= Now();
     var d = new Date(date);
    var dataRows = Platform.Function.LookupRows('_Open','EventDate',d);
   if(dataRows && dataRows.length > 0) {
         for(var i=0; i<dataRows.length; i++) {
               Platform.Response.Write(dataRows[i]["JobID"]);
               Platform.Response.Write('|');
               //Platform.Response.Write(dataRows[i]["SubscriberID"]);
               Platform.Response.Write('|');
               //Platform.Response.Write(dataRows[i]["EventDate"]);
               
               Platform.Response.Write('\n');
            }
          }
    }
 catch (e) {
  Write("<br>Exception: " + e);
}
</script>


PRINT THE SUBSCRIBERS WHO CLICKED

<script type="javascript" runat="server">
Platform.Load("core","1.1.1");
try {
     var date= Now();
     var d = new Date(date);
    var dataRows = Platform.Function.LookupRows('_Click','EventDate',d);
   if(dataRows && dataRows.length > 0) {
         for(var i=0; i<dataRows.length; i++) {
               Platform.Response.Write(dataRows[i]["JobID"]);
               Platform.Response.Write('|');
               //Platform.Response.Write(dataRows[i]["SubscriberID"]);
               Platform.Response.Write('|');
               //Platform.Response.Write(dataRows[i]["EventDate"]);
               
               Platform.Response.Write('\n');
            }
          }
    }
 catch (e) {
  Write("<br>Exception: " + e);
}
</script>

PRINT THE JOURNEYS THAT ARE RUNNING

<script type="javascript" runat="server">
Platform.Load("core","1.1.1");
try {
    var dataRows = Platform.Function.LookupRows('_Journey','JourneyStatus','Running');
   if(dataRows && dataRows.length > 0) {
         for(var i=0; i<dataRows.length; i++) {
               Platform.Response.Write(dataRows[i]["JourneyName"]);
               Platform.Response.Write('|');
               Platform.Response.Write(dataRows[i]["LastPublishedDate"]);
               Platform.Response.Write('|');
               Platform.Response.Write(dataRows[i]["JourneyID"]);
               
               Platform.Response.Write('\n');
            }
          }
    }
 catch (e) {
  Write("<br>Exception: " + e);
}

</script>


THE OTHER WAY IS TO CREATE AN AUTOMATION AND STORE THE DATA INTO DATA EXTENSIONS FROM DATA VIEWS REGULARLY [DAILY].

PULL THE DATA AND SHOW THEM IN A DASHBOARD IN CLOUD PAGES

DEFINE THE SUBSCRIEBERS INTERACTIONS


Select
s.NumberOfEmailsSent,
o.NumberOfOpens,
s.SubscriberKey,
c.NumberOfClicks,
b.NumberOfBounce,
CASE
    WHEN s.NumberOfEmailsSent > 30 THEN 'Saturated'
    WHEN s.NumberOfEmailsSent = 30 THEN 'Almost Saturated'
    WHEN s.NumberOfEmailsSent < 30 OR s.NumberOfEmailsSent > 10 THEN 'Undersaturated'
    ELSE 'On Target'
END AS Status
from
(Select  count(*) as NumberOfEmailsSent, SubscriberKey from  _sent
WHERE EventDate >= DATEADD(day, -30, GETDATE())
group by SubscriberKey ) s
LEFT join
(Select count(*) as NumberOfOpens, SubscriberKey from  _open
WHERE EventDate >= DATEADD(day, -30, GETDATE())
group by SubscriberKey) o
on s.SubscriberKey=o.SubscriberKey
LEFT join
(Select count(*) as NumberOfClicks,SubscriberKey from  _click
WHERE EventDate >= DATEADD(day, -30, GETDATE())
group by SubscriberKey) c
on s.SubscriberKey=c.SubscriberKey
LEFT join
(Select count(*) as NumberOfBounce,SubscriberKey from  _bounce
WHERE EventDate >= DATEADD(day, -30, GETDATE())
group by SubscriberKey) b
on s.SubscriberKey=b.SubscriberKey

ONCE YOU DEFINE THE SUBSCRIEBERS INTERACTIONS

YOU CAN DEFINE THE SEND TIME OPTIMIZATIONS BASED

ON HOW LIKELY THE SUBSCRIBERS OPENS

SELECT
SubscriberKey,
CASE
WHEN s.WEEKDAY=0 THEN 'MONDAY'
WHEN s.WEEKDAY=1 THEN 'TUSEDAY'
WHEN s.WEEKDAY=2 THEN 'WEDNESDAY'
WHEN s.WEEKDAY=3 THEN 'THURSDAY'
WHEN s.WEEKDAY=4 THEN 'FRIDAY'
WHEN s.WEEKDAY=5 THEN 'SATURDAY'
WHEN s.WEEKDAY=6 THEN 'SUNDAY'
END
AS LIKELYOPENSON
FROM
(SELECT MAX(DATEPART(WEEKDAY, EventDate)) AS WEEKDAY,SubscriberKey from _Open
WHERE EventDate >= DATEADD(day, -30, GETDATE())
group by SubscriberKey) s
WHERE SubscriberKey IN (SELECT SubscriberKey FROM Interaction_Status )




Comments

Post a Comment


Knowledge Article

Most Viewed

Image

CLOUD PAGE ENABLEMENT - PART 1

 CLOUD PAGE ENABLEMENT - PART 1 CREATE A CLOUD PAGE IN MARKETING CLOUD  USE CASE : Create a landing page in marketing cloud to collect consent from subscribers. Step 1: Create a landing page and publish it [no coding required] Step 2: Build a form control using bootstrap  <form class = "row g-3"       action = "https://tenantEndpoint/ConsentCollection"       method = "Post" > </form> Update your form "action" attribute value with your cloud page URL. Method attribute "Post" Add form controls  To collect email, add the below form control <div class = "col-md-6" >       <label for = "inputEmail4" class = "form-label" > Email </label>       <input type = "email" class = "form-control"               id = "inputEmail4" name = "inputEmail4"               value = "%%=v(@inputEmail4)=%%" required %% = v(@disabled) = %% &
Image

EMAIL NOT SENT IN JOURNEY BUILDER

TROUBLESHOOTING JOURNEY SENDS First step towards troubleshooting in SFMC is to install Query Studio from AppExchange. https://appexchange.salesforce.com/appxListingDetail?listingId=a0N3A00000FP3yFUAT Once you have access to Query studio you can write SQL queries and troubleshoot the issues quickly. If you are building a complex queries for a use case, you can write and execute the queries to see if it returns the desired output. Once, you are satisfied with your query you can save and add it to query activity. You can also save the output into a data extension if required, by default query studio stores the output into a data extension under the folder QueryStudioResults. If you have to execute another SQL with the output of the previous result, you can reference the Data Extensions and apply it in your FROM statement. FAQ : 1. How to find out who all did not receive email during journey send ? Best practice is to enable send logging for your account. This will help a-lot during troubl
Image

CONSIDERATIONS FOR JOURNEY BUILDER

 CONSIDERATIONS FOR JOURNEY BUILDER   WHAT HAPPENS WHEN YOU SEND AN EMAIL OUTBOUND MAIL MANAGEMENT GETS INVOKED BY MARKETING CLOUD , OMM IS NOT IN OUR CONTROL BUT LETS GO THROUGH BEHIND THE SCENE ACTIONS. 1. OOM PREPARES DATABASE FOR THE JOBS, OOM ANALYZES THE EMAIL, WHETHER IT'S A TEMPLATE BASED EMAIL OR HTML, WHETHER EMAILS CONTAINS PERSONALIZATIONS OR DYANMIC CONTNETS.  2.  OOM STRUCTURES THE EMAIL BASED ON HEADER , BODY AND FOOTER. OOM RETRIEVES THE SUBJECT LINE , BODY CONTENT , AMPSCRIPT IN THE EMAIL AND INTERPRETS THE AMPSCRIPT AND RETIRVES IMAGES. 3. BASED ON THE DATABASE AND STRUCUTRE MAINATAINED BY THE OOM, IT DETERMINES THE CONTENT FOR THE SUBSCRIBERS AND PROCESSES TO MAINTAIN THE PLACEHOLDERS FOR EACH SUBSCRIBERS. 4. OOM HAS PLACED THE PROCESSES IN THE QUEUE, OOM BUNDLES EMAILS IN 500 BATCHES AND SEND TO SUBSCRIBERS INBOX.  NOW WE HAVE THE BACKGROUD , WHAT ARE THE CONSIDERATIONS FOR BUILDING A JOURNEY  JOURNEY PERFORMANCE ARE BASED ON : 1. DATA MODEL 2. FILTERS  3. JOURN
Image

Journey Builder REST API Documentation

Journey Builder REST API Documentation Home Page Journey Builder REST API Documentation Introduction The Journey Builder REST API allows you to programmatically interact with the Journey Builder feature of Salesforce Marketing Cloud. With this API, you can create, update, and manage customer journeys, as well as perform various operations related to contacts and interactions within those journeys. This document provides detailed information on how to use the Journey Builder REST API to integrate and automate your marketing workflows. Base URL The base URL for accessing the Journey Builder REST API is:
Image

Preference Center Demystified

Preference Center Demistifier Home Page Preference Center Demystified Email preference centers can unlock a wealth of subscriber information if executed properly. Learn more about them to create the personalized email experiences that build loyalty and trust.

Popular Posts

Image

CLOUD PAGE ENABLEMENT - PART 1

 CLOUD PAGE ENABLEMENT - PART 1 CREATE A CLOUD PAGE IN MARKETING CLOUD  USE CASE : Create a landing page in marketing cloud to collect consent from subscribers. Step 1: Create a landing page and publish it [no coding required] Step 2: Build a form control using bootstrap  <form class = "row g-3"       action = "https://tenantEndpoint/ConsentCollection"       method = "Post" > </form> Update your form "action" attribute value with your cloud page URL. Method attribute "Post" Add form controls  To collect email, add the below form control <div class = "col-md-6" >       <label for = "inputEmail4" class = "form-label" > Email </label>       <input type = "email" class = "form-control"               id = "inputEmail4" name = "inputEmail4"               value = "%%=v(@inputEmail4)=%%" required %% = v(@disabled) = %% &
Image

EMAIL NOT SENT IN JOURNEY BUILDER

TROUBLESHOOTING JOURNEY SENDS First step towards troubleshooting in SFMC is to install Query Studio from AppExchange. https://appexchange.salesforce.com/appxListingDetail?listingId=a0N3A00000FP3yFUAT Once you have access to Query studio you can write SQL queries and troubleshoot the issues quickly. If you are building a complex queries for a use case, you can write and execute the queries to see if it returns the desired output. Once, you are satisfied with your query you can save and add it to query activity. You can also save the output into a data extension if required, by default query studio stores the output into a data extension under the folder QueryStudioResults. If you have to execute another SQL with the output of the previous result, you can reference the Data Extensions and apply it in your FROM statement. FAQ : 1. How to find out who all did not receive email during journey send ? Best practice is to enable send logging for your account. This will help a-lot during troubl
Image

CONSIDERATIONS FOR JOURNEY BUILDER

 CONSIDERATIONS FOR JOURNEY BUILDER   WHAT HAPPENS WHEN YOU SEND AN EMAIL OUTBOUND MAIL MANAGEMENT GETS INVOKED BY MARKETING CLOUD , OMM IS NOT IN OUR CONTROL BUT LETS GO THROUGH BEHIND THE SCENE ACTIONS. 1. OOM PREPARES DATABASE FOR THE JOBS, OOM ANALYZES THE EMAIL, WHETHER IT'S A TEMPLATE BASED EMAIL OR HTML, WHETHER EMAILS CONTAINS PERSONALIZATIONS OR DYANMIC CONTNETS.  2.  OOM STRUCTURES THE EMAIL BASED ON HEADER , BODY AND FOOTER. OOM RETRIEVES THE SUBJECT LINE , BODY CONTENT , AMPSCRIPT IN THE EMAIL AND INTERPRETS THE AMPSCRIPT AND RETIRVES IMAGES. 3. BASED ON THE DATABASE AND STRUCUTRE MAINATAINED BY THE OOM, IT DETERMINES THE CONTENT FOR THE SUBSCRIBERS AND PROCESSES TO MAINTAIN THE PLACEHOLDERS FOR EACH SUBSCRIBERS. 4. OOM HAS PLACED THE PROCESSES IN THE QUEUE, OOM BUNDLES EMAILS IN 500 BATCHES AND SEND TO SUBSCRIBERS INBOX.  NOW WE HAVE THE BACKGROUD , WHAT ARE THE CONSIDERATIONS FOR BUILDING A JOURNEY  JOURNEY PERFORMANCE ARE BASED ON : 1. DATA MODEL 2. FILTERS  3. JOURN
Image

Journey Builder REST API Documentation

Journey Builder REST API Documentation Home Page Journey Builder REST API Documentation Introduction The Journey Builder REST API allows you to programmatically interact with the Journey Builder feature of Salesforce Marketing Cloud. With this API, you can create, update, and manage customer journeys, as well as perform various operations related to contacts and interactions within those journeys. This document provides detailed information on how to use the Journey Builder REST API to integrate and automate your marketing workflows. Base URL The base URL for accessing the Journey Builder REST API is:
Image

Preference Center Demystified

Preference Center Demistifier Home Page Preference Center Demystified Email preference centers can unlock a wealth of subscriber information if executed properly. Learn more about them to create the personalized email experiences that build loyalty and trust.
Image

SEND LOG EANBLEMENT

SEND LOG EANBLEMENT STEP BY STEP GUIDE HOW TO ENABLE SEND LOGGING IN SALESFORCE MARKETING CLOUD  STEP 1 : CREATE SEND LOG DATA EXTENSION Create a data extension for Send Log utilizing send log template. You can create similar Send log for SMS, Push etc.,             Default attributes for Send Log Add custom attributes to send log, custom attributes will increase you query optimization and troubleshooting If you have Google Analytics enabled you can add utm_campaign and utm_source attributes as well. Best Practice would be to archive send log on a monthly basis and set the retention policy to 6 months.  STEP 2 : CREATE CODE SNIPPET TO ADD CUSTOM ATRRIBUTES TO SEND LOG  Default send log attributes gets added to send log by default as it picks from system personalization string  Email personalization strings can be found in email tool bar: Profile and System Attribute   Create a code snippet  Write an AmpScript block to add custom attributes to Send Log data extension                   %

Share with Friends

Disclaimer:

The information provided on this technical blog is for general informational purposes only. As a SFMC (Salesforce Marketing Cloud) Technical Architect, I strive to offer accurate and up-to-date content related to SFMC and its associated technologies. However, please note that technology is constantly evolving, and the information provided may become outdated or inaccurate over time.

The content published on this blog represents my personal views and experiences as a SFMC Technical Architect and does not necessarily reflect the official views or opinions of any organization or employer I may be affiliated with.

While I make every effort to ensure the accuracy and reliability of the information presented, I cannot guarantee its completeness, suitability, or applicability to your specific circumstances. Therefore, it is essential to verify any information provided and make your own independent assessments or seek professional advice if needed.

Furthermore, any actions taken based on the information provided on this blog are at your own risk. I shall not be held liable for any damages, losses, or inconveniences arising from the use of the information presented here.

Please keep in mind that SFMC and its associated technologies are complex and require technical expertise for proper implementation and management. It is recommended to consult with qualified professionals or official SFMC documentation for comprehensive guidance.

Finally, please note that any product or company names mentioned on this blog are trademarks or registered trademarks of their respective owners. The mention of these trademarks or registered trademarks does not imply any endorsement or affiliation with the blog.

By accessing and using this blog, you agree to the terms of this disclaimer. If you do not agree with any part of this disclaimer, please refrain from using this blog.

Home Page