Üzgünüz, bu sayfa henüz tercüme edilmemiş bulunuyor. Emarsys ekibimizin tüm dökümanlarımızı sizin dilinizde sunmak için yoğun çalıştığından emin olmanızı isteriz.
The Automation Center is a robust and flexible tool, and you can build programs in many different ways. However, the way you build a program path can affect its performance.
Here are some issues that you should always take into consideration before you start building programs, to ensure that their performance is optimal.
Please note that Emarsys is continuously monitoring the Automation Center and in certain circumstances we may put programs into failsafe mode if we find that these pose a risk the overall performance of your account.
Batches are better
A good general rule is that batches processes are more efficient than single ones. In other words, think carefully about how important the timing of a program action really is. Below are some examples.
Emails
If you want to send different content to contacts depending on filter criteria, use the personalization options available in the email rather than creating separate emails on separate program paths. This will also make the email reporting more coherent.
Recurring filters
There are many cases where a Recurring filter entry node will have the same result as an External event node, but will perform far better.
For example, you can trigger a shipping confirmation email using the External event node. But you can just as easily set an hourly filter to return all contacts whose items have been shipped in the last hour, and send a batch email.
Wait nodes
If you set the Wait node to wait for 24 hours, each contact going through it will be processed individually. Where possible, set it to wait for a specific time, e.g. "wait until tomorrow 10 am", and process the contacts in batches.
Consider your account activity as a whole
Remember that an automated program must use the same account resources as your other segments and emails, as well as the other programs.
- Avoid scheduling Wait nodes for high traffic hours when you are sending large email campaigns.
- Avoid scheduling Wait nodes for the same time in multiple programs.
- Avoid scheduling many Recurring filters for the same time.
Filters
All filter nodes reference your entire contact database, even if they are filtering for a single contact, so use them efficiently.
- You should never run multiple filters sequentially. Replace them with a single combined segment.
- Never place a filter immediately after a transactional entry node. Content should be personalized within the email where possible (see above).
Reporting
The Automation Center does have program reporting, but avoid creating extra paths without additional actions (such as sending), merely to see how many contacts end up there.
You will get much more accurate and relevant reporting when you tie your customer engagement programs in with your Smart Insight customer lifecycle reports.