Show Menu

Load file


Load file
activity allows you to import data in one structured form to use this data in Adobe Campaign. The data is temporarily imported and another activity is necessary to definitively integrate it in the Adobe Campaign database.

Context of use

The way in which the data will be extracted is defined when the activity is configured. The file to load may be a list of contacts, for example.
Only the "flat" structure files are taken into account, such as the .txt, .csv, etc., files for example.
You can:
  • Use the file structure to apply it to another file's data (recovered using the
    Transfer file
    activity) or,
  • Use the structure and data from the file to import it into Adobe Campaign.


The activity configuration involves two steps. First, you need to define the expected file structure by uploading a sample file. Once this is done, you can specify the origin of the file whose data will be imported.
The data of the sample file is used for configuring the activity but is not imported. We recommend using a sample file containing little data.
  1. Drag and drop a
    Load file
    activity into your workflow.
  2. Select the activity, then open it using the button from the quick actions that appear.
  3. Upload the sample file that will let you define the expected structure when importing the final file.
    Once the data file is uploaded, two new tabs appear in the activity:
    File structure
    Column definition
  4. Go to the
    File structure
    tab to view the structure that is automatically detected from the sample file.
    If the file structure was incorrectly detected, you have several options to correct any possible errors:
    • You can choose to use the structure of another file by selecting the
      Detect structure from a new file
    • You can modify the default detection parameters to adapt them to your file. The
      File type
      field lets you specify if the file you want to import is made up of columns with fixed length. In that case, you must also specify the maximum number of characters for each column in the
      Column definition
      All of the detection options necessary to correctly recover the data from the file are regrouped in
      File format
      . You can modify them then re-detect the structure of the last file loaded in the activity by taking into account these new settings. To do this, use the
      Apply configuration
      button. For example, you can specify a different column separator.
      This operation takes into account the last file that was loaded in the activity. If the file detected is large, the data preview will only show the first 30 lines.
      In the
      File format
      section, the
      Check columns from file against column definitions
      option lets you verify that the columns of the file you are uploading correspond to the column definition.
      If the number and/or name of columns don't match the column definition, an error message will display when executing the workflow. If the option is not activated, warnings will display in the log file.
  5. Go to the
    Column definition
    tab to check the data format for each column and adjust the parameters if necessary.
    Column definition
    tab allows you to precisely specify the data structure of each column in order to import data that does not contain any errors (for example, using null management) and make it match the types that are already present in the Adobe Campaign database for future operations.
    For example, you can change the label of a column, select its type (string, integer, date, etc.) or even specify error processing.
    For more information, refer to the Column format section.
  6. In the
    tab, specify whether the file is to be processed for loading data:
    • Comes from an inbound transition in the workflow.
    • Is the one that you uploaded during the previous step.
    • Is a new file to upload from the local machine. The
      Upload a new file from local machine
      option appears if uploading a first file was already defined in the workflow. This allows you to upload another file to be processed if the current file does not suit your needs.
  7. If the file that you want to load the data from is compressed into a GZIP file (.gz), select the
    option in the
    Add a pre-processing step
    field. This allows you to unzip the file before loading the data. This option is only available if the file comes from the activity's inbound transition.
  8. The
    Keep the rejects in a file
    option enables you to download a file containing errors that occurred during the import, and to apply to it a post-processing stage. When the option is activated, the outbound transition is renamed as "Rejects".
    Add date and time to the file name
    option lets you add a timestamp the name of the file containing the rejects.
  9. Confirm the configuration of your activity and save your workflow.
If any error occurs with the activity after executing the workflow, refer to the logs to get more details on the values that are incorrect in the file. For more on workflows logs, refer to this section

Column format

