Information about the requirements for your report suite before using Data Sources.
The following sections list constraints that apply to Data Sources and data imported into marketing reports and analytics.
Each calendar day you can upload data for 90 unique dates. If you exceed this limit, the upload will fail with an error message stating that you have ?exceeded the maximum unique days.
Only data with current or past dates can be imported. Do not attempt to use future dates in your Data Sources data.
All rows must have a date specified to enable report graphing capabilities. If a row does not include a date, Data Sources generates an error and rejects the file. The date/time format varies by data source type:
Full Processing Data Sources: Use the ISO 8601 date format of
YYYY-MM-DDThh:mm:ss±UTC_offset (for example,
2013-09-01T12:00:00-07:00), or Unix Time Format (the number of seconds elapsed since January 1, 1970).
Standard and Integration Data Sources: Use the following date format:
MM/DD/YYYY/HH/mm/SS (for example,
Data Sources supports multi-byte encoding. Data Sources attempts to detect the format of the incoming Data Sources file, and when necessary, converts it to a supported format. The following table lists common character formats and their support status.
Supported. The report suite used with Data Sources must have multi-byte character support enabled.
See New Report Suite in Help
|UTF-8 with Byte Order Mark (EF BB BF)||
Supported. This format is non-standard, though many Windows applications save in this format.
For example, WordPad saves in this format if you pick "UTF-8".
|ISO-8859-1 (aka Latin-1 or Windows-1252)||Supported. Microsoft Excel saves in this format when you pick a "tab delimited" export. The Report suite must be using the ISO-8859-1 locale.|
|UTF-16 Little-endian, with Byte Order Mark (FF FE)||Converted to ISO-8859-1 or UTF-8, as determined by your report suite configuration. Microsoft Excel saves in this format when you pick a unicode export.|
|UTF-16 Big-endian, with Byte Order Mark (EF FF)||Converted to ISO-8859-1 or UTF-8, as determined by your report suite configuration.|
|UTF-16 with no byte-order mark||Not supported.|
If you submit a UTF-8 or ISO-8859-1 file and your report suite is not configured to support it, one of the following happens: