Technical workflows technical-workflows

A/B Testing

abTesting

This workflow analyzes the tracking logs of each variant. At the end of the A/B testing period, it automatically calculates the winning variant. By default, it is started every day.

Billing

billing

This workflow sends the system activity report to the 'billing' user by email. By default, it is automatically started every day at 1am.

Copy headers from delivery templates

smtpHeaderupdate

This workflow copies SMTP headers set for email delivery templates to the corresponding child non-template deliveries. Only email marketing deliveries are picked up by this workflow. SMTP headers are not copied to transactional deliveries and proof deliveries.
This workflow is not run periodically. It must be started by the user on a per-use basis.
If there is a high volume of deliveries on your instance, you can update the NmsCleanup_DeliveryPurgeDelay option in the Application settings. If you make a change in SMTP headers of any template, you then need to execute the workflow again after the change so that the corrected headers are copied over to non-template deliveries.Learn more

Database cleanup

cleanup

This workflow is the database maintenance workflow: it runs different statistics and processes, and deletes obsolete data from the database according to the configuration that has been defined. By default, it is automatically started every day 4am.

Import a shared audience

importSharedAudience

This workflow synchronizes the Adobe Experience Cloud audience data imported in Adobe Campaign. By default, it is started every hour.

Instant Report Sharing

reportSendingNow

This workflow is started as soon as a report is scheduled to be sent. It converts your report into a pdf file then sends it in an email to the targeted recipients.

KPIs reconciliation with Adobe Analytics

kpiReconciliation

This workflow fetches the KPIs from Reporting service once a day and reconciles them with the data from Adobe Analytics. It then pushes the difference if needed. By default, it is started every day at 4.20am.

Message Center local archiving

mcSynch_local

This workflow archives real-time events into a historical table. By default, it is started every hour.

Reporting aggregates

reportingAggregates

This workflow updates the aggregates used in the reports. By default, it is automatically started at 2am.

Share KPIs with Adobe Analytics

kpiSharing

This workflow pushes KPI data every 15 minutes from Adobe Campaign Standard to Adobe Analytics.

Sync with Launch

SyncWithLaunch

This workflow synchronizes the tag mobile properties imported in Adobe Campaign Standard. It is started every 15 minutes.

Tracking logs recovery

SyncWithLaunch

This workflow synchronizes the tag mobile properties imported in Adobe Campaign Standard. It is started every 15 minutes.

Recover Tracking Logs

trackingLogRecovery

This workflow restores lost tracking logs. Note that this technical workflow is used in specific contexts and restricted to Adobe internal use only.
By default, it is started every 10 minutes.

Update delivery execution

updateDeliveryExecInfo

This workflow copies the broadlogs and the tracking logs in the local database. By default, it is started every 10 minutes.

Update delivery indicators

updateDeliveryIndicators

This workflow updates the delivery's KPIs (Key Performance Indicator). By default, it is started every hour.

Update event status

updateEventsStatus

This workflow allows you to attribute a status to an event. The following event statuses are available:
Pending: The event is in a queue. No message template has been assigned to it yet.
Pending delivery : The event is in the queue, a message template has been assigned to it and it is being processed by the delivery.
Sent: This status is copied from the delivery logs. It means that the delivery was sent.
Ignored by the delivery: This status is copied from the delivery logs. It means that the delivery was ignored.
Delivery failed: This status is copied from the delivery logs. It means that the delivery failed.
Event not taken into account : The event could not be linked to a message template. The event will not be processed.

Update for deliverability

deliverabilityUpdate

This workflow allows you to create the list of bounce rule qualification rules, as well as the list of domains and MX in the platform. This workflow only functions if the HTTPS is open. By default, it is automatically started at 2am.