- All data sent should be wrapped in double quotes.
- Actual quotation marks should be denoted with two quotation marks (ex: """Hello"" World" to send "Hello" World value).
- Blank fields should be sent as blank, not as "" (interpreted as an empty string rather than a null value).
It is critical for
record_id's to be consistent across all flat files. (e.g. it is how we know things like categories/items are linked together)
record_idmust exist in the “Items” table.
UTC DateTime vs. UTC Date is an important distinction (e.g. if a field is listed as DateTime and only Date is provided, that row will be flagged as invalid and not imported).
While many fields are Optional, if the data is readily available it is highly recommended to provide to RS. (maximum data for AI to leverage in decision making).
If there is no data for a column, make sure the field comes over as blank. (e.g. as opposed to “NULL”, "0", “NO”, or "", as those can be interpreted as strings).
Each field provided has some type of impact on the final campaign performance of Cortex. These impacts are discussed in the “Context/Considerations” column found in the file schemas article, but please contact your technical onboarding contact at ReSci if you have any additional questions.
parent_record_idcolumns: Remember that the
parent_record_idreferenced in a row should always match another row’s
record_id. (e.g. parent items must exist as their own standalone row/entry).