Introducing WS-Proxy Create Method in SFMC

Introducing WS-Proxy Create Method in SFMC
Home Page

Introducing WS-Proxy Create Method in SFMC:

Use Case

Description: This use case describes the process of creating data views data extensions in Salesforce Marketing Cloud using the "Data View AMP Scriptify" custom app from the AppExchange. This app provides enhanced capabilities for data extension creation and management.

Actors:

  • Marketers: The user with administrative privileges responsible for managing data extensions and data views in Marketing Cloud.

Preconditions:

  • The Marketers has installed the "Data View AMP Scriptify" custom app from the AppExchange.
  • The Marketers has the necessary permissions to create data extensions.
  • The Marketing Cloud account is set up and accessible.

Main Flow:

  1. The Marketers logs in to the Marketing Cloud account.
  2. The Admin navigates to the "AppExchange" tab in the Marketing Cloud dashboard.
  3. The Marketing Cloud displays a list of installed custom apps, including "Data View AMP Scriptify."
  4. The Admin selects the "Data View AMP Scriptify" custom app from the list.
  5. The custom app interface loads, providing advanced data extension management options.
  6. Within the "Data View AMP Scriptify" app, the Admin selects the checkboxes for the data views they want to create. These checkboxes represent predefined data views that come with the app and offer specific functionalities or data configurations.
  7. The app may provide additional options or settings related to the selected data views, which the Admin can configure as needed.
  8. The Admin clicks on the "Create New Data Extension" button within the app after selecting the desired data views.
  9. The app prompts the Admin to provide the following information for the new data extension:
    • Data Extension Name: A unique and descriptive name for the data extension.
    • External Key: An optional external key for easy reference and integration purposes.
    • Fields: Defines the fields/columns to be included in the data extension, along with their data types and attributes.
    • Data Retention Policy: Specifies how long the data in the data extension should be retained.
    • Primary Key: Specifies the primary key field that uniquely identifies each record in the data extension.
    • Data Extension Type: Selects the appropriate data extension type, such as Standard or Filtered.
    • Sharing Settings: Determines the sharing permissions for the data extension.
  10. The Admin reviews the provided information and ensures the accuracy of the data extension configuration.
  11. The Admin clicks on the "Create Data Extension" button within the app to create the data extension.
  12. The "Data View AMP Scriptify" app validates the data extension configuration and communicates with Marketing Cloud to create the new data extension with the specified settings, including the selected data views.

Postconditions:

  • The Marketers successfully creates the new data extension using the "Data View AMP Scriptify" custom app, including the selected data views.
  • The data extension, along with the associated data views, is now available for use in various Marketing Cloud functionalities, such as data import, segmentation, and automation activities.

Note: This use case provides an overview of the process to create data views data extensions in Salesforce Marketing Cloud using the "Data View AMP Scriptify" custom app from the AppExchange. The actual steps and configuration options may vary depending on the specific version and setup of the custom app. It is essential to refer to the official documentation and user guides for accurate and up-to-date instructions.

Solution Documentation

This solution documentation outlines the process of creating data views data extensions in Salesforce Marketing Cloud using the "Data View AMP Scriptify" custom app from the AppExchange. The "Data View AMP Scriptify" app provides advanced data extension management capabilities, including the ability to select predefined data views for enhanced functionalities.

Prerequisites

  • A Salesforce Marketing Cloud account with administrative privileges.
  • Installation of the "Data View AMP Scriptify" custom app from the AppExchange.

Step-by-Step Guide

  1. Log in to Salesforce Marketing Cloud

    2. Ensure that you have the necessary login credentials to access the Marketing Cloud account.

  2. Access the AppExchange Tab

    3. Once logged in, navigate to the "AppExchange" tab in the Marketing Cloud dashboard.

  3. Find "Data View AMP Scriptify" App

    4. In the AppExchange tab, you will see a list of installed custom apps. Locate and select the "Data View AMP Scriptify" custom app from the list.

  4. Launch "Data View AMP Scriptify" App

    5. Click on the "Data View AMP Scriptify" app to launch its interface, which provides advanced data extension management options.

  5. Select Data Views to Create

    6. Within the "Data View AMP Scriptify" app, you will find a list of available data views represented by checkboxes. Select the checkboxes corresponding to the data views you wish to create. Each data view offers specific functionalities or data configurations.

  6. Configure Additional Options (Optional)

    7. The "Data View AMP Scriptify" app may provide additional options or settings related to the selected data views. You can configure these options as needed for your data extension.

  7. Initiate Data Extension Creation

    8. After selecting the desired data views and configuring additional options, click on the "Create New Data Extension" button within the app.

  8. Provide Data Extension Details

    9. The app will prompt you to provide the following information for the new data extension:

    • Data Extension Name: Enter a unique and descriptive name for the data extension.
    • External Key (Optional): Define an external key for easy reference and integration purposes.
    • Fields: Specify the fields/columns to be included in the data extension, along with their data types and attributes.
    • Data Retention Policy: Set the data retention period for the data extension.
    • Primary Key: Specify the primary key field that uniquely identifies each record in the data extension.
    • Data Extension Type: Select the appropriate data extension type, such as Standard or Filtered.
    • Sharing Settings: Determine the sharing permissions for the data extension.
  9. Review Configuration and Confirm

    10. Carefully review the provided information to ensure the accuracy of the data extension configuration.

  10. Create Data Extension

    11. Click on the "Create Data Extension" button within the app to initiate the data extension creation process.

  11. Validation and Communication with Marketing Cloud

    12. The "Data View AMP Scriptify" app will validate the data extension configuration and communicate with Marketing Cloud to create the new data extension with the specified settings, including the selected data views.

