2020 Release Notes: Release G

While you’ve always been able to manually build personalized 1:1 Explore Pages for your ABM campaigns, per target account, PathFactory hasn’t supported dynamically changing Explore Page elements until now. We have enabled automated changes to the company logo and company name based on the visitor. This will ease some of the effort involved in scaling ABM personalization.

As outlined in our 2020 Release D, we switched all PathFactory customers not using our Demandbase integration, over to our OEM 6sense partnership supporting anonymous account identification by default. These new dynamic personalization features are now powered by 6sense account identification by default, and customers using our Demandbase integration are not yet supported for these new features.

Dynamic personalization can be used on Explore pages in two ways:

1. The Brand Logo or Partner Logo can be set to dynamically change based on the visitor’s company that is identified.To configure this simply navigate to Appearance Settings > Explore Tab. You’ll need to be using the Branded, Partnership or Personalized Hero Layout. You’ll notice two new Dynamic toggles on the Brand Logo and Partner Logo fields. If toggled on, PathFactory will infer the company of the visitor (using 6sense), then using an integration with Clearbit will place the visitors Company’s logo into that space. If a company cannot be identified or the logo cannot be retrieved, then PathFactory will default to the logo you have set in the appearance setting, so it is recommended to always include a logo as a fallback.

   

   At the moment you are able to toggle on dynamic logos for both the Brand Logo and Partner Logo fields, but you wouldn’t want to turn both on at the same time because the visitor would then see their company logo twice. We plan to add validation rules to prevent this in the future.

   

   If using the logo personalization feature, we are required to include the message “Logos provided by Clearbit” in the footer of your explore page as shown below.

   

2. The text of the Explore page can be swapped out using various dynamic personalization tokens. Here is an example:When placing copy on your explore page simply use one of these tokens to dynamically swap out the text, per visitor:

    {{company.name}} {{company.naics_description}} {{company.country}} {{company.address}} {{company.city}} {{company.country_iso_code}} {{company.phone}} {{company.domain}} {{company.state}} {{company.region}} {{company.zip}} {{company.employee_count}} {{company.employee_range}} {{company.industry}} {{company.sic}} {{company.revenue_range}} {{company.naics}} {{company.annual_revenue}} {{company.sic_description}}

   All token values returned are supplied by 6sense.

   If a value cannot be found for the visitor then the token will simply render as blank, however in a subsequent release we will be adding support for a default value if the company is not recognized.

For customers who are using their own Demandbase keys in PathFactory, they will not be able to leverage these new dynamic ABM focused features.

PathFactory supports a custom topic taxonomy and many languages, but until now your topic taxonomy was only designed to be used in one language. Because topics can be displayed on Explore Pages and when you use the Topic Sidebar promoter on a Recommend Content Track, we have now added support for localizing topics. When you navigate to Languages, you’ll notice a new Topics tab. In that tab you’ll see your full topic taxonomy which can be customized for any language you have configured.

With this update you can now easily localize every part of all of your Content Tracks and Explore Pages to ensure visitors can have their entire experience available in their native tongue.

In 2020 Release F, we added two new default values per content type. At that time we called them Engagement Weight and Engagement Threshold, however to ensure consistency across our entire product we have renamed these to:

• The header which was previously Engagement Weight is now Content Engagement Score
• The header which was previously Engagement Threshold is now Engagement Time Threshold (Seconds)

We’ve also changed the behavior of these defaults. Previously if you updated a Content Asset’s Content Type, we would not apply the default Content Engagement Score and Engagement Time Threshold (Seconds), however now we do, but only if you hadn’t already customized the Content Engagement Score or Engagement Time Threshold (Seconds) for that asset. So when a Content Asset’s Asset Type is updated we do apply the defaults for that Content Type (presuming you hadn’t already customized these values for that asset). In the example below, note how the defaults change when the asset type changes:

Previously when you changed the default Content Engagement Score or Engagement Time Threshold (Seconds) values in Content Tags, we would automatically apply those new defaults to any asset that had not already had a custom value applied, however, in order to see that change for a given asset in the content library you needed to refresh your browser. We now show that change immediately upon loading a content asset in the Content Library.

When adding Content to a Content Track there are many filtering options already available, however a PathFactory customer requested being able to filter based on when content was last updated, and we’ve added just that. This will make it easier to narrow down the right content when building your track.

Whenever possible we want to allow you to Autoplay videos displayed inside PathFactory, however some browsers and devices have measures which prevent this from happening in some scenarios. In particular some modern browsers prevent videos from autoplaying if they are not muted. We have updated our autoplay feature to automatically mute your videos to increase the likelihood that a video automatically starts playing when accessed, however not all video players, browsers, and browser versions will always autoplay. Note: mobile devices generally do not allow autoplay within a web browser in order to conserve bandwidth. For more detail on the environments we’ve tested and the results we saw, please see the AutoPlay section within our article, Using Video Content in Content Tracks.

We have made two new improvements to our CSV Content Upload to give you greater flexibility for how you keep content up to date.

1. Previously the only unique field we used to identify a Content Asset when updating your Content Library using CSV upload was the Asset URL. This didn’t allow you to update any asset URLs when using CSV Upload. When downloading your Content Library to CSV you’ll notice a new column for “Content UUID” which is a content asset’s unique identifier in PathFactory. You can now include that column in your CSV Upload and provide a new source URL and PathFactory will update the source URL of the asset. Note: If Content UUID is not present, the URL column will be used to identify the content.
2. Previously we required that all columns were included when uploading via CSV, however if the Overwrite all duplicate content assets box was checked on CSV upload, and a column was left blank, the fields would all be overwritten as blank values. We now allow a CSV to be uploaded without all columns being required. Any column omitted will not have it’s values overwritten.

Alongside all of these important incremental enhancements to our core product we’ve also been hard at work on our newest upcoming features:

Virtual Event Experience (VEX) is an extension of our existing capabilities to better accommodate live and on-demand event use cases that are so relevant to the world we live in today.

Website Tools is a new suite of capabilities to optimize the customer and buyer experience by recommending the most relevant content, on your website to each individual visitor and track their content journey on every page on your website.

Contact your Account Executive or Customer Success Manager today to learn more! We’re excited about these and can’t wait to share more.