Troubleshooting: Transmission problems when sending via FTP

Another common issue I see is a problem when trying to send a datafeed or product file via FTP protocol. This great for reasons of efficiently and the ability to automate the entire process, but there are several common issues that occur. Here is a quick checklist to run through when setting up or feeding in this method:

1. Make sure the CSE account is set up to accept via FTP. An engine will almost never automatically create an FTP location to send a product file to. At sign up, or after an account has been created, login to the control panel or account administration part of the CSE (typically this is done through a link on the home page for advertisers or merchants). Once logged in, there will be a way to update or change the method to submit products. This must be set to send or receive product information via FTP access.

2. Make sure the correct FTP username and password is being used. The FTP username and password is NOT the same as the account username and password issued upon sign up. The FTP username and password is typically very different and sometimes nothing more than a random series of numbers and letters. Some CSE’s require a request to be sent in, however, many will issue this information when an update method is chosen.

3. Make sure the path, account information and file name is correct. Path names are never quite the same, but verify all characters and spelling. There is a big difference between “ftp://ftp.uploads.google.com” and “ftp.uploads.google.com”. Check the full path extension and when copying and pasting password information, make sure not to include spaces. Once all this is verified, the last portion is the file name. Sometimes an engine picks up the file regardless, but otherwise an engine may be looking for a different file name. This can cause hours or possibly months of headaches if a merchant realizes down the road their products are not being updated because an old product file is still being used.

June 2nd, 2007