- 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
Data reconciliation using relations
The following example demonstrates a workflow that updates the database using the purchasing data in a file. The purchasing data contains data referencing elements from other dimensions, such as the client emails and product codes.
The Transactions and Products resources used in this example do not exist in the Adobe Campaign database by default. They were therefore created beforehand using the Custom resources function. The profiles that correspond to the email addresses in the imported file, as well as the products, were loaded into the database beforehand.
The workflow is made up of the following activities:
-
A Load file activity, which loads and detects the data of the file to import. The imported file contains the following data:
- Transaction date
- Client email address
- Code of product purchased
date;client;product 2015-05-19 09:00:00;mail1@email.com;ZZ1 2015-05-19 09:01:00;mail2@email.com;ZZ2 2015-05-19 09:01:01;mail3@email.com;ZZ2 2015-05-19 09:01:02;mail4@email.com;ZZ2 2015-05-19 09:02:00;mail5@email.com;ZZ3 2015-05-19 09:03:00;mail6@email.com;ZZ4 2015-05-19 09:04:00;mail7@email.com;ZZ5 2015-05-19 09:05:00;mail8@email.com;ZZ7 2015-05-19 09:06:00;mail9@email.com;ZZ6 -
A Reconciliation activity to bind purchasing data to database profiles as well as products. It is therefore necessary to define a relation between the file data and the profile table as well as the product table. This configuration is carried out in the activity’s Relations tab:
- Relation with the Profiles: the file’s client column is linked to the email field of the Profiles dimension.
- Relation with the Products: the file’s product column is linked to the productCode field of the Profiles dimension.
Columns are added to the inbound data in order to reference the foreign keys of the linked dimensions.
-
An Update data activity allows you to define the database fields to update using the imported data. As the data was already identified as belonging to the Transactions dimension in the previous activity, here you can use the Directly using the targeting dimension identification option.
By using the option that automatically detects fields to update, the links configured in the previous activity (to profiles and products) are added to the list of Fields to update. You must also make sure that the field that corresponds to the transaction date is correctly added to this list.
Resources
Adobe Account
