Required file name format for uploading a file archive
When you upload multiple files in a compressed archive to the Content Library, the Message Editor uses the name of each uploaded file to generate the name of the content element that it creates for the file. If the file name includes double underscores, the Message Editor can configure additional content element properties, including reference labels and multiple content variations. The file name format uses double underscores as separators in a specific sequence. All files in the archive must follow the file name format exactly.
Automatically configuring reference labels and content variations based on file name is available only for file archives that you designate as Content archives. You cannot automatically configure multiple content variations or reference labels for Template or Mixed archives.
If the Message Editor detects a file name that contains double underscores in its filename, the system checks the archive to confirm that all file names follow the required name format. The system cancels the upload if any of the files do not follow the name format exactly. If no files contain double underscores, the system does not configure additional content element properties and it creates a single content element for each uploaded file.
| Content type | File name structure required during upload |
|---|---|
|
Content element that contains a single asset |
<content element name>.<file extension> Example: Uploading the file Coupon.html creates the content element Coupon.html. |
|
Content element with a single asset and a reference label (optional) |
<content element name>__<reference label>.<file extension> Example: Coupon__frenchcoupon.html creates the content element Coupon__frenchcoupon.html and assigns the reference label frenchcoupon to the content element. |
|
Single content element that contains multiple variations. |
<content element name>__<variation field name>__<variation field value>.<file extension> Example: Uploading an archive with the following three files creates the single content element Coupon that contains the files as multiple variations.
If the value of the personalization field LOCALE for an email recipient listed in the output list table (OLT) is french, then the content of Coupon__LOCALE__french.html displays in the email or landing page sent to that individual. For example, the coupon might be translated into French for an email recipient that specified French as the preferred language for contact by email. |
|
Default content variation. |
<content element name>__ <variation field name>__[[<variation field value>]].<file extension> Content elements that contain multiple variations must specify one default variation. The default variation displays when the value of the variation field for the recipient does not match any of the variation values specified in the content element. Specify the default variation by using double square brackets in the file name. Example: In the following list of files, Coupon__LOCALE__[[english]].html will be designated the default variation for the content element Coupon.
|
|
Content element with multiple variations and specifies a reference label. |
<content element name>__ <reference label>__<variation field name>__ <variation field value>.<file extension> Example: Uploading the following list of files creates the content element Coupon and assigns the reference label rewardspromo to the content element. Notice that you need to define a reference label for only one variation to assign the label to the content element.
|
The variation field that you specify to configure multiple content variations must be an OLT personalization field defined in an Output List Table (OLT). You can view a list of available personalization fields on the Deliver Settings page. You cannot use a Built-in or Constant personalization field as a variation field.
The variation value that you select for each content variation must be configured as an additional value for the personalization field that you specify as the variation field. You define the possible variation values in the properties of the personalization field.