Technical workflows
Last update: July 8, 2024
- Topics:
- Instance Settings
CREATED FOR:
- Experienced
- Admin
Technical workflows are delivered out-of-the-box with Adobe Campaign. Technical workflows are operations or jobs scheduled to be executed on a regular basis on the server.
They allow you to carry out maintenance operations on the database, leverage the tracking information in the deliveries, and update the provisional jobs on the deliveries.
Functional administrators can access technical workflows under the Administration > Application settings > Workflows menu.
NOTEAs a functional administrator, you can restart or pause technical workflows, and modify their properties and structure.
List of technical workflows
Technical workflows are used to handle self-triggered background and technical processes in Adobe Campaign.
| Label | ID | Description |
| 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. |
Previous pageTarget mappings in Campaign
Next pageBranding
Campaign
- Campaign Standard documentation
- Release Notes
- Getting started
- Profiles and audiences
- Communication channels
- Get started with communication channels
- About communication channels
- Delivery best practices
- Email messages
- SMS messages
- Push notifications
- In-App messaging
- Direct mail
- Transactional messaging
- Landing pages
- Designing email content
- Testing and Sending
- Reporting
- Integrating with other solutions
- Get started with Campaign integrations
- Campaign and Experience Manager
- Campaign and Target
- Campaign and Analytics
- Campaign and Audience Manager or People core service
- Campaign and Analytics for Mobile
- Campaign and Triggers
- Campaign and Microsoft Dynamics 365
- Campaign and Adobe Experience Platform
- Managing processes and data
- Get started with data and processes management
- Workflow general operation
- Executing a workflow
- Calling a workflow with external parameters
- Targeting activities
- Execution activities
- Channel activities
- Data management activities
- Filtering data
- Importing and exporting data
- Use cases
- About workflow use cases
- Deliveries
- Creating deliveries with a complement
- Creating deliveries on profiles’ creation date
- Creating a weekly delivery
- Creating a cross-channel delivery
- Identifying duplicates before a delivery
- Birthday delivery
- Coupling email and direct mail deliveries
- Sending an email with enriched fields
- Personalizing an email with additional data
- Sending a recurring push notification
- Segmentation and targeting
- Data management
- Reconcile a File audience with the database
- Deduplicating the data from an imported file
- Enriching profile data with data contained in a file
- External signal activity and data import
- Updating the database with external data
- Updating data based on an automatic file download
- Data reconciliation using relations
- Data update using reconciliation
- Exporting profiles in an external file
- Updating multiple subscription statuses from a file
- Subscribing profiles from a file to a specific service
- Developing
- Administrating
- Get started with Campaign Standard administration
- Monitoring guidelines
- Audit Trail
- Configuration guidelines
- Users and security
- Configuring channels
- Configuring mobile channels
- Implementing Push tracking
- Adding images and videos iOS
- Understanding push notifications payload structure
- Implementing local notification tracking
- Tags in Adobe Experience Platform synchronization FAQ
- Experience Platform SDK integration FAQ
- Configuring tag rules to support Adobe Campaign Standard use cases
- Mobile use cases supported in Adobe Campaign Standard
- How to migrate your mobile application from SDK v4 to Adobe Experience Platform SDK
- Push Notification Channel changes
- Configuring SMS channel
- Application settings
- Working with APIs
- Get started with Campaign Standard APIs
- About Campaign Standard APIs
- Global concepts
- Interacting with custom resources
- Managing profiles
- Managing services and subscriptions
- Interacting with marketing history
- Privacy management
- Managing transactional messages
- Managing workflows
- Managing organizational units
- Managing geographical units
- Troubleshooting
- Campaign Control Panel