Will changes of the personalization blocks affect the live campaign?

[algerz81927054]

Hi all,

I'm now having a campaign set up in the "Message Center" using the real-time data type (NmsRtEvent).

My question is:

If referencing a personalization block in the HTML source of the campaign delivery template,

When I make code changes to the personalization block, will the change be applied to the live message immediately?

Or, would the changes only take place when I hit the "publish" button on the dashboard?

If the personalization changes will only work after I published it via the button on the dashboard. Does that mean the live campaign is sending my customers the message based on a mirror file but not based on the real personalization/delivery template?

If so, where does the Adobe Campaign system hold the mirror file (actual live code) before publishing?

[asish_kumarp599]

I think you need to publish it reflect the changes. Have you tried testing this?

[pablo_rosero1]

Hi Alger,

This forum is for Adobe Campaign Standard. Your post has been moved to the Adobe Campaign Classic​ community.

Please post all your comments or questions about Campaign Classic directly there.

All the best,

Pablo

[Jonathon_wodnicki]

All changes to Message Center deliveries need to be published.

[algerz81927054]

Thank you, Pablo!

[algerz81927054]

Thank you for the reply, Wodnicki!

I have very limited knowledge to the Message Center feature. Could I ask one more stupid question?

Q: Do you know where does the Adobe Campaign hold the actual live code? Is there any place could I find the live code?

In other words, once we published a transactional message template, where does Adobe save the published code? In a workflow?

[Jonathon_wodnicki · Accepted solution]

Hi,

Message Center is a transactional messaging product packaged as a Campaign module, which functions in 2 modes: as a single 'control' installed on an existing marketing instance, and as one or more new dedicated 'execution' instances. Each instance has its own db and functions independently, with the execution instances potentially hosting multiple web/smtp servers (1:4 is a good ratio of db:server). The control instance publishes delivery templates and their supporting objects, e.g. typologies, to the execution instances, which then answer soap calls and send out messages using the templates and info from the calls. Periodically the control downloads delivery/tracking log data from the exec instances. Code is contained in nms:messageCenter.js, which can be modified to add functionality in unusual cases. The exec instances are otherwise normal Campaign instances and run maintenance workflows, etc.

Thanks,

-Jon

[algerz81927054]

Thank you, Jon!