WordPress 3.3-beta Ready for testing
A beta release of our WordPress plugin has been released to Github. It adds a number of new settings to the UI to allow customers to manage their Content without development resources.
We’ve added a whole new tab to the Sailthru plugin settings to give you fine grained control over how your WordPress content is synced with Sailthru. While this was achievable previously through WordPress hooks and filters we wanted to put this control in the hands of all of your team, and not need you to rely on developers to add our hooks and filters.
We’ll break it down feature by feature below, but here’s what your new Content Settings screen looks like.
Content API Syncing
This setting allows you to enable or disable the Sailthru content API. In a normal setup this will be enabled by default, but if for you want to only use Sailthru’s spidering to gather the site content you can turn this off.
Included Post Types Allow to Select the Content You Sync to Sailthru
This setting allows you to configure exactly which type of WordPress content you are sending to Sailthru with a few clicks. We’ll detect all the different types of Content available on your site and you choose what to send to Sailthru for use in your content recommendations. Easy.
Sailthru Interest Tags From More Sources
You can now combine Sailthru Tags, WordPress Tags and Categories into a single set of interests to use in Sailthru. This is useful for customers that want to always bring in categories for use as an interest tag. This is an update from our previous behavior, which used a fallback approach to tagging content. We heard that you wanted more control without development hours
We also heard that you want to use your existing WordPress taxonomies as interest tags. So with the release of this functionality not only can you choose WordPress tags and categories you can also layer on any existing taxonomies that you might be using.
We think these changes will give you a lot more control over your content recommendations with less work.
White List of vars
Today Sailthru sends all meta data about a WordPress content type into the Sailthru Content API, our customers are using it for filtering feeds, or using Zephyr to filter content on the fly in an email campaign or on-site. The challenge has been that there’s sometimes too much data for you to filter through and understand. We wanted to make it easier for your teams to understand what is available and control that. So we’ve introduced a global whitelist of vars on the Content API call.
What this means in practice is that you decide what gets sent. If you have a custom field in WordPress that’s meaningful to Sailthru, or data from a plugin and that’s all you want to use in Sailthru then you can add them to a whitelist and we’ll only use that.
Many of our customers use WordPress for their blogging platform in their e-commerce store but did not have a good way to define which content items were from the store and which are from the blog. This field allows you to automatically add a tag o multiple tags to each content item so you know what’s come from where.
We hope you like these upcoming changes, we’re excited about them and wanted to give you the chance to test these changes out before we officially launch the plugin into production and on WordPress VIP. If you have any feedback while you test this on your WordPress sandboxes please let us know.