SSJS Platform

SSJS Platform
Home Page

Server-Side JavaScript (SSJS) Platform Functions

Write an SSJS code block to get atrribute values 

<script runat="server">
  /*
   * Script Author: Shashi Prasad
   * Date: 10th Dec, 2024
   * Description: This script demonstrates the use of GetAttributeValue to retrieve values 
   * from different attributes or fields for a recipient in Marketing Cloud.
   */

  // GetAttributeValue: Returns the value from a specified attribute or sendable data extension field.

  // Profile attribute email address
  var contactEmail = Platform.Recipient.GetAttributeValue('EmailAddr');
  Platform.Response.Write("Contact Email: " + contactEmail + '<br/>');
  
  // Sendable data extension attribute
  var subscriberkey = Platform.Recipient.GetAttributeValue('UID');
  Platform.Response.Write("Subscriber Key: " + subscriberkey + '<br/>');
  
  // MID
  var memberId = Platform.Recipient.GetAttributeValue('memberid');
  Platform.Response.Write("Member ID: " + memberId + '<br/>');
  
  // BU Name
  var busName = Platform.Recipient.GetAttributeValue('Member_Busname');
  Platform.Response.Write("Business Name: " + busName + '<br/>');
  
  // Subscriber Key
  var subscriberKey = Platform.Recipient.GetAttributeValue('_subscriberkey');
  Platform.Response.Write("Subscriber Key: " + subscriberKey + '<br/>');
  
  // Job Id
  var jobId = Platform.Recipient.GetAttributeValue('jobid');
  Platform.Response.Write("Job ID: " + jobId + '<br/>');
</script>

Write an SSJS block to delete data from data extension 

<script runat="server">
  /*
   * Script Author: [Your Name]
   * Date: [Current Date]
   * Description: This script deletes rows from a specified Data Extension where the specified 
   * column values match the given criteria.
   */

  // Define the Data Extension name
  var deName = "Dataview_Bounce";

  // Define the column names and values to match for deletion
  var columnNames = ["SMTPCode"];
  var columnValues = [550];

  // Delete rows from the Data Extension
  var rows = Platform.Function.DeleteData(deName, columnNames, columnValues);

  // Output the result
  Platform.Response.Write("Rows Deleted: " + rows);
</script>

Write an SSJS block to insert data from data extension 

<script runat="server">
  /*
   * Script Author: [Your Name]
   * Date: [Current Date]
   * Description: This script inserts data into a specified Data Extension with the provided column names
   * and values.
   */

  // Define the Data Extension name
  var deName = "Dataview_Sent";

  // Define the column names and values for insertion
  var columnNames = ["JobID", "ListID", "BatchID", "SubscriberID", "SubscriberKey", "EventDate"];
  var columnValues = [12345, 12345, 12345, 1234567890, "shashi@gmail.com", "11/29/2023"];

  // Insert rows into the Data Extension
  var rows = Platform.Function.InsertData(deName, columnNames, columnValues);

  // Output the result
  Platform.Response.Write("Rows Inserted: " + rows);
</script>

Write an SSJS block to lookup a data extension 

<script runat="server">
  /*
   * Script Author: [Your Name]
   * Date: [Current Date]
   * Description: This script looks up a SubscriberKey in a specified Data Extension based on
   * the provided column names and values.
   */

  // Define the Data Extension name
  var deName = "Dataview_Bounce";

  // Define the column names and values for the lookup
  var columnNames = ["IsUnique", "BounceCategory"];
  var columnValues = [1, "Hard bounce"];

  // Lookup SubscriberKey in the Data Extension
  var subscriberKey = Platform.Function.Lookup(deName, 'SubscriberKey', columnNames, columnValues);

  // Output the result
  Platform.Response.Write("SubscriberKey: " + subscriberKey);
</script>

Write an SSJS block to Lookup rows by sorting a row in a data extension 

<script runat="server">
  /*
   * Script Author: [Your Name]
   * Date: [Current Date]
   * Description: This script looks up rows in a specified Data Extension based on
   * the provided column names and values.
   */

  // Define the Data Extension name
  var deName = "Dataview_Bounce";

  // Define the number of rows to return
  var numRows = 0; // Change this value as needed

  // Define the column and direction to sort by
  var sortOrder = 'SubscriberKey ASC'; // Change this value as needed

  // Define the column names for the lookup
  var columnNames = ["IsUnique", "BounceCategory"];

  // Define the values to look up in the specified columns
  var columnValues = [1, "Hard bounce"];

  // Lookup rows in the Data Extension
  var dataRows = Platform.Function.LookupOrderedRows(deName, numRows, sortOrder, columnNames, columnValues);

  // Output the result
  if(dataRows && dataRows.length > 0) {
    for(var i=0; i<dataRows.length; i++) {
      Platform.Response.Write("SubscriberKey: " + dataRows[i]["SubscriberKey"] +  "<br/>");
      Platform.Response.Write("EventDate: " + dataRows[i]["EventDate"] +  "<br/>");
      Platform.Response.Write("============================================= <br/>");
    }
  }
