- Campaign Standard documentation
- Latest Updates
- 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
- 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
Campaign - Microsoft Dynamics 365 integration workflows
The Workflows page lists the technical workflows and their status.
The integration application comes with three workflows:
Microsoft Dynamics 365 to Campaign
- Send contacts from Microsoft Dynamics 365 into Adobe Campaign
- Custom entities: Bring in custom tables from Microsoft Dynamics 365 to Adobe Campaign. Learn more
- This is also known as Ingress (referring to the ingress of data from Microsoft Dynamics 365 to Adobe Campaign)
Campaign to Microsoft Dynamics 365
- Email marketing events from Adobe Campaign Standard are sent to Dynamics 365 (email send, open, click, bounce). Learn more
- This is also known as Egress (referring to the egress of data from Adobe Campaign to Microsoft Dynamics 365)
Opt-In/Out
Opt-out statuses (e.g., denyList) can be synchronized from Microsoft Dynamics 365 to Adobe Campaign or from Adobe Campaign to Microsoft Dynamics 365. The data can also by synchronized bidirectionally (i.e. data flows in both directions). Learn more.
It is strongly recommended that you stop the Microsoft Dynamics 365 to Campaign workflow before publishing changes to either Adobe Campaign Standard or Microsoft Dynamics 365. These changes include updates to resources/entities (and their associated fields), links, identifier columns, etc… that are currently in use by the integration. Failure to do so could lead to data loss and/or the workflow stopping unexpectedly.
Workflow backlog
This integration application first reads in data and then writes data to the destination. The Backlog column indicates the number of records that have been queued and are waiting to be written. This value is expected to grow when you have a large amount of data to process (e.g., you are running the integration for the first time, you are replaying the data, etc.).
If your Microsoft Dynamics 365 and/or Campaign records are not updating, you should first check to see if there is a large number of records waiting to be written to the destination.
Workflow status
The Status column indicates the state of the background processes associated with the workflow. Possible values are:
- RUNNING: The process is currently running and your data should be synchronized.
- STOPPED: The process is not currently running, so you should not expect your data should be synchronized.
- STARTING: You have requested that the workflow processes to start. The application has not yet started to synchronize the data associated with this workflow, but you can expect it will after a few minutes (when it will then show the status of RUNNING)
- FAILED: The workflow processes were running but they encountered error(s) and they could not recover from these.
Available actions
Possible actions are listed below.
-
Edit: Clicking the pencil icon will send you to another page that will allow you to make updates to the workflow. Keep in mind that any changes you make will NOT take effect until you stop the workflow and then restart it.
-
Start: A Start button requests that a stopped workflow be started. This button will only appear when the processes associated with the workflow are currently stopped. The processes will first change to “STARTING” and then to “RUNNING”. The data associated with the workflow will not start synching until the workflow is in a “RUNNING” state.
The start button is a toggle. If the workflow processes have been started already, the button will change to a Stop button.
-
Stop: A Stop button requests that a running workflow be stopped. This button will only appear when the processes associated with the workflow are currently running.
When you edit a workflow, your updates are NOT immediately incorporated into the running processes’ rules, until you stop the workflow and then click the Start button. Then your updates are incorporated into the running processes (once the process returns to a RUNNING state).
A warning indication is added to the Stop button to let you know when you have (a) made updates to workflow, but (b) have not done a Stop/Start of this workflow.
Resources
Adobe Account
