Block Automations

Automation is a process of taking basic tasks and automating them with minimal human intervention. In Jomablue, Block Automation allows users to configure automatic actions that occur when Community users interact with Blocks in Community. To effectively use this feature, it’s important to understand the associated terms defined below:

• Interaction - This refers to the data recorded when a person interacts with a Block. For example, when a user clicks on a File Block to download a file, the recorded interaction is  labelled as ‘download_started.’
• Automation - This is an instruction for Jomablue to do something when an interaction has been recorded. For example, if this happens, then implement X
• Action - This is the result of the Automation. For example, add a custom field to a person’s record, trigger a campaign, mark a Person as having attended a Session.

Benefits of using Block Automation

Block Automations offer several benefits to Jomablue users, including:

• Simplified post-event reporting, as interaction data associated with automated Blocks will be included in a People Export
• Improvement of data quality
• Reduced risks of human errors in reporting
• Ability to send intelligent, targeted email or SMS campaigns based on a Community User’s interaction

Features of Block Automation

Key Features of Block Automation include:

• Multiple Automation can be applied to a single Block
• Once created, an Automation cannot be deleted
• Any Block with an enabled Automation cannot be deleted, even if no recorded interaction data exists

Below is a visual example showcasing multiple Automations applied to a Block:

Set up Block Automation

Before setting up Automations in a Block, you need to determine the Automation required:

1. Determine the Automation Required
   
   Identify the interaction and action you wish to automate. Each Block in Community has its own set of unique interactions that can be linked to your selected action. There are three actions available for each Block:
   
   

   Available Actions	Description
   Add Person Custom Field	Adds a custom field to a person. The Custom field Key and Value can be specified or dynamic values can be applied (e.g., the Vimeo video URL or the file name)
   Fire Custom Campaign Trigger	Creates a selectable trigger for campaign building, allowing instant sending of a campaign to a person based on their interaction with a Block
   Session Attended	This allows any Block Interaction to mark a Person as having attended a Session based on their interaction with a Block

2. Navigate to the Canvas Builder or Block Editor to Create Automation
   
   Block Automation setup can be accessed via:
   
      a. Clicking the Automation tab when editing a Block in the Block Editor
      b. Directly from the Canvas Builder by clicking the lightning bolt icon displayed on the Block
   
3. Define the Automation
   
      a. Click on Add Automation
      b. Choose the Interaction you wish to Automate
      c. Select the Action you wish to link to the above Interaction
   
   The following example shows the Automation of whenever a person starts playing a video, a custom field is added to the person record.
   
   
      d. Click Next
4. Configure the Action
   
   Once linked, the next step is to configure the action. This is achieved by following these steps:
   
      a. Configure the key of the custom field that will be added to the person record. The Custom Field Key is the name of the field in the Custom Field. For example, the custom field key could be linked to the Video URL
      b. Configure the value of the custom field that will be added to the person record. The Custom Field Value is the variable data within that field. For example, the custom field value could be linked to the total Video duration.
      c. Press Save and the Automation is created

Note: You can delete the automation by clicking the Delete button located in the top right corner while editing the automation, as shown below:

‘Add Custom Field to Person’ Block Automation Action

The ‘Add a custom field to a Person’ is a Block Automation Action that enables any Block Interaction to add a custom field to the Person. This Block Automation Action provides several usages such as:

• It allows users to decide which interactions are important to them and make that data available in People records and a People export
• Custom fields can be applied in campaigns. (e.g., send a campaign to people who have reached the end of a VOD or identify those who didn't watch a live stream).
• It saves time in building reports from scratch

Key & Value Pair

TA Custom field comprises of a Key & Value. A key-value pair is two pieces of data associated with each other. The Key serves as a unique identifier that points to its associated value, which is either the data being identified or a pointer to that data. For example:

• Key: The Custom Field Key is the name of the field in the Custom Field  (e.g., Keynote Livestream)
• Value: The Custom field value is the variable data within that field (e.g., watched stream)

Configure the ‘Session Attended’ Action

1. When configuring Block Automation, select the interaction you wish to link with the ‘Add Custom field to the Person’ action. For example, when configuring Automation for a File Download Block, we can link ‘Download Button Clicked’ to ‘Add Custom Field to Person’
   ​
2. The next step is to configure the action by defining Custom Field Key and Value. For example, we set the Filename as the Custom Field Key and static text (Downloaded) as the Custom Field Value.
   

Now, whenever an attendee clicks on the File to download, this will be added to the person record, indicating that the attendee has downloaded the file. This can be viewed in the People Export file.

​Note: You do not need to define the Custom Field in custom fields once you set up the automation. It is only required if you want the Custom Field to be editable in the person record.

‘Session Attended’ Block Automation Action

‘Session Attended’ is a Block Automation Action that allows any Block Interaction to mark a Person as having attended a Session. Here are some examples of interactions where the ‘Session Attended’ Action is applicable:

• Clicking play on a Live Stream
• Watching past a certain threshold on a VOD (customisable)
• Clicking on a Lead Capture Block
• Downloading a file

Configure the ‘Session Attended’ Action

1. When configuring Block Automation, select the interaction to link with the ‘Mark Person as having attended Session’ action. For example, the interaction ‘Video reached end’ is linked to the ‘mark the person as having attended a session’.
   
2. Next, you must select the session you wish to mark as the person having attended.
   ​​
   

Note: If the Block you are configuring is on a Session Canvas, it will automatically fill in the corresponding Session. You have the option to change the Session if required.