Content of e-Marketing Spot remote widgets and feeds
When you decide to offer an e-Marketing Spot as a remote widget or a feed, you must decide which data to display to customers in the widget or feed reader. The data can be images or text, or both.
The web activities and default content scheduled for the e-Marketing Spot provide the data available for display in the remote widget or feed reader. A set of feed formatting JSP files then define which pieces of the available data to include in the Atom feed that is passed to the remote widget or feed reader. The data available depends on the type of web activity or default content running in the e-Marketing Spot, and your specific store implementation. Here are a few examples:
- Consider an e-Marketing Spot that displays a "Deal of the Day" ad using a web activity with the Recommend Content action. In this example, the web activity returns the following data to the e-Marketing Spot: a single image of the "Deal of the Day" ad. When this e-Marketing Spot is offered as a remote widget or feed, the data available is the single image.
- Consider another e-Marketing Spot that displays a list of featured products using a web activity with the Recommend Catalog Entry action. In this example, the web activity returns the following data about each product to the e-Marketing Spot: product name, standard price, offer price, long description, short description, full image, thumbnail image, descriptive attributes, and so on. When this e-Marketing Spot is offered as a remote widget or feed, all this data is available. If you want to display only the product name and the thumbnail image in the remote widget or feed reader, a store developer can customize the associated feed JSP file to include only those two pieces of data in the Atom feed.
- Consider another e-Marketing Spot that has no web activities running and displays default content. The same logic described in the previous examples for web activities applies to default content: the data available for the Atom feed depends on the type of default content being displayed, that is, catalog entries, categories, and content.
For e-Marketing Spot remote widgets, the widget editor you use gives you a lot of control over how you use the Atom feed data in the widget. For example, you can include all the feed data in the widget, or exclude data you do not want to display. You can arrange the data any way you want in the widget. In addition, you can add text, images, buttons, and other features to the remote widget that are not included in the feed.
For e-Marketing Spot feeds displayed in a feed reader, it is important that the Atom feed contains only the specific text and images from the e-Marketing Spot that you want to display in the feed reader.
Atom feed default content
The following table lists the data that each feed entry will contain without customization of the feed formatting JSP files, based on the type of web activity that is running in the e-Marketing Spot:
| Type of web activity | What each entry in the Atom feed will display by default |
|---|---|
Displays catalog entries from the store catalog
using actions such as:
|
|
Displays promotional advertisements and/or text
using one of:
|
One of the following:
If the marketing content has a predefined or custom click action, the feed will support it. |
Displays categories from the store catalog using
one of:
|
|
Feed format
WebSphere Commerce delivers the feed in Atom-format XML, making it readable in browsers and on sites that support Atom feeds. If your site requires RSS-format, a store developer can customize the feed formatting JSP files. Changing the JSPs implies providing the content using different tags and a slightly different structure. The client should be able to interpret and support both formats. The feed has a parameter where you can specify what format you want. By default, WebSphere Commerce uses Atom format, but the format can be changed.