Please upload csv-files with addresses or target group definitions (with customer IDs or eMail addresses) to /upload/manual. Click on Adresses > Lists, choose action Import addresses and follow the given instructions. You can find a manual in article “How to import addresses?”.

A set of standard fields is set up. Individual fields can be defined. When choosing a field description, please take into consideration that these can be used as variables in all e-mail components and that the name scheme should be standardized.

Generally, two types of automatic imports exist:

The complete positive database is available and synchronized on a daily basis. The selection of target groups takes place in promio.connect or via import of target group definitions (customer ID, eMail, internal promio.connect ID, one-columned csv).

Target groups are imported as sub parts of the total database. Here the following options are available:

• Checks for new files run daily or every five minutes.
• Afterwards the target group is ready for further use (standard).
• The target group is added to an existing newsletter list automatically and, thus, is ready for auto target groups afterwards. This makes managing auto campaigns (lifecycle mailings) very easy.

• Sub clients yes/no: Should addresses for different sub clients imported in one file? This can be assigned with b2b_user_id.
• Time of checks for new files (only for daily checks, at the hour 0-24).

File structure / Nomenclature:

• Format: .csv
• Compression (optional): bzip2, gzip with the ending .bz2, .Z
• Encoding (optional): DES openssh
• File name:
  • [SENDERID]_[NAME]_[CHARSET]_[IMPORTTEMPLATEID]_YYYYMMDDHHMMSS.csv
    • SENDERID: ID of the client to which the file is imported
    • NAME: Target group description that is used as the name in the system after import. Please do not use special characters or underscores.
    • CHARSET: [utf8|latin]
    • IMPORTTEMPLATEID: Integer, a variable that is provided by promio.net and that defines all information for the defined filetype (columns and type assignment always have to be constant)
• Validity: The following things are automatically validated:
  • Filename on correct syntax
  • Number of lines in the file vs. number of lines after import into a temporary table
  • E-Mail on correct syntax. Duplicates will be ignored.
• Logfile: After the import a logfile is supplied in the system and, in addition, an e-mail with error and warning information is sent to an defined distribution list.
• Files have to be uploaded into the directory /upload/auto/ of promio.connect SFTP server.

This is the standard file structure which can be extended for individual purposes.

After the automatic import of a target group, you can carry out additional tasks by invoking an API call. A common application is the automatic set-up of an email with subsequent dispatch.

This requires configuring an automatic import process through promio.net support.

To do so, you must provide two files in a ZIP archive:

Contains the data configured for automatic import.

adress1@mail.de
adress2@mail.de

Contains the SOAP API call to be invoked after the automatic import. %CHECKSUM%, %REQUEST_ID% and %TARGETGROUP_ID% must remain unchanged; these placeholders are replaced automatically after import.

The other values must be filled out correctly. Be certain to ensure that all text uses HTML entities throughout.

 < => &lt;
 > => &gt;
etc.

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="https://api.promio-mail.com/1.4/soap/"
                   xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                   xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
                   SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
    <SOAP-ENV:Body>
        <ns1:createDelivery>
            <authentification xsi:type="ns1:authentification">
                <checksum xsi:type="xsd:string">%CHECKSUM%</checksum>
                <requestId xsi:type="xsd:string">%REQUEST_ID%</requestId>
                <requestIdBlockedMinutes xsi:type="xsd:integer">0</requestIdBlockedMinutes>
            </authentification>
            <delivery xsi:type="ns1:delivery">
                <format xsi:type="ns1:contentType">html</format>
                <clientId xsi:type="xsd:integer">$CLIENTID$</clientId>
                <deliveryReceiver xsi:type="ns1:deliveryReceiver">
                    <targetGroupAndSendFromId xsi:type="ns1:targetGroupAndSendFromId">
                        <targetGroupId xsi:type="xsd:integer">%TARGETGROUP_ID%</targetGroupId>
                        <sendFromId xsi:type="xsd:integer">$SEND_FROM_ID$</sendFromId>
                    </targetGroupAndSendFromId>
                </deliveryReceiver>
                <deliverySendTime xsi:type="ns1:deliverySendTime">
                    <sendDelayMinutes xsi:type="xsd:integer">$SEND_DELAY_MINUTES$</sendDelayMinutes>
                </deliverySendTime>
                <sendTestMail xsi:type="xsd:boolean">false</sendTestMail>
                <delivery xsi:type="xsd:boolean">false</delivery>
                <subject xsi:type="xsd:string">Betreffzeile</subject>
                <description xsi:type="xsd:string">Testcampaign</description>
                <campaignCode xsi:type="xsd:string">test</campaignCode>
                <contentHtml xsi:type="xsd:string">
                    &lt;h1&gt;Content&lt;/h2&gt;&lt;p&gt; some escaped HTML &lt;/p&gt;
                </contentHtml>
                <contentText xsi:type="xsd:string">Content text as text/plain</contentText>
            </delivery>
        </ns1:createDelivery>
    </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

This ZIP file must be named according to the agreed upon naming scheme and saved in the SFTP folder /upload/auto for automatic processing.