What’s New With Bronto’s Product Catalog Data Feature? August 25th, 2015 Mike Gottlieb, Manager, Product Management Mike Gottlieb, Manager, Product Management Mike Gottlieb, Manager, Product Management Author BioMike Gottlieb works to identify trends and bring to market new features and functions for users of Oracle’s Bronto Software. He is currently focused on solutions that deliver personalized product content, and he also oversees product management activities on Bronto’s existing embedded apps. With more than 12 years of experience launching new products across several different industries, including retail, healthcare, pharmacy automation and HR, Gottlieb has a proven track record of delivering high-quality, impactful solutions. Read More About Mike Mike Gottlieb, Manager, Product Management It’s been a few weeks since we graduated the Product Catalog Data feature from Bronto Labs, and it has been a success for our early adopters! Many of you have begun to import your product feeds and are starting to leverage that data in your marketing messages. Since the feature was first introduced in Bronto Labs a little over two months ago, we’ve seen our customers import over 1.1 million products and send more than 40 million messages with those products. If you’re not one of those customers, get started today! My first blog post will point you in the right direction: Enhance Your Message Content With Product Data. Customer Webinar Want a quick tour of the new Product Catalog functionality? Click here to view a Webinar! Quick Tips for Successfully Importing Product Data Since the feature’s release, I’ve noticed a few of you have had some difficulty importing your first product feed. Here are four quick tips to help you. As always, don’t hesitate to contact Bronto Support with questions. Ensure your product file is a properly formatted delimited or xml file. For samples of what a proper file looks like, check out Bronto Help. We followed Google’s Products Feed Specification, so if you want even more detail, read their documentation. Make sure your Bronto Product Configuration is set up correctly, including selection of the right feed format and field delimiter. Triple check your Field Mappings to make sure you entered the correct labels from your product feed’s header row or xml tags. You must use the complete label for this to work, including any prefix, such as g:, that might appear with that label. After your import is completed, check the Product Import History page in the Products section. If the import failed or completed with any failed products, something went wrong. You can click the Transaction Log link to download a log of the issues, which should help you troubleshoot what went wrong. Usually, the issues are either a poorly formatted file, a mismatched mapping, or some missing data from specific product rows. What’s New We continue to enhance the experience of using Product Catalog Data in your messages. In the last few weeks, we have introduced two new features to further streamline the process. Inserting Product Tags In my first blog post, I covered the Product tag syntax needed to insert products into your messages. It required you to know the syntax as well as the product field names. Now, if you are using the New Message Editor, you can select the Product Tag option from the Add Content Insert menu to see a list of all available product fields. From that list, you can select the field you wish to insert into your message and then specify the placeholder you want to associate it with. Or, if you want to display product data connected to a cart loop, you can check the “Use Cart SKUs” checkbox. When you click Insert Product Tag, the tag is created for you in the body of the message. Specify Delivery-Specific Product IDs in the AddDeliveries API If you are currently using the addDeliveries API to schedule your messages, you now have the option to specify which Product IDs you would like to use for each product placeholder in your message. That means you can create template messages with these product placeholders and decide at the time of scheduling, via the API, which products you would like to use in that specific delivery. If you have the capabilities to programmatically fill in those placeholders, you might even come up with some pretty creative uses for this feature! For more info on how to update your API call, check out the Bronto Developers website. If you have any comments or questions on this post, please leave a comment and I’ll respond as quickly as possible.