Use the FDA Connector (Federated Data Access) to connect Campaign to one or more external databases and process information stored into them without affecting your Campaign Cloud Database data. You can then access external data without changing the structure of Adobe Campaign data.
As a Managed Cloud Services user, contact Adobe to connect your external database(s) with Campaign.
Compatible databases for Federated Data Access are listed in the Compatibility matrix.
In the context of an Enterprise (FFDA) deployment, a specific external account is available to manage communication between Campaign local database and Snowflake cloud database. This external account is set up for you by Adobe and must not be modified.
The FDA option is subject to the limitations of the third-party database system that you use.
In addition, be aware of the following limitations and best practices:
The FDA option is made to manipulate the data in external databases in batch mode in workflows. To avoid performance issues, it is not recommended to use the FDA module in the context of unitary operations, such as: personalization, interaction, real-time messaging, etc.
Avoid the operations that need to use both the Adobe Campaign and the external database as much as possible. To do this, you can:
Export the Adobe Campaign database to the external database and execute the operations only from the external database before re-importing the results into Adobe Campaign.
Collect the data from the external Adobe Campaign database and execute the operations locally.
If you want to carry out personalization in your deliveries using data from the external database, collect the data to use in a workflow to make it available in a temporary table. Then use the data from the temporary table to personalize your delivery. To perform this, pre-process message personalization in a dedicated workflow using the Prepare the personalization data with a workflow option, available in the Analysis tab of the delivery properties. During the delivery analysis, this option automatically creates and executes a workflow that stores all of the data linked to the target in a temporary table, including data from tables linked in an external database.
This option significantly improves performances when executing the personalization step.
Campaign comes with several workflow activities you can use to interact with data from your external database(s):
Filter on external data - Use the Query activity to add external data and use it in the defined filter configurations.
Create sub-sets - Use the Split activity to create sub-sets. You can use external data to define the filtering criteria to use.
Load external database - Use the external data in the Data loading (RDBMS) activity.
Adding information and links - Use the Enrichment activity to add additional data to the worktable of the workflow, and links to an external table. In this context, it can use data from an external database.
You can also directly define a connection to an external database from all the workflow activities listed above, for a temporary usage. In this case, it will be on a local external database, to be used only within the current workflow.
This type of configuration must only be used temporary to collect data. The external account configuration should be preferred for any other usage.
For example, in the Query activity, you can define a temporary connection to an external database as follows: