Bulk files, especially those with a large number of rows, can be uploaded via FTP, which can be useful for repetitive tasks such as keyword bid changes or monthly budget setting.
The easiest way to connect to the Platform via FTP is to use an FTP program. There are many of these available to download online. One such example is Filezilla, a free, open-source FTP program available for Windows, Mac and Linux.
For more information on Filezilla and help on using the program, please feel free to read their Wiki article: https://wiki.filezilla-project.org/Using (external link).
Once you have an FTP program, open it up and enter the following credentials:
Server: ftp.marinsoftware.com
Username: Your Platform username
Password: Your Platform password
Once you have successfully connected, each client you have access to will be listed as a separate folder represented by their Tracker ID. Files should be transferred to the top level folder (not any of the sub-folders within each client folder) and will begin processing in the Activity Log of the client (normally within 30 seconds).
To determine the correct folder for each client, you can navigate to the Admin tab, click on the Clients & Users tab and the Clients sub-tab, where you will find each of your MarinOne client accounts listed, along with a Tracker ID column. The alphanumeric string in this column will line up with the FTP folder you will use for uploading files.
Files can be either tab or comma delimited and saved in either Unicode text (.txt) or .csv format. It's also possible to compress a large single file in .zip format to reduce file transfer time.
Please note that Excel corrupts non-standard / double-byte characters, e.g. ê, Ä, ß, á, Ñ, ®, あ, ﾙ, ض, etc. when saving as CSV or Text (Tab delimited) format. However, saving as a Unicode Text in Excel will preserve all special characters in the bulk upload file.
The structure of the files should be the same format as when using the Bulk Tool in the Platform.
The same logic also applies:
Files must begin with one of the prefixes listed below. FILENAME can be replaced with any text to make the file easily identifiable for you.ns_FILENAME.txt
|
Object |
Standard |
Held |
Auto |
|
Campaign |
campaign_FILENAME.txt |
campaignHeld_FILENAME.txt |
campaignAuto_FILENAME.txt |
|
Group |
group_FILENAME.txt |
groupHeld_FILENAME.txt |
groupAuto_FILENAME.txt |
|
Keyword (in existing campaign & group) |
keyword_FILENAME.txt |
keywordHeld_FILENAME.txt |
keywordAuto_FILENAME.txt |
|
Keyword (edit only) |
keywordEdit_FILENAME.txt |
keywordEditHeld_FILENAME.txt |
- |
|
Keyword (in new or existing campaign)* |
- |
bulkCreateCampaignsHeld_ FILENAME.txt |
bulkCreateCampaigns_ FILENAME.txt |
|
Negative Keyword |
negative_FILENAME.txt |
negativeHeld_FILENAME.txt |
- |
|
Creative |
creative_FILENAME.txt |
creativeHeld_FILENAME.txt |
creativeAuto_FILENAME.txt |
|
Placement |
placement_FILENAME.txt |
placementHeld_FILENAME.txt |
- |
|
Google Product Group |
shopping_FILENAME.txt |
shoppingHeld_FILENAME.txt |
shoppingAuto_FILENAME.txt |
|
Microsoft Product Target |
shopping_FILENAME.txt |
shoppingHeld_FILENAME.txt |
shoppingAuto_FILENAME.txt |
|
Sitelink |
sitelink_FILENAME.txt |
sitelinkHeld_FILENAME.txt |
- |
|
Microsoft Sitelink |
sitelinkMicrosoft_FILENAME.txt |
sitelinkMicrosoftHeld_FILENAME.txt |
- |
|
Folder |
folder_FILENAME.txt |
- |
- |
|
Action by Dimension |
dimensions_FILENAME.txt |
dimensionsHeld_FILENAME.txt |
dimensionsAuto_ FILENAME.txt |
|
Location Targets |
geoLocationTargetCampaigns_ FILENAME.txt |
geoLocationTargetCampaignsHeld_ FILENAME.txt |
- |
|
Group Level Retargting |
groupRetargetList_ FILENAME.txt |
groupRetargetListHeld_ FILNAME.txt |
- |
* Format should be a standard keyword bulk sheet
Note: For Channel Connect, please note that the directory of where the file should be dropped is essential. For example, each type of Channel Connect files i.e. Criteo , Gemini etc. will have their own FTP directory folders and the corresponding files need to go into the right folder to be imported correctly.
Note: Your file name should not reference another object level or feature other than what's listed before the underscore ('_'), as the platform will not ignore what comes after the underscore. For example, a file name of "campaignHeld_Auto assign values to dimensions" will result in the platform treating the file as an Actions By Dimensions upload, rather than a campaign upload.