Post-creation Steps

  • After successfully creating the data extension, it will be available for use in various Marketing Cloud functionalities, such as data import, segmentation, and automation activities.
  • Ensure to keep track of the created data extensions and their associated data views for future reference and maintenance.

Technical know-how

Introduction:

Salesforce Marketing Cloud is a robust platform that empowers businesses to engage with customers on a personalized level, deliver targeted messages, and drive successful marketing campaigns. To maintain a competitive edge in today's fast-paced digital landscape, real-time data integration becomes crucial. The WebSocket Proxy (ws-proxy) Create Method is a powerful feature introduced in Salesforce Marketing Cloud, providing developers with the ability to seamlessly integrate real-time data from external sources into their Marketing Cloud journeys. In this blog, we will explore the key functionalities of the createItem and createBatch methods, and how they can revolutionize your marketing efforts.

Understanding WebSocket Proxy:

The WebSocket Proxy (ws-proxy) is a technology that facilitates bidirectional communication channels between a client and a server. This enables the seamless exchange of data in real-time without the need for traditional HTTP polling mechanisms. With the introduction of the ws-proxy create method, Salesforce Marketing Cloud now offers an efficient and scalable way to connect with external systems and synchronize data seamlessly.

1. createItem Method:

The createItem method is designed to handle individual data items and is ideal for scenarios where you need to send real-time updates or events to Marketing Cloud. This could include events like abandoned carts, lead conversions, user interactions, or any other critical data point that you want to leverage for immediate customer engagement.

The process for using the createItem method involves:

  1. Establishing a WebSocket connection: Your external system initiates a WebSocket connection with the Marketing Cloud server using a secure endpoint.
  2. Sending data as JSON: Once the connection is established, you can send individual data items to the Marketing Cloud server in JSON format. The data should follow the structure defined in your Marketing Cloud data extension.
  3. Real-time updates: As soon as the data item is received and processed by Marketing Cloud, it can trigger immediate actions in your marketing journeys, such as sending personalized emails, updating subscriber preferences, or triggering automation rules.

The createItem method is especially useful for capturing time-sensitive events, ensuring your customer engagement remains timely and relevant.

2. createBatch Method:

While the createItem method handles individual data items, the createBatch method allows you to send multiple data items in a single payload. This is advantageous when you want to synchronize large datasets or perform bulk updates within Marketing Cloud. The createBatch method streamlines the data transfer process, reducing the number of WebSocket connections required and improving overall performance.

The steps for using the createBatch method include:

  1. Bundling data into batches: Before initiating the WebSocket connection, you package multiple data items into a JSON array, creating a batch of data that requires synchronization with Marketing Cloud.
  2. Submitting the batch: Once the WebSocket connection is established, you send the batch of data to the Marketing Cloud server, where it is processed efficiently.
  3. Optimizing data sync: By sending data in batches, you can significantly reduce the overhead associated with establishing multiple connections, resulting in a more streamlined and responsive integration.

3. Data Flow Diagram

3. HTML Form for Cloud Page


                
  <form action="%%=RequestParameter('PAGEURL')=%%"  method="post" class="needs-validation" >
          <div class="mb-3">
            <label><strong>Create:</strong></label>
            <br>
            <div class="form-check">
              <input type="checkbox" id="sentDataView" name="sentDataView" value="sentDataView"
                     class="form-check-input" aria-describedby="invalidCheck3Feedback" required>
              <label for="sentDataView" class="form-check-label">Sent</label>
            </div>
            <div class="form-check">
              <input type="checkbox" id="openDataView" name="openDataView" value="openDataView"
                     class="form-check-input">
              <label for="openDataView" class="form-check-label">Open</label>
            </div>
            <div class="form-check">
              <input type="checkbox" id="clickDataView" name="clickDataView" value="clickDataView"
                     class="form-check-input">
              <label for="clickDataView" class="form-check-label">Click</label>
            </div>
            <div class="form-check">
              <input type="checkbox" id="bounceDataView" name="bounceDataView" value="bounceDataView"
                     class="form-check-input">
              <label for="bounceDataView" class="form-check-label">Bounce</label>
            </div>
            <!-- Add more checkboxes for additional data views as needed -->
          </div>
          <button type="submit" class="btn btn-outline-success">Submit</button>
        </form>

