We are very excited to finally announce the release of custom user roles within the platform, adding in the management of user roles and permissions! You, our customers, are always fantastic about providing feedback for future improvements and this was a big ticket item. With the varying structures of teams and needs, we wanted to not only give you the autonomy to define your own user roles, but also increase the flexibility of access across the platform. We have tried to exemplify best practices from some of your favorite (or not so favorite) SaaS platforms, putting the control in your hands.

Admins, Authors and Reporters are still available as default roles within PathFactory, however any Admins will now be able to see an additional tab within the User Management section called User Roles. Here you can add these custom roles and define which areas within your subscriptions of the PathFactory platform the role type will have access to. For example, if a custom role has access to User Management selected in their permissions, they will also be able to create, edit and delete role types moving forward.

Once you have built and saved your user role, you can then apply that new custom role to any users moving forward within the User List tab. User roles can be cloned for easy scaling/editing and multiple role types can be applied to a single user. This is particularly helpful if you are defining roles by module (Campaign Tools, Website Tools, VEX or PathFactory for Sales), and there are certain users that need access to more than one module, such as Campaign Tools and VEX.

For full details on our new roles and permissions capabilities, visit our updated user roles article.

Do you have a custom language name that was not available in our languages tag drop down list for content assets? If so, this update is for you! We have updated this list to be based off the language configurations in the platform settings tab. Here, you can add new custom language names. These names will then be available within your drop down list when tagging content assets and can also be surfaced as values within your language filters on Explore, VEX and Microsite pages. Have a niche language that you want to be able to surface for a specific region you are promoting to? We’ve got you covered.

If you’ve ever been in these libraries within the platform settings, you’ve probably selected a piece of external code, CTA button or specific form and said to yourself “GAH! I wish I could see where this has been applied!” Rest easy, you weren’t alone.

Now when you navigate to any of these libraries and select a configuration from the list, the right pane will show information about where that configuration is currently applied. This will help with governance and maintaining clean libraries, while also providing much needed visibility before making any changes to these configurations.

Admins are now able to enable or disable the Eloqua tracking script for Campaign Tools and VEX within the Eloqua Account tab of the Organization Settings. When enabled, PathFactory automatically loads the Eloqua tracking script onto your Campaign Tools and VEX pages. You can disable this if you wish to customize your Eloqua tracking script implementation in external code. A common use case that supports this need is when your Eloqua tracking script is included in your tag management. To avoid it loading twice and therefore tracking page views twice, we have added this option.

Previously when using our dynamic text and logo capabilities on Explore pages, if a visitor landed on the Explore page then PathFactory would use the IP address to look up the company data which is powered by 6sense. This 6sense company data then gets saved in a data table. This is a unique benefit for PathFactory customers. We have OEM’d 6sense giving you the industries’ best match rates.

This improvement allows PathFactory to take a known visitor’s email domain and align it to the appropriate 6sense company data in the data table. It increases the likelihood for accuracy rather than searching for a match based on the visitor’s IP address each time. This will also populate relevant information for field merges moving forward as well.

If no 6sense company data from the table matches the email domain, then we simply use the IP address once again to look up 6sense company data as before. This helps to handle any scenarios where a visitor is known by a public email domain vs. a company one (gmail, hotmail etc.). If no 6sense company data is surfaced in the IP lookup, your fallback settings will be displayed just as they were in the past.

Previously, when adding a title override to a content asset within a track, this override title was not being displayed in search engine results when the track search engine directive was set to allow for this. We have updated this logic to ensure the override title is what is displayed if it’s been applied. If the content asset has a designated SEO title however (which can be configured in the advanced edit window of the asset), this will take priority.

In an effort to simplify the configuration work for your microsites, we have added the ability to define your search and filter settings once vs. having to do it within each track block on the landing page editor tool. To leverage this capability, navigate to the new Search & Filter tab within your microsite settings area.

You’ll then be able to define whether you want the search bar to be available on your microsite landing pages for visitors to interact with, as well as the filters. You can also select which values you want to be available within these filters externally. These settings can still be overridden at the track block level within the landing page editor tool.

If you want to override any of the filter labels to display different text externally, you can do this within the new Microsite Builder tab of the Languages Configuration settings.

This new tab in Appearances Configuration gives you the flexibility to update the look and feel of your landing page filters and card configurations across your entire microsite or VEX event. You can also now set a rounded corner radius for your card configurations!

Release E allows you to apply multiple query strings to your VEX or microsite landing page link before sharing externally. Once a visitor clicks into your landing page, the search criteria and/or available filter drop downs will be pre-filtered based on the values set in your query strings. This is a great way to direct different audiences (possibly entering from different channels or part of different persona groups) to predefined content while still providing them the flexibility to expand your search. It also reduces your need to create multiple versions of pages for these different groups.

For more information on query strings or advice on how to set them for your links, reach out to your Solutions Architect and they will be happy to help!

Your visitors can now choose multiple values when interacting with your filters on VEX or microsite landing pages. This logic is based on an “or” format, so any of the defined track assets / sessions for that block that are tagged with any of the values selected will be displayed. They can also search for keywords, which is helpful for lists that are traditionally longer such as topics.

You will now be able to better surface your known visitors from PathFactory who are visible in PathFactory for Sales but not yet a contact or lead in Salesforce. These visitors that are known to PathFactory will now get surfaced in account saved search criteria so that you can get a true, holistic view of all visitors engaging within your accounts.