How to use workflow data
- Applies to:
- Campaign Classic v7
- Topics:
- Workflows
- Data Management
Updating the database
All collected data can be used to update the database, or in deliveries. For example, you can enrich message content personalization possibilities (include the number of contracts in the message, specify the average shopping cart over the last year, etc.) or detail population targeting (send a message to contract co-holders, target the 1,000 best subscribers to online services, etc.). This data can also be exported or archived in a list.
Lists and direct updates
The data of the Adobe Campaign database and the existing lists can be updated using two dedicated activities:
-
The List update activity lets you store worktables in a datalist.
You can select an existing list or create it. In this case, the name and possibly the record folder are computed.
Refer to List update.
-
The Update data activity performs a mass update of the fields in the database.
For more on this, refer to Update data.
Subscription/unsubscription management
To find out about subscribing and unsubscribing recipients to an information service via a workflow, refer to Subscription Services.
Sending via a workflow
Delivery activity
The delivery activity is detailed in Delivery.
Enriching and targeting deliveries
Deliveries can process data from workflows in order to customize content or within the framework of target population selection.
For example, within the framework of a direct mail delivery, you can include the additional data, taken from data manipulation carried out in the workflow, in the extraction file:
In addition to the usual personalization fields, you can add personalization fields from workflow stages to the delivery content. The additional data defined in the workflow activities can be kept and made accessible in the delivery assistant, as shown in the example below, for defining the name of the output file within the framework of direct mail delivery:
The data contained in the workflow table is identified by its name: it is always made up of the targetData link. For more on this, refer to Target data.
Within the framework of email delivery, personalization fields can also use data from target extension performed in the targeting workflow stages, as shown in the example below:
If a segment code is specified in a targeting activity, it is added to a specific column of the workflow table and will be offered along with the personalization fields. To display all personalization fields, click the Target extension > Other… link accessible via the personalization button.
Campaign
- Campaign v7 documentation
- Release notes
- Get started
- Start with Adobe Campaign
- Profile management
- Create and manage lists
- Import and export data
- Filter data
- Create queries
- Permissions
- Data packages and enumerations
- CRM connectors
- Create and send messages
- Get started with messages
- Send emails
- Send SMS
- Send LINE messages
- Send push notifications
- Send direct mail
- Use delivery templates
- Personalize deliveries
- Use seed addresses
- A/B testing
- Services and subscriptions
- Monitor deliveries
- Get started with delivery monitoring
- Access the list of deliveries
- Delivery dashboard
- Delivery performances best practices
- Delivery troubleshooting
- Delivery statuses
- Understand delivery failures
- Understand quarantine management
- Track messages
- Track personalized links
- Configure URL tracking options
- Access the tracking logs
- Test tracking
- Tracking troubleshooting
- Deliverability management
- Content management module
- Orchestrate marketing campaigns
- Response manager
- Design and share reports
- Design web content
- Create online surveys
- Integrate with Adobe Experience Cloud
- Automate with workflows
- Manage Offers
- Transactional Messaging
- Integrate with social media
- Installation and configuration guide
- Architecture principles
- Deployment types
- Security and privacy settings
- Install Campaign (on-premise)
- Configure Campaign
- Connect to Campaign
- Connect Campaign to external systems
- Configure external accounts
- Configure Federated Data Access
- Get started with Federated Data Access
- Best practices and limitations
- Configuration guidelines
- Configuration steps
- Configure Amazon Redshift
- Configure Azure Synapse
- Configure Google BigQuery
- Configure Hadoop
- Configure Microsoft SQL Server
- Configure Netezza
- Configure Oracle
- Configure PostgreSQL
- Configure SAP HANA
- Configure Snowflake
- Configure Sybase IQ
- Configure Teradata
- Configure Vertica Analytics
- Remote access rights
- Connect to the database
- Create the data schema
- Define data mapping
- Appendices
- Monitoring guide
- Developers guide
- Technotes
- Campaign Control Panel