markus.codes

Yesterday I received a feature request via the chrome web store and today I added the requested improvements of the Journey Details feature as well as another improvement of the Expose Wait Activity Keys feature.

Feature Request

I received the following feature request via the chrome web store:

“Firstly, am so glad to have found this plug in! Thanks for developing it. At present you show the Wait activities, it would be great to do the same thing for other activities in Journey Builder to. I’m currently extracting the XHR data for Email Activities so that I can get the TriggerSendIds for each email so that I can use a single email and use dynamic content based on which email is being sent. Makes life a lot easier for Marketing to maintain the livery on a single email than multiple emails for each step. Many thanks, Spence”

So after reading this I improved the following features:

Journey Details

I added an overview of all activities of the current version including the id, the activity key, the type, the name and the triggeredSendId for email activities. This information is not only available in the interface, but also in JSON-format so it can be copy-pasted to an external system for further processing. The JSON-output looks like this:

{
  "activities": [
    {
      "id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
      "key": "WAIT-1",
      "type": "WAIT",
      "name": ""
    },
    {
      "id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
      "key": "EMAILV2-1",
      "type": "EMAILV2",
      "name": "Example email",
      "triggeredSendId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
    }
  ]
}

Enhance UI features - Expose Wait Activity Keys

I updated this feature to expose the activity keys of all other canvas activities present in the currently viewed journey version as well. Therefore I renamed the feature to “Expose Activity Keys”.

Contributing

This project is open source and I published the code of this Google Chrome Developertools extension to my github account so anyone can have a look at it or even improve the extension. If you like to add another feature, please feel free to open a pull request or raise an issue requesting the feature.

Repository: github.com/mslabina/sfmc-chrome-devtools