Skip to content

Plan an Amazon S3 file import

If you need to load a large customer population from files in Amazon S3, contact your JustAI team before building the export. File imports need a customer-specific assessment and setup. Your JustAI team must confirm whether your requirements can be supported and provide the agreed format and procedure.

For profiles you can send now, use the Identify API, directly or through Hightouch. For a small list, use CSV upload.

Share these requirements with your JustAI team:

  • The number of profiles and the approximate size of the export.
  • The JustAI environment that should receive the profiles.
  • Your stable user ID and the attributes you need, including email. Use the same ID as your Identify and Track calls.
  • Whether you need an initial snapshot, ongoing updates, or both.
  • How quickly updates need to appear and who will monitor them.
  • How corrections, blank values, deletions, and consent changes should work.

Before you export files, get confirmation of the supported file format, column types, folder layout, completion signal, update rules, delivery schedule, and verification steps. Do not assume that another customer’s import settings apply to yours.

Grant access only after your JustAI team confirms the import and provides the identity and permissions it needs. Restrict access to the agreed bucket and prefix, and give it only the permissions required for the agreed operation. Review encryption requirements with your AWS administrator.

Never send AWS access keys, warehouse passwords, or private keys in a ticket, email, or screenshot. Use synthetic data for samples until your teams agree on a secure transfer procedure.

Contact your JustAI team before planning an import of past events. Confirm availability, how the events would be used, and how you would verify the result before exporting or sending them.

Do not replay past events through the Track API. A matching event received after a journey is published can start, advance, or end that journey, regardless of its timestamp. An old timestamp does not make a Track request safe for historical loading.

  1. Get the import procedure and acceptance checks confirmed by your JustAI team before granting access or enabling an export.
  2. Test the agreed procedure with synthetic profiles in the intended environment.
  3. If the test includes a profile load, compare the saved user IDs, email addresses, and attributes in Users or the Profiles API with your test records.
  4. Confirm the result with your JustAI team before sending a full population or scheduling ongoing deliveries.

A successful upload to S3 confirms only that the files arrived in S3. It does not confirm that JustAI accepted or loaded them.