4. Create a Folder via WS-Proxy


 function CreateAfolder(name,customerkey,description,parentFolderCategoryID){
    // Create a new instance of WSProxy to interact with the SOAP object.
    var api = new Script.Util.WSProxy();

    var newFolder = {
      "Name" : name,
      "CustomerKey" : customerkey,
      "Description" : description,
      "ContentType" : "dataextension",
      "IsActive" : "true",
      "IsEditable" : "true",
      "AllowChildren" : "true",
      "ParentFolder": {"ID":parentFolderCategoryID}
    };
    
    var status = api.createItem("DataFolder", newFolder);
    return status;
  }

5. Data Views Configurations


function CreateSentDataViews(CategoryID)
  {
       var deObj = {
        "CustomerKey" : "Dataview_Sent",
        "Name" : "Dataview_Sent",
        "CategoryID":CategoryID,
        "Fields" : [
          { "Name" : "AccountID", "FieldType" : "Number" },
          { "Name" : "OYBAccountID", "FieldType" : "Number"},
          { "Name" : "JobID", "FieldType" : "Number" },
          { "Name" : "ListID", "FieldType" : "Number" },
          { "Name" : "BatchID", "FieldType" : "Number" },
          { "Name" : "SubscriberID", "FieldType" : "Number" },
          { "Name" : "SubscriberKey", "FieldType" : "Text", "MaxLength" : 254 },
          { "Name" : "EventDate", "FieldType" : "Date"},
          { "Name" : "Domain", "FieldType" : "Text","MaxLength" : 128},
          { "Name" : "TriggererSendDefinitionObjectID", "FieldType" : "Text","MaxLength" : 36},
          { "Name" : "TriggeredSendCustomerKey", "FieldType" : "Text","MaxLength" : 36}
        ]
    };

    return deObj;
  }

  function CreateOpenDataViews(CategoryID)
  {
       var deObj = {
        "CustomerKey" : "Dataview_Open",
        "Name" : "Dataview_Open",
        "CategoryID":CategoryID,
        "Fields" : [
          { "Name" : "AccountID", "FieldType" : "Number" },
          { "Name" : "OYBAccountID", "FieldType" : "Number"},
          { "Name" : "JobID", "FieldType" : "Number" },
          { "Name" : "ListID", "FieldType" : "Number" },
          { "Name" : "BatchID", "FieldType" : "Number" },
          { "Name" : "SubscriberID", "FieldType" : "Number" },
          { "Name" : "SubscriberKey", "FieldType" : "Text", "MaxLength" : 254 },
          { "Name" : "EventDate", "FieldType" : "Date"},
          { "Name" : "Domain", "FieldType" : "Text","MaxLength" : 128},
          { "Name" : "TriggererSendDefinitionObjectID", "FieldType" : "Text","MaxLength" : 36},
          { "Name" : "TriggeredSendCustomerKey", "FieldType" : "Text","MaxLength" : 36},
          { "Name" : "IsUnique", "FieldType" : "Boolean"}
        ]
    };

    return deObj;
  }


  function CreateClickDataViews(CategoryID)
  {
       var deObj = {
        "CustomerKey" : "Dataview_Click",
        "Name" : "Dataview_Click",
        "CategoryID":CategoryID,
        "Fields" : [
          { "Name" : "AccountID", "FieldType" : "Number" },
          { "Name" : "OYBAccountID", "FieldType" : "Number"},
          { "Name" : "JobID", "FieldType" : "Number" },
          { "Name" : "ListID", "FieldType" : "Number" },
          { "Name" : "BatchID", "FieldType" : "Number" },
          { "Name" : "SubscriberID", "FieldType" : "Number" },
          { "Name" : "SubscriberKey", "FieldType" : "Text", "MaxLength" : 254 },
          { "Name" : "EventDate", "FieldType" : "Date"},
          { "Name" : "Domain", "FieldType" : "Text","MaxLength" : 128},
          { "Name" : "TriggererSendDefinitionObjectID", "FieldType" : "Text","MaxLength" : 36},
          { "Name" : "TriggeredSendCustomerKey", "FieldType" : "Text","MaxLength" : 36},
          { "Name" : "IsUnique", "FieldType" : "Boolean"},
          { "Name" : "URL", "FieldType" : "Text","MaxLength" : 900},
          { "Name" : "LinkName", "FieldType" : "Text","MaxLength" : 1024},
          { "Name" : "LinkContent", "FieldType" : "Text"}
        ]
    };

    return deObj;
  }
  
  function CreateBounceDataViews(CategoryID)
  {
       var deObj = {
        "CustomerKey" : "Dataview_Bounce",
        "Name" : "Dataview_Bounce",
        "CategoryID":CategoryID,
        "Fields" : [
          { "Name" : "AccountID", "FieldType" : "Number" },
          { "Name" : "OYBAccountID", "FieldType" : "Number"},
          { "Name" : "JobID", "FieldType" : "Number" },
          { "Name" : "ListID", "FieldType" : "Number" },
          { "Name" : "BatchID", "FieldType" : "Number" },
          { "Name" : "SubscriberID", "FieldType" : "Number" },
          { "Name" : "SubscriberKey", "FieldType" : "Text", "MaxLength" : 254 },
          { "Name" : "EventDate", "FieldType" : "Date"},
          { "Name" : "Domain", "FieldType" : "Text","MaxLength" : 128},
          { "Name" : "TriggererSendDefinitionObjectID", "FieldType" : "Text","MaxLength" : 36},
          { "Name" : "TriggeredSendCustomerKey", "FieldType" : "Text","MaxLength" : 36},
          { "Name" : "IsUnique", "FieldType" : "Boolean"},
          { "Name" : "BounceCategoryID", "FieldType" : "Number" },
          { "Name" : "BounceCategory", "FieldType" : "Text","MaxLength" : 50},
          { "Name" : "BounceSubcategoryID", "FieldType" : "Number" },
          { "Name" : "BounceSubcategory", "FieldType" : "Text","MaxLength" : 50},
          { "Name" : "BounceTypeID", "FieldType" : "Number" },
          { "Name" : "BounceType", "FieldType" : "Text","MaxLength" : 50},
          { "Name" : "SMTPBounceReason", "FieldType" : "Text"},
          { "Name" : "SMTPMessage", "FieldType" : "Text"},
          { "Name" : "SMTPCode", "FieldType" : "Number" },
          { "Name" : "IsFalseBounce", "FieldType" : "Boolean"}
        ]
    };

    return deObj;
  }