When you load a sample file, the column format is automatically detected with the default parameters for each data type. You can modify these default parameters in order to specify the particular processes to apply to your data, particularly when there is an error or an empty value.
To do this, select
Edit properties
from the quick actions of the column whose format you would like to define. The column format detail window will open.
You may then modify the formatting for each column.
The column formatting allows you to define the value processing of each column:
  • Ignore column
    : does not process this column during data loading.
  • Data type
    : specifies the type of data expected for each column.
  • Format and separators
    : specify the properties of a text, the time, date, and numerical value format, as well as the separator specified by the column context.
    • Maximum number of characters
      : specifies the maximum number of characters for string type columns.
      This field must be filled in when loading files made up of columns with fixed length.
    • Letter case management
      : defines whether a character case process needs to be applied for
    • White space management
      : specifies whether certain spaces need to be ignored in a string for
    • Time format
      Date format
      : specify the format for
      Date and time
    • Format
      : allows you to define the format of numerical values for
      Floating number
    • Separator
      : defines the separator specified by the column context (thousands separator or decimal separator for numerical values, separator for dates and time) for
      Date and time
      , and
      Floating number
  • Remapping of values
    : this field is only available in the column detail configuration. It lets you transform certain values when they are imported. For example, you can transform "three" into "3".
  • Error processing
    : defines the behavior if an error is encountered.
    • Ignore the value
      : the value is ignored. A warning is generated in the workflow execution log.
    • Reject the line
      : the entire line is not processed.
    • Use a default value
      : replaces the value causing the error with a default value, defined in the
      Default value
    • Use a default value in case the value is not remapped
      : replaces the value causing the error with a default value, defined in the
      Default value
      field, unless a mapping was defined for the erroneous value (see the
      Remapping of values
      option above).
    • Reject the line when there is no remapping value
      : the entire line is not processed unless a mapping was defined for the erroneous value (see the
      Remapping of values
      option above).
    Error processing
    concerns errors regarding values in the imported file. For example, a faulty data type encountered ("four" all in letters for an "Integer" column), a string containing more characters than the maximum number authorized, a date with faulty separators, etc. However, this option does not concern errors generated by empty value management.
  • Default value
    : specifies the default value according to the error processing chosen.
  • Empty value management
    : specifies how to manage empty values during data loading.
    • Generate an error for numerical fields
      : generates an error for the numerical fields only, otherwise inserts a NULL value.
    • Insert NULL in the corresponding field
      : authorizes empty values. The value NULL is therefore inserted.
    • Generate an error
      : generates an error if a value is empty.

Example 1: Updating the database

The load file activity mainly structures the data from a transfer file activity in order to integrate it into the existing data.
The following example shows the result of an automatically downloaded load file activity via a transfer file activity, followed by an update data activity. This workflow aims to enrich the Adobe Campaign database with new profiles or to update existing profiles using the data recovered from the imported file.
  1. Drag and drop a
    Transfer file
    activity into your workflow and configure it in a way so that it recovers the file you would like.
  2. Drag and drop a
    Load file
    activity into your workflow and place it after the
    Transfer file
  3. Select the activity, then open it using the button from the quick actions that appear.
  4. In the
    File to load
    section of the
    tab, check the
    Use the file specified in the inbound transition
  5. Configure your activity as specified earlier.
  6. Drag and drop an
    Update data
    activity into your workflow and place it after the
    Load file
    activity, then configure it. Refer to Update data .
Once the workflow has started, the data from the uploaded file is extracted and then used to enrich the Adobe Campaign database.

Example 2: Sending an email with enriched fields

The load file activity also enables to send an email enriched with additional data from an external file in the same workflow.
The example below shows how to send an email using additional data retrieved from an external file through the load file activity. In this example, the external file contains a list of profiles with their associated account number. You want to import this data to send an email to each profile with their account number.
  1. Drag and drop a
    activity into your workflow and open it to define the main target.
  2. Drag and drop a
    Load file
    activity to assign some data to a profile. In this example, load a file containing account numbers corresponding to some profiles of the database.
  3. Drag and drop an
    activity into your workflow and link the load file and query activities to it.
  4. In the
    Advanced relations
    tab of the enrichment activity, select the
    0 or 1 cardinality simple link
    and define the fields to be used for reconciliation. Here we use the last name to reconcile the data with the database profiles.
  5. In the
    Additional data
    tab, select the elements that you want to use in your email. Here select Account number (column from the file that you retrieved through the load file activity).
    For more on this, see the Enrichment section.
  6. Drag and drop a
    activity into your workflow and open it to refine the main target.
    For more on this, see the Segmentation section.
  7. Drag and drop an
    Email delivery
    activity into your workflow and open it.
  8. Add a personalization field and select the additional data defined in the enrichment activity (here Account number) from the
    Additional data (targetData)
    node. This enables to dynamically retrieve the account number of each profile in the email content.
  9. Save the email and start the workflow.
The email is sent to the target. Each profile receives the email with their corresponding account number.