You may be saying to yourself “Hmm…I swear I just saw release notes from PathFactory a couple of weeks ago.” and if so you would be right. This is not a deja vu moment, this is not a drill!
Our team has been hard at work making improvements to our VEX module and important updates to our Marketo integration. With this in mind, we wanted to provide you with the details sooner rather than later so that you can begin taking advantage of this latest functionality.
Marketo API form submission exports to replace webhooks
On May 7th Marketo will be discontinuing support for server side submissions to the form endpoint commonly used for PathFactory webhooks. This will cause any existing webhooks which are passing data to Marketo to stop working. In order to support existing Marketo workflows moving forward, any existing webhook configurations will be converted to API Form Submission Exports. Moving forward, PathFactory will use the Marketo’s REST API to submit engagement data to your existing webhook form, and any workflows that you have currently set up will continue to work without any changes needed in Marketo.
API Form Submissions Reports list
If you already have an API integration set up between your instances of PathFactory and Marketo, we have already migrated your webhooks over to the new API method. You just need to turn them on in the Marketo section of your Organization Settings. If you are not already integrated, you will need to set up a new API connection to continue to take advantage of your PathFactory engagement data in Marketo.
Manage the components of your Marketo API integration individually
Administrators are now able to enable or disable individual components of our API integration with Marketo. This gives you more control over the number of API calls that PathFactory sends to Marketo, and allows you to take further advantage of some of our integration capabilities without worrying about exceeding your API limits in Marketo. The options available are:
- Munchkin Script for Campaign Tools and Virtual Events – When enabled, PathFactory automatically loads a customized version of the Marketo Munchkin script onto your Campaign Tools and Virtual Event pages. The script passes to content tag metadata to Marketo as query parameters on page views, and allows you to track threshold met activities. This option does rely on Marketo API calls.
- Cookie Identification – When enabled, PathFactory automatically attempts to identify visitors using their Marketo cookie. This process uses the Marketo REST API, and will consume your API quota.
- API Form Submission Exports – PathFactory will use Marketo’s REST API to write PathFactory engagement data through a Marketo form.
- Custom Object Exports – PathFactory will use the bulk API to create a new Marketo Custom Object containing all engagement within PathFactory where each row of data is an individual visitor session. Using a custom object allows us to store the complete history of leads’ engagement with PathFactory tracks against the lead record in Marketo.
Tag your sessions with relevant categorization
We have added the ability to tag your sessions with language, topic, persona, industry, business unit, and funnel stage information. This helps with organization of your sessions and will also allow your visitors to filter by these tags in the event landing page environment – more on that below!
Session tags appear within the Sessions tab of your VEX event. You can scroll left and right to see all available tags and you can sort and filter your sessions based on these different tags.
VEX Session tab
To add or edit tags to a session, click on the Edit tags button and a pop-up window will appear.
The list of values that are available for each tag type come from the content tag lists that your admins can set within the platform settings cog. The only exception to this is the language tag, which is based off of the options set in your language configurations list.
Languages menu item
Search and filter options available within VEX landing pages
If you have been eager for better session navigation within your VEX events, this update is for you! With the introduction of session tagging in our authoring environment, you can now leverage those tags as external filters on your VEX landing pages for visitors to use. This is great if you are running a large scale event that incorporates many sessions, or are building an on-demand webinar center for example.
Example of a Landing Page
Use the new Search & Filter tab within your VEX event settings to outline which filters and values will be available on your landing pages.
Search & Filter tab
The Availability tag is based on the status of a session and is not something that you need to manually set. If it is a live session type, the status could be upcoming, live or finished depending on the start times and end times that have been set for that session. If it is an on-demand session type, the only status will be on-demand.
If you want to override the filter labels for your event, you can do this within the new Virtual Event tab of the Languages Configuration settings.
Virtual Event tab
The styling of the search and filter options can be done at the block level within the landing page editor. You can also override your default settings you applied in your Search & Filter tab for each block if required.
Filter and Search configurations
That’s it for this maintenance release! We’ll be back to our regularly scheduled programming for Product Release E on May 11th, with exciting updates across the entire platform. Stay tuned!