Each User Feed is uploaded as two .JSON files. The header file defines all fields that will be sent in the User Feed as well as the data types for each field. The data file contains all data for each user that you would like to send, such as id, birthday, gender, name, email etc. The naming convention for these two files is as follows:
Please ensure that a pair of header and data files always have the same timestamp, and that the timestamp (“YYYYMMDDHHMMSS”) is in UTC. Since the importer jobs are accessing these files as they are created, please ensure that they are temporary when you are creating on the FTP Server.
The number and types of attributes that you provide in the User Feed can vary according to your requirements. The only required field is the id. The id of one customer should be the same as the id you’re sending via the CrossEngage Web Tracking on your website or via the Public API (see here)
The 360° User Profiles are generated using data from the User Feed as well as the CrossEngage Web Tracking, this means that the id is the matching condition for each of your clients, so it is important that a user has the same id in your User Feed and the CrossEngage Web Tracking.
In case you use multiple stores with a separate id logic each, we can accomodate for that, too. For further information speak to your account manager.