</script>

Write an SSJS block to Lookup rows in a data extension 

<script runat="server">
  /*
   * Script Author: [Your Name]
   * Date: [Current Date]
   * Description: This script looks up rows in a specified Data Extension based on
   * the provided column names and values.
   */

  // Define the Data Extension name
  var deName = "Dataview_Bounce";

  // Define the column names for the lookup
  var columnNames = ["IsUnique", "BounceCategory"];

  // Define the values to look up in the specified columns
  var columnValues = [1, "Hard bounce"];

  // Lookup rows in the Data Extension
  var dataRows = Platform.Function.LookupRows(deName,columnNames,columnValues);

  // Output the result
  if(dataRows && dataRows.length > 0) {
    for(var i=0; i<dataRows.length; i++) {
      Platform.Response.Write("SubscriberKey: " + dataRows[i]["SubscriberKey"] +  "<br/>");
      Platform.Response.Write("EventDate: " + dataRows[i]["EventDate"] +  "<br/>");
      Platform.Response.Write("============================================= <br/>");
    }
  }
</script>

Write an SSJS block to update data into a data extension 

<script runat="server">
  /*
   * Script Author: [Your Name]
   * Date: [Current Date]
   * Description: This script updates rows in a specified Data Extension based on
   * the provided column filter names and values.
   */

  // Define the Data Extension name
  var deName = "Dataview_Bounce";

  // Define the column names and values for the filter
  var columnFilterNames = ["IsUnique", "BounceCategory"];
  var columnFilterValues = [1, "Hard bounce"];

  // Define the column names and values for the update
  var columnUpdateNames = ["JobID", "ListID"];
  var columnUpdateValues = [12345, 12345];

  // Update rows in the Data Extension
  var rowsUpdated = Platform.Function.UpdateData(deName,columnFilterNames, columnFilterValues,columnUpdateNames, columnUpdateValues);

  // Output the result
  Platform.Response.Write("Rows Updated: " + rowsUpdated);
</script>

Write an SSJS block to upsert data into a data extension 

<script runat="server">
  /*
   * Script Author: [Your Name]
   * Date: [Current Date]
   * Description: This script updates rows in a specified Data Extension based on
   * the provided column filter names and values.
   */

  // Define the Data Extension name
  var deName = "Dataview_Bounce";

  // Define the column names and values for the filter
  var columnFilterNames = ["IsUnique", "BounceCategory"];
  var columnFilterValues = [1, "Hard bounce"];

  // Define the column names and values for the update
  var columnUpdateNames = ["JobID", "ListID"];
  var columnUpdateValues = [12345, 12345];

  // Update rows in the Data Extension
  var rowsUpdated = Platform.Function.UpsertData(deName,columnFilterNames, columnFilterValues,columnUpdateNames, columnUpdateValues);

  // Output the result
  Platform.Response.Write("Rows Updated: " + rowsUpdated);
</script>

Write an SSJS block for date and time function 

<script runat="server">
  /*
   * Script Author: [Your Name]
   * Date: [Current Date]
   * Description: This script demonstrates the usage of Now, SystemDateToLocalDate, and LocalDateToSystemDate functions.
   */

   // Get the current system time
   var time = new Date();

   // Convert system time to local time
   var localTime = Platform.Function.SystemDateToLocalDate(time);

   // Convert local time back to system time
   var systemTime = Platform.Function.LocalDateToSystemDate(time);

  // Output the result
  Platform.Response.Write("Time: " + time + "\n");
  Platform.Response.Write("Local Time: " + localTime + "\n");
  Platform.Response.Write("System Time: " + systemTime + "\n");
</script>

Write an SSJS block for Utility function 

<script runat="server">
  /*
   * Script Author: [Your Name]
   * Date: [Current Date]
   * Description: This script demonstrates the usage of Base64Encode, Base64Decode, GUID, IsEmailAddress, IsPhoneNumber, and MD5 functions.
   */

   // Define a normal string
   var normalStr = "Shashi";

   // Encode the string to Base64
   var encodedStr = Platform.Function.Base64Encode(normalStr);

   // Decode the Base64-encoded string
   var decodedStr = Platform.Function.Base64Decode(encodedStr);

   // Generate a random GUID
   var randomID = Platform.Function.GUID();

   // Check if the email address is valid
   var isEmailValid = Platform.Function.IsEmailAddress("shashi@example.com");

   // Check if the phone number is valid
   var isPhoneValid = Platform.Function.IsPhoneNumber("1234567890");

   // Calculate MD5 hash of the string
   var md5String = Platform.Function.MD5(normalStr, "UTF-8");

  // Output the result
  Platform.Response.Write("Normal String: " + normalStr + "\n");
  Platform.Response.Write("Encoded: " + encodedStr + "\n");
  Platform.Response.Write("Decoded: " + decodedStr + "\n");
  Platform.Response.Write("Random ID: " + randomID + "\n");
  Platform.Response.Write("Is Email Valid: " + isEmailValid + "\n");
  Platform.Response.Write("Is Phone Valid: " + isPhoneValid + "\n");
  Platform.Response.Write("MD5 Hash: " + md5String + "\n");
