the personal blog of adam spriggs
Tips for the technical side of Salesforce Marketing Cloud.
Sometimes it’s handy having a list of Content Builder Assets by folder in a Data Extension, especially for migrating Package Manager.
Before you add this Script Activity in Automation Studio, add your API creds and update the Category ID for your target Data Extension. You can also update the query criteria starting on line 91, if needed.
As always, let me know if you have any feedback in the comments below (or on Github).
I don’t know about you, but I’ve found monitoring crucial File Import Activities in SFMC a challenge. I think it’s important to ensure all of the rows in the file got imported or have some recourse to identify exceptions — outside of accessing the results file that gets dropped in the SFTP Import folder or relying on the import results email.
Here’s a script that retrieves and iterates through the ImportResultsSummary SOAP object data (via WSProxy) and writes it to a Data Extension of the same name.
NOTE: The
DestinationIDis either aListIDor theObjectIDof a Data Extension. If you’ve got an inventory ofDataExtensionSOAP object data, you can use something like this dataset to build a pretty comprehensive report on import exceptions.
I started setting proper Customer/External Keys on all Import Activities after using this data, just so ImportDefinitionCustomerKey is meaningful. One less thing to have to track down when troubleshooting.
Of course, I welcome any feedback y’all might have on this.
Audit Events are worthwhile to explore in Salesforce Marketing Cloud (SFMC) if you’re in a vertical that includes tighter roles and permissions. You can supplement your audit scheme by retrieving these Audit Events via REST and writing them to a Data Extension (DE).
First, you’ll need to enable the feature here: Email Studio > Admin > Security Settings > Enable Audit Trail Data Collection > Yes
After you’ve collected data for a few days, create a Script Activity like this and set it to run on the desired interval in an Automation.
You’ll need to add your target Data Extension’s Category ID, MID, REST API Tenant, Client Id and Client Secret.
With additional scrutiny on outbound links in corporate inboxes these days, one-click unsubscribe pages aren’t always a good idea — any visit from a click will result in an immediate action. In the case of a one-click unsubscribe page, it’s an opt-out.ย That’s no good.
Here’s an example of a two-click unsubscribe page that requires an additional click to confirm the subscriber’s desire to unsubscribe (or not).
As always, if you have any feedback, questions or find any issues with this, feel free to drop me note on the contact page or via comment down below.
I do love well though-out SFMC email architectures, especially ones that are modular. One of the drawbacks of using the AMPscript reference blocks for sharing content across email definitions is that, while the actual changes are done in only a few places, getting the actual send definitions updated requires an additional step — republishing. This goes for Journey emails, also.
Here’s a script that I wrote to automate pausing, publishing and starting Triggered Send Definitions (TSD) by folder. It’ll recursively traverse the folder structure if you have a bunch of nested folders. Results of the process are logged in a Data Extension. To get started, create a Data Extension with this schema:
Name: republish_trigger_log
External Key: republish_trigger_log
Here’s the script — just update line 10 with the parent folder’s Category ID.
This script starts at the CategoryID specified on line 10 and loops down through all of the child folders.
NOTE: You can find the Category ID by inspecting the URL at the bottom of your browser when you hover over the folder in SFMC.
When it encounters and “Active” Triggered Send Definition, it pauses, publishes and starts it. Results of those three actions are recorded in republish_trigger_log.
I recommend running this Script Activity in an unscheduled Automation.