A Deep Dive into Real-Time Tracking Of Automation Status In SFMC

Introduction:

Effectively monitoring the status of automations in Salesforce is crucial for ensuring seamless operations. In this blog post, we delve into an advanced approach to automation monitoring logic, providing detailed insights on how to track automations using Salesforce Marketing Cloud's API objects: Automation and AutomationInstance.

Understanding the Challenges:

Before we explore the solution, it's essential to acknowledge the challenges associated with traditional monitoring methods. The advanced audit trail log, while informative, fails to log the name of the automation in the message column, as discussed in this Salesforce article https://help.salesforce.com/s/articleView?id=sf.mc_rn_october_2020_setup_new_audit_trail_activites.htm&type=5.

Additionally, relying on data views (https://help.salesforce.com/s/articleView?id=sf.mc_as_data_view_automation_instance.htm&type=5) requires waiting 24-48 hours to access the necessary details.

The Solution: Leveraging API Objects

To overcome these challenges, we recommend utilizing the API objects Automation and AutomationInstance along with the provided Server-Side JavaScript (SSJS) script.

Sample SSJS Script:

<script runat="server"> Platform.Load("Core", "1.1.1"); var output = ""; var i; var dataRows = Platform.Function.LookupRows('<Data_Extension_Name>', 'Flag', 'True'); if (dataRows && dataRows.length > 0) { for (i = 0; i < dataRows.length; i++) { // Retrieving automation details var automationCustomerKey = dataRows[i]["Customer_Key"]; var rr = Platform.Function.CreateObject("RetrieveRequest"); // Adding properties to retrieve // ... // Applying a filter based on CustomerKey // ... // Invoking retrieve and processing results var retrieveStatus = [0, 0, 0]; var automationResultSet = Platform.Function.InvokeRetrieve(rr, retrieveStatus); // Extracting relevant automation details // ... // Mapping numeric status to human-readable labels var Print = mapStatusToLabel(Status); // Updating monitoring list with the latest details var updateResults = Platform.Function.UpsertData("<Data_Extension_Name>", ["Customer_Key"], [automationCustomerKey], ["Automation_Name", "Status", "ScheduledTime", "AutomationID", "AutomationType", "CompletedTime", "CreatedDate", "ModifiedDate", "StartTime", "StatusLastUpdate", "StatusMessage"], [Name, Print, ScheduledTime, AutomationID, AutomationType, CompletedTime, CreatedDate, ModifiedDate, StartTime, StatusLastUpdate, StatusMessage]); } Write("<br>" + output); } </script>


Conclusion:

By incorporating the above SSJS scripts and leveraging the Automation and AutomationInstance API objects, you can enhance your automation monitoring capabilities. This detailed guide provides a comprehensive solution to efficiently track and manage automation statuses in Salesforce Marketing Cloud.

Comments

Post a Comment

Popular posts from this blog

SQL Query Activity Hack

In Salesforce Marketing Cloud (SFMC), we often use SQL Queries to manipulate data in our campaigns. Typically, when we're working with the same source and target data extensions, we know that SQL Queries can either update existing records or append new ones. However, did you know that there's another option? In this scenario, if we define the source data extension within double quotes in the SQL Query, we can perform an overwrite data action. This means we have the ability to replace existing data in the target data extension with the new data from the source. It's a handy trick that adds flexibility to how we handle data in SFMC, allowing for more precise control over the outcome of our SQL Queries. Sample Example: SELECT<Column_names> FROM " [Data Extension ABC] " WHERE <Condition> DATA Action : Overwrite Source Data Extension  :  [Data Extension ABC]
Read more

Mobile Push Configuration In Journey Builder

When you're using Salesforce Marketing Cloud's Journey Builder to send out Push messages, there's an important thing to keep in mind. You want to avoid sending these messages to devices that haven't agreed to receive them. Surprisingly, Journey Builder doesn't have a built-in way to stop this from happening. So, to make sure your Push messages only go to opted-in devices, you need to add a specific code, called AMPscript, into the message content. This AMPscript acts like a safety net, making sure your Push messages only go to devices that have said "yes" to getting them. This extra step is crucial because it helps you follow good communication practices and avoid sending messages to people who haven't given their permission. In simpler terms, by adding below bit of code, you're making sure your messages respect people's choices about what they want to receive. Since Journey Builder doesn't automatically do this for Push messages, using AMP...
Read more

One Click Unsubscribe & Hard Bounce Automation Solution

  CONTEXT: In February 2024, Google and Yahoo introduced updated email standards affecting two key areas.   Hard Email Bounces: Tightened restrictions on undeliverable emails significantly impact sender reputation and IP status in SFMC. Compliance with Google’s new standards mandates refraining from sending eDMs to email addresses receiving 'hard bounce' notifications.   One-Click Unsubscribe: When recipients opt to 'one-click unsubscribe' in Gmail or Yahoo, the action is recorded in SFMC's 'businessunitunsubscribe' table, halting further eDMs.       Customers stop receiving eDMs after this action is stored in SFMC, however, this data doesn't automatically sync back to Salesforce CRM Related links to this topic can be found below:  ·         https://help.salesforce.com/s/articleView?id=sf.mc_es_bulk_sender_guidelines.htm&type=5   · ...
Read more