</script>

Write an SSJS block for ParseJSON function 

<script runat="server">

  // Load the Core library with version 1.1.1
  Platform.Load("Core", "1.1.1");

  // Your payload as a JSON string
  var payloadString = '[{"Prod_ID": 1, "Prod_Name": "Nike", "Prod_Desc": "Shoe"}, {"Prod_ID": 5, "Prod_Name": "Puma", "Prod_Desc": "Slipper"}, {"Prod_ID": 10, "Prod_Name": "Adidas", "Prod_Desc": "Jacket"}]';

  // Parse the JSON string
  var payload = Platform.Function.ParseJSON(payloadString);

  // Check if parsing was successful
  if (payload !== null) {

    // Iterate through the payload array
    for (var i = 0; i < payload.length; i++) {
      var product = payload[i];

      // Extract and print product details
      var productId = product.Prod_ID;
      var productName = product.Prod_Name;
      var productDescription = product.Prod_Desc;

      // Output the parsed values
      Platform.Response.Write("Product ID: " + productId + "<br>");
      Platform.Response.Write("Product Name: " + productName + "<br>");
      Platform.Response.Write("Product Description: " + productDescription + "<br>");
      Platform.Response.Write("-------------------------<br>");
    }

  } else {

    // Output message if parsing failed
    Platform.Response.Write("Failed to parse JSON.");

  }

</script>

Write an SSJS block for browser utility function 

<script runat="server">
  /*
   * Script Author: [Your Name]
   * Date: [Current Date]
   * Description: This script demonstrates the usage of various Platform.Request functions in Marketing Cloud scripting.
   */

   // Check if the request is made over SSL
   var IsSSL = Platform.Request.IsSSL;

   // Check if the request has SSL
   var HasSSL = Platform.Request.HasSSL;

   // Get the client's IP address
   var ClientIP = Platform.Request.ClientIP;

   // Get the request method (e.g., GET or POST)
   var Method = Platform.Request.Method;

   // Get the query string parameters
   var QueryString = Platform.Request.QueryString;

   // Get the referring URL
   var ReferrerURL = Platform.Request.ReferrerURL;

   // Get the current request URL
   var RequestURL = Platform.Request.RequestURL;

   // Get the user agent string
   var UserAgent = Platform.Request.UserAgent;

   // Get information about the browser
   var Browser = Platform.Request.Browser;

  // Output the result
  Platform.Response.Write("IsSSL: " + IsSSL + "\n");
  Platform.Response.Write("HasSSL: " + HasSSL + "\n");
  Platform.Response.Write("ClientIP: " + ClientIP + "\n");
  Platform.Response.Write("Method: " + Method + "\n");
  //Platform.Response.Write("QueryString: " + QueryString + "\n");
  //Platform.Response.Write("ReferrerURL: " + ReferrerURL + "\n");
 // Platform.Response.Write("RequestURL: " + RequestURL + "\n");
 // Platform.Response.Write("UserAgent: " + UserAgent + "\n");
 // Platform.Response.Write("Browser: " + Stringify(Browser) + "\n");
</script>

TOP


Comments

Post a Comment

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 %% = ...
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 M...
Image

Understanding Transactional Messaging

Understanding Transactional Messaging Home Page Understanding Transactional Messaging Transactional messaging refers to the process of sending automated messages to users in response to specific actions or events. These messages are typically triggered by user interactions or system events and are often personalized and time-sensitive. The primary goal of transactional messaging is to provide relevant and timely information to users based on their actions. Key Characteristics of Transactional Messaging Triggered by User Actions: Transactional messages are usually triggered by ...
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. ...

Knowledge Article

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 %% = ...
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 M...
Image

Understanding Transactional Messaging

Understanding Transactional Messaging Home Page Understanding Transactional Messaging Transactional messaging refers to the process of sending automated messages to users in response to specific actions or events. These messages are typically triggered by user interactions or system events and are often personalized and time-sensitive. The primary goal of transactional messaging is to provide relevant and timely information to users based on their actions. Key Characteristics of Transactional Messaging Triggered by User Actions: Transactional messages are usually triggered by ...
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

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

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