If you are going to import a file via FTP to upload Registrations into Aimbase, you must follow this file format guide.
Use an excel spreadsheet, but be sure to save it as a .csv file. The field name will be the column headers in your file and below them in each column, you will have a value. For example, PrchaseDt is the Field Name and the Value is below it in YYYYMMDD format.
.png)
You can add as many registrations to one file as you want. Each individual registration will be a row.
Once you have completed your file, go to our instructional guide on how to use a FTP software to upload your file successfully.
| Field Name | Required | Format | Description |
| ACTION | X | “A”, “E”, "O" | Specifies action to be performed on data row; A= new registration, E= End record, designates end of file. O= update existing record. |
| LANGCODE | X | “EN” | Define the language the survey will be sent in by using an accepted language code |
| SRVYTYPE | X | “R” | Must be set to ‘R’ for registration survey. |
| HIN | X | HIN/Serial of product; number must be unique, no two products are given the same HIN. | |
| PURCHSDT | X | YYYYMMDD | Date the product was purchased; this is the date that will be used to trigger survey activity |
| DELIVERYDT | YYYYMMDD | Date the product was delivered | |
| REGTYPE | Registration Type Code | ||
| REGSOURCE | Registration Source Code | ||
| DLRNUMBR | X | Dealer Number of dealer that sold the product to the customer, main dealer number prefix; used in combination with dealer location number to uniquely identify a dealer; if Dealer Number is not provided, reporting will not be available at the dealer level | |
| DLRLOCTN | Location number of the dealer that sold the product; sub-dealer number, used in combination with dealer location number to uniquely identify a dealer; used only if a dealer has sub-locations that need to be identified separately from the main location | ||
|
MODELBRD |
X | Identify Brand Name. |
|
| MODELCOD | X | Manufacturer’s model code of the product purchased; reference Product/Model File Format information available in the FTP document on help.aimbase | |
| MODELYER | YYYY | Year of the model (XXXX format) | |
| CFSTNAME | X | First name of the purchaser | |
| CLSTNAME | X | Last name of the purchaser | |
| CTITLE | Title of the purchaser | ||
| CADDRES1 | X | Customer Address 1; Max length 256 characters | |
| CADDRES2 | Customer Address 2; Max length 256 characters | ||
| CCITY | X | Customer city | |
| CSTATE | Customer state | ||
| CPSTCODE | US 5 or 5+4 zip code, or, Canadian 6 digit code | Customer postal code | |
| CCOMPNYN | Customer company name | ||
| CCOMPNYT | Customer company title | ||
| CCOUNTY | Customer county | ||
| CCOUNTRY | X | Customer Country; use ISO 3166 two-digit country codes; ISO 3166 two-digit country codes are available below | |
| CHMPHONE | Customer home phone | ||
| CWKPHONE | Customer work phone | ||
| CFAX | Customer fax | ||
| CEMAIL | Customer email | ||
| CNOEMAIL | “YES”, “NO” | Customer does not want to be contacted via email | |
| KEYID | Integer value | Action code “S”, ID of the survey key printed on a survey that the manufacturer has sent to consumer. Must match KEYID values reserved and sent to the manufacturer. Survey Key Reservation File information available below. | |
| CNOMAIL | “YES”, “NO” | Customer does not want to be contacted via mail | |
| CNOPHONE | “YES”, “NO” | Customer does not want to be contacted via phone | |
| SENDSRVY | “YES”, “NO” | Override to prevent survey from being sent to owner | |
|
ACCOUNTID |
Company External ID | ||
|
CEXTERNALID |
External ID | ||
|
SUBSTATUS |
Subscriber Status | ||
| Engine serial number 1 | |||
| Engine Brand 1 | |||
| Engine HP 1 | |||
| Engine Serial Number 2 | |||
| Engine Brand 2 | |||
| Engine HP 2 | |||
| <Custom Field Name> | Registration file supports custom fields. Any short name values not matching the standard field list will be created as a custom field. We support custom short field name up to 50 characters and values up to 2,048 characters. |