4. Configure Status updates and Tokens

Overview

This step enables you to configure Marketo Program member status updates, and manage program custom tokens (My Tokens). Read more about Marketo Program member status here, and custom tokens here. This is an optional step.

Prerequisites:

• Access to Marketo with a Program created.  
• Access to Hubilo organizer dashboard, and connected a Marketo Program to a Hubilo webinar/event. See how.

Step-1: Configure Program Member Status

There are four Hubilo triggers available which can be mapped with relevant Program member status:

1. When a registration is added to Hubilo event: This will be triggered when a successful registration is added to Hubilo from the connected program. Use this trigger to update program member status to(say) ‘Registered’. 
2. When a registrant attends a Hubilo event: This will be triggered when a registrant logs-in to a webinar/virtual event or checks-in to an in-person event. Use this trigger to update program member status to(say) ‘Attended’ or ‘Attended Virtually’ or ‘Attended in-person’, etc.
3. When an event/webinar ends: This will be triggered approximately 30 minutes after the event/webinar ends for all who didn’t attend the event. Use this trigger to update program member status to(say) ‘No-Show’.
4. When a registrant attends an on-demand event/webinar: This will be triggered when a registrant logs-in to a webinar/virtual event after the event ends. Use this trigger to update program member status to(say) ‘Attended On-demand’.   
   
   

The status dropdown on the right will be populated automatically from your Marketo Program by fetching all the program member statuses that you’ve configured.

Note: Please note that Marketo doesn’t allow users to move backwards to an earlier program status. Status progression is one way only. Mapping a backward status with a future trigger will result in sync failures. You can also set one or more statuses as a success criteria for your program. See more details here.

Once the status mapping is done successfully, and the data sync is turned on after all steps are completed, Hubilo will automatically update the Program member status for all members in Marketo. 

Step-2: Configure custom Program Tokens (My Tokens)

Tokens in Marketo serve as variables that store static information, enabling marketers to create generic templates for emails, landing pages, and more, as they get resolved to their respective values.

You will need to create custom tokens in Marketo first, and then be able to set up the mapping of the tokens with Hubilo data values. See how.

Hubilo provides a list of values that can be mapped with custom tokens in Marketo. Once all the steps are completed and the sync is enabled, the token values in Marketo will be automatically updated. 

For example, if there’s a token created in Marketo, named ‘{my.Event Name}’ and it’s mapped with ‘Event Name’ under Hubilo dropdown, then the token value in Marketo will be replaced with the actual Hubilo event name. 

Also, whenever the event name is updated in Hubilo, the token value will also get automatically updated in Marketo.




Note: While mapping make sure that the data type of a token matches the data type of the corresponding Hubilo data values, or otherwise the sync might fail. Please refer to the table below for data types.

*Timezone will be the same as that of Hubilo event. If your Marketo instance is set to a different timezone, the date/time may get converted by Marketo to that timezone.

Once done, click on Save and Continue to move ahead in the setup.