Adobe Campaign comes with a set of built-in technical workflows. They manage operations and jobs scheduled for periodic execution on the server. They let you carry out maintenance on the database, forward tracking information on deliveries, or set up provisional processes on deliveries. Technical workflows are configured via the Administration > Production > Technical workflows node.
Native templates are available for creating technical workflows. They can be configured to suit your needs.
The Campaign process subfolder centralizes the workflows required for executing processes within the campaigns: task notification, stock management, cost calculation, etc.
The list of technical workflows installed with each module is available in a dedicated section.
You can create other technical workflows in the Administration > Production > Technical workflows node of the tree structure. However, this process is reserved for expert users.
The activities offered are the same as for targeting workflows. Learn more
The workflows detailed in this section are installed with the different Adobe Campaign built-in packages. These packages, and related technical workflows, depend on your license agreement.
By default, technical workflows are available in a sub-folder of the following node: Administration > Production > Technical workflows.
Note that technical workflows can only be started and modified by operators with Administration permissions.
Technical workflows related to the Message Center add-on are available by default in the Administration > Production > Message Center > Technical workflows node.
Learn how to monitor technical workflows in this dedicated section.
|Alias cleansing (aliasCleansing)||Installed by default||This workflow standardizes enumeration values. It is triggered every day at 3am by default.|
|Billing (billing)||Installed by default||This workflow sends the system activity report to the ‘billing’ operator by email. It is triggered the 25th of every month on the Marketing instance.|
|Campaign jobs (operationMgt)||Installed by default||This workflow manages the jobs for marketing campaigns (launches targeting, file extraction, etc.). It also creates workflows related to recurring and periodic campaigns.|
|Collect data for HeatMap service (collectDataHeatMapService)||Installed by default||This workflow retrieves data required by the HeatMap service.|
|Collect privacy requests (collectPrivacyRequests)||Privacy Data Protection Regulation||This workflow generates the recipient’s data stored in Adobe Campaign and makes it available for download in the privacy request’s screen.|
|Cost calculation (budgetMgt)||Installed by default||This workflow starts the calculation of expense and cost lines on the budgets, plans, programs, campaigns, deliveries and tasks.|
|Database cleanup (cleanup)||Installed by default||This workflow is the database maintenance workflow: it makes different calculations from the statistics and processes, and deletes obsolete data from the database according to the defined configuration in the deployment assistant. It is triggered every day at 4am by default.|
|Delete blocked LINE users (deleteBlockedLineUsersV2)||LINE channel||This workflow ensures that the LINE V2 users’ data is deleted after they have blocked the LINE official account for 180 days.|
|Delete privacy requests data (deletePrivacyRequestsData)||Privacy Data Protection Regulation||This workflow deletes the recipient’s data stored in Adobe Campaign.|
|Delivery indicators (deliveryIndicators)||Mid-sourcing platform||This workflow updates delivery tracking indicators for a delivery. This workflow is triggered every hour by default.|
|Distributed marketing processes (centralLocalMgt)||Central/local Marketing (Distributed Marketing)||This workflow starts processing related to using the distributed marketing module. It launches the creation of local campaigns and manages notifications related to orders and campaign package availability.|
|Event purge (webAnalyticsPurgeWebEvents)||Web Analytics connectors||This workflow lets you delete every event from the database field according to the period configured in the Lifespan field.|
|Export audiences to the Adobe Experience Cloud (exportSharedAudience)||Integration with Adobe Experience Cloud||This workflow exports audiences as shared audiences/segments. These audiences can be used in the different Adobe Experience Cloud solutions that you use.|
|Forecasting (forecasting)||Delivery||This workflow analyzes deliveries saved in the provisional calendar (creates provisional logs). It is triggered every day at 1am by default.|
|Full aggregate calculation (propositionrcp cube) (agg_nmspropositionrcp_full)||Offer engine (interaction)||This workflow updates the Full aggregate for the Offer proposition cube. It is triggered every day at 6am by default. This aggregate captures the following dimensions: Channel, Delivery, Marketing Offer and Date. The Offer proposition cube is then used to generate reports based on offers. Learn more about cubes in this section.|
|Identification of converted contacts (webAnalyticsFindConverted)||Web Analytics connectors||This workflow indexes site visitors that have completed their purchase after a re-marketing campaign. The data recovered by this workflow can be accessed in the Re-marketing efficiency report (Refer to this page).|
|Import audiences from the Adobe Experience Cloud (importSharedAudience)||Integration with Adobe Experience Cloud||This workflow allows you to import audiences/segments from different Adobe Experience Cloud solutions into Adobe Campaign.|
|Jobs on deliveries in campaigns (deliveryMgt)||Installed by default||This workflow triggers the approved deliveries and starts post-processing the service provider for an external delivery. It also sends approval notifications and reminders.|
|Jobs on service providers (supplierMgt)||Installed by default||This workflow starts processing the provider (email to the router and post-processing) once deliveries have been approved.|
|MID to LineUserID migration (MIDToUserIDMigration)||LINE channel||This workflow generates the LINE V2 users’ ID for migration from LINE V1 to LINE V2.|
|Message Center <external_account_name> (mcSynch_<external_account_name>)||Transactional message control (Message Center - Control)||This workflow:
|MessageCenter full aggregate calculation (agg_messageCenter_full)||Transactional message control (Message Center - Control)||This workflow updates the Full aggregate for the Message center cube. It is triggered every day at 3am by default. This aggregate captures the following dimensions: Channel, Date, Status and Event type. The Message center cube is then used to generate reports based on events. You can learn more about cubes in|
|Mid-sourcing (delivery counters) (defaultMidSourcingDlv)||Transfer to Mid-sourcing||This workflow collects count information for deliveries on the mid-sourcing server. Count information includes general delivery indicators such as number of deliveries sent, etc. Tracking information such as opens are not included. It is triggered every ten minutes by default.|
|Mid-sourcing (delivery logs) (defaultMidSourcingLog)||Transfer to Mid-sourcing||This workflow collects delivery logs on the mid-sourcing server. It is triggered every hour by default.|
|NMAC opt-out management (mobileAppOptOutMgt)||Mobile App Channel (Push)||This workflow updates notification unsubscriptions on mobile devices. It is triggered every 6 hours between 1am and midnight.|
|Offer notification (offerMgt)||Installed by default||This workflow deploys approved offers onto the online environment, as well as every category contained in the offer catalog.|
|Paused workflows cleanup (cleanupPausedWorkflows)||Installed by default||This workflow analyzes paused workflows that have severity set to normal and triggers warnings and notifications when they have been paused for too long. After a month, paused technical workflows are stopped unconditionally. By default, it is triggered every Monday at 5 am. For more information, refer to Handling of paused workflows.|
|Privacy request cleanup (cleanupPrivacyRequests)||Privacy Data Protection Regulation||This workflow erases the access request files that are older than 90 days.|
|Processing batch events (batchEventsProcessing)||Transactional message execution (Message Center - Execution)||This workflow lets you put batch events into a queue before associating them with a message template.|
|Processing real time events (rtEventsProcessing)||Transactional message execution (Message Center - Execution)||This workflow lets you put real-time events into a queue before associating them with a message template.|
|Proposition synchronization (propositionSynch)||Control of offer engine with execution instance||This workflow synchronizes propositions between the marketing instance and the execution instance used for interactions.|
|Recovery of web events (webAnalyticsGetWebEvents)||Web Analytics connectors||Every hour, this workflow downloads segments on internet user behavior on a given site, puts them into the Adobe Campaign database and launches the re-marketing workflow.|
|Reporting aggregates (reportingAggregates)||Delivery||This workflow updates aggregates used in reports. It is triggered every day at 2am by default.|
|Sending of indicators and campaign attributes (webAnalyticsSendMetrics)||Web Analytics connectors||This workflow lets you send email campaign indicators from Adobe Campaign to Adobe Experience Cloud Suite via the Adobe® Analytics connector. The indicators concerned are as follows: Sent (iSent), Total count of opens (iTotalRecipientOpen), Total number of recipients who clicked (iTotalRecipientClick), Errors (iError), Opt-Out (opt-out) (iOptOut).|
|Stock: Orders and alerts (stockMgt)||Installed by default||This workflow launches stock calculation on the order lines and manages warning alerts thresholds.|
|Tracking (tracking||Installed by default||This workflow performs the recovery and consolidation of tracking information. It also assures the recalculation of tracking and delivery statistics, especially those used by Message Center archiving workflows. By default, it is triggered once per hour.|
|Update event status (updateEventsStatus)||Transactional message execution (Message Center - Execution)||This workflow lets you assign a status to an event. Event statuses are as follows:
|Update for deliverability (deliverabilityUpdate)||Installed by default||Once the Deliverability monitoring (Email Deliverability) package is installed, this workflow runs nightly and manages the bounce emails qualification rules, as well as the list of domains and MXs. This requires the HTTPS port to be open on the platform.|