6. WS-Proxy CreateBatch Method


 function CreateDataViews(dataViews){
    var api = new Script.Util.WSProxy();
    var response = api.createBatch("DataExtension", dataViews);
    return response;
  }

7. Main Function


<script runat="server">
      Platform.Load("core", "1");
      var method=Platform.Request.Method;
      try {
      if (method=="POST"){
        Variable.SetValue("@method","POST");
        var isSentDataView=Variable.GetValue("@sentDataView");
        var isOpenDataView=Variable.GetValue("@openDataView");
        var isClickDataView=Variable.GetValue("@clickDataView");
        var isBounceDataView=Variable.GetValue("@bounceDataView");

        var categoryID=RetrieveFolderID("Data Views");
        if (!categoryID){
        var parentFolderCategoryID=RetrieveFolderID("Data Extensions");
        var createDataFolder=CreateAfolder("Data Views","Data Views","Data Views",parentFolderCategoryID)
        categoryID=createDataFolder.Results[0].NewID;
        }

        var dataViews=[];
        if(isSentDataView)
        {
            var sentDataView=CreateSentDataViews(categoryID);
            dataViews.push(sentDataView);

        }
        if(isOpenDataView)
        {
            var openDataView=CreateOpenDataViews(categoryID);
            dataViews.push(openDataView);

        }
        if(isClickDataView)
        {
            var clickDataView=CreateClickDataViews(categoryID);
            dataViews.push(clickDataView);

        }
        if(isBounceDataView)
        {
            var bounceDataView=CreateBounceDataViews(categoryID);
            dataViews.push(bounceDataView);

        }
        
        var response=CreateDataViews(dataViews);
        var status=response.Status;
        var requestID=response.RequestID;
        var result= {"Status": status, "RequestID": requestID};
        var output=Stringify(result);
        Variable.SetValue("@status",status);
        Variable.SetValue("@result",output);
      }
      else{
        Variable.SetValue("@method","GET");
      }
    }
    catch (ex) {
  // If an exception occurs during the execution, catch it and write the error messages to the output.
  Write(ex.message + '\n');
  Write(ex.description + '\n');
  Write(ex.jintException + '\n');
}
</script>

Conclusion:

The WebSocket Proxy (ws-proxy) Create Method in Salesforce Marketing Cloud opens up a world of possibilities for real-time data integration. By using the createItem and createBatch methods, businesses can maintain an up-to-date view of customer interactions and rapidly respond with personalized marketing efforts. This enables marketers to deliver targeted messages, drive engagement, and boost customer loyalty.

In the dynamic landscape of modern marketing, leveraging real-time data integration has become a necessity. With the ws-proxy create method, Salesforce Marketing Cloud empowers businesses to stay ahead of the competition and forge stronger connections with their customers.

TOP


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