If the scenario was constructed using a Targeter, the content can be updated the same way. If the Targeter is retrieving content from the repository based on a specific attribute, as long as new content contains that attribute, the scenario/targeter combo will still work and will display updated content as often as desired.
For example, you might have a scenario that is combined with a targeter to deliver informational content based on what state the customer lives in, such as a wireless carrier providing information to elite customers in different states. Non-elite customers receive generic information. You might have a scenario which uses a Rule Set in a Targeter to determine what content to display in the slot. The content displayed is based upon the customer’s Home state and memberStatus. An elite customer who lives in Massachusetts will see different content than an elite customer who lives in Connecticut. The Massachusetts customer might see content called PromoOne which contains a description of “Monthly promotion for customers in MA.” The Connecticut customer will see content called PromoTwo which contains a description of “Monthly promotion for customers in CT.” Non-elite customers, no matter what state they live in, will see the generic information. The targeter might be constructed as follows:
Show this content: Items whose description contains Person's homeAddress.state To these people: people whose MemeberStatus is elite Otherwise Show this content: genericPromo to everyone
In order to keep this scenario/targeter combination in place, but update the content, you just need to ensure that the new content is loaded into the same repository and that each item in the repository contains descriptions that contain states. The targeter query will pick up the content based on the description attribute.
Viewing the new content on the site can happen as quickly as the assets (content) are deployed.
