How to Upload files via Direct Upload

Below are the instructions on how to upload files for the first time.

1. Go to the Integration tab in Ignite

2. Click on ‘Get Started’ button

3. Choose ‘Direct Upload’ and select ‘Continue’

4. Name your workspace - name it something that helps you identify the data that will be loaded in this space

5. Select ‘CRM Insights’ and click continue

6. Drag and drop or select your files you want to upload, follow the formatting guidelines here

7. The hashing (if required) and validation will start

8. Once your files have been validated and hashed (if required), you will see messages alerting you if they passed validation, had warnings, or had errors.

1. 1. If there are warnings, your file will still process but there may be records that are skipped

   2. If there are errors, your file will not process. Errors will need to be corrected and the file reuploaded.

9. Choose the files you want to continue with (files that failed validation cannot be processed) and click ‘Continue’

10. Your files will finish uploading and your insights will be available

Below are the instructions for adding files into an already created workspace.

1. Go to the Integration tab in Ignite

2. You can click ‘Add files’ on the Workspace tile

3. OR Click ‘View Workspace’

4. Then click ‘Upload files’

5. Drag and drop or select your files you want to upload, follow the formatting guidelines here

6. The hashing (if required) and validation will start

7. Once your files have been validated and hashed (if required), you will see messages alerting you if they passed validation, had warnings, or had errors.

1. 1. If there are warnings, your file will still process but there may be records that are skipped

   2. If there are errors, your file will not process. Errors will need to be corrected and the file reuploded.

8. Choose the files you want to continue with (files that failed validation cannot be processed) and click ‘Continue’

9. Your files will finish uploading and your insights will be available in 2-3 days.

 

Potential Warning Messages
You can still process files that have warnings

1. Segment(s) too small 

      a. Segment(s) have fewer than the recommended minimum of 20k records which could affect insightability

      b. Recommended action: Combine smaller segments or add more IDs to meet the recommended 20k minimum.

2. Records are missing IDs in the ID column

      a. A number records are missing IDs. These records are skipped during processing.

      b. Recommended action: If you know the IDs that were missing add them and upload the corrected file. If not, no action is needed as these rows are skipped during processing.

 

3. Records are missing Group=Segment pairs

      a. A number of records are missing a Group=Segment pair. These records are skipped during processing.

      b. Recommended action: Review your file and identify the records that do not have a Group=Segment pair in either the ‘Add’ or ‘Remove’ column and update to include the pair.

 

4. Records do not have valid Group=Segment pairs

      a. A number of records do not have a valid Group=Segment format. These records are skipped during processing.

      b. Recommended action: Review your ‘Add’ column and ensure that each record has a correctly formatted Group=Segment pair, (ex. Customers=Purchasers). Pairs cannot contain commas, pipes, or equal signs within the group or segment names (ex. Customers=Purchasers, Q1)

 

5. Records have a mismatch between the ID Type and ID value

      a. A number of records have an ID Type does not match the ID value. (ex: ID Type=HMMD5 but ID is actually a SHA2)

      b. Recommended Action: Review your file and ensure that your IDs match the ID Type listed in the ID column.

           i. HEMMD5: 32-character hexadecimal number. For example, ec55d3e698d289f2afd663725127

           ii. HEMSHA1: 40-character hexadecimal number. For example, A94A8FE5CCB19BA61C4C0873D391E987982FBBD3

           iii. HEMSHA2: 64-character hexadecimal number. For example, 051f26bd6cde782239bf52e56854d3feeca75ae5a84508d1ff9a1868ba167ee5

 

6. Invalid ID type

      a. A number of records have an invalid ID type.

      b. Recommended action: Update the ID Type to be HEMMD5, HEMSHA1, HEMSHA2, MAID, or IP based on the type of ID you have in the ID column.

 

Potential Error Messages
You cannot process files that have error messages

1. Records are missing IDs in the ID column

      a. All records do not have an ID in the ID column

      b. Recommended Action: Add an ID for each record.

 

2. Records are missing Group=Segment pairs

      a. All records are missing a Group=Segment pair in the ‘Add’ column

      b. Recommended action: Update the ‘Add’ or ‘Remove’ column to include at least one Group=Segment pair for each record

 

3. Records do not have valid Group=Segment pairs

      a. All records do not have the group=segment formatted correctly

      b. Recommended action: Review your file to ensure that each record has a correctly formatted Group=Segment pair in either the ‘Add’ or ‘Remove’ column, (ex. Customers=Purchasers). Pairs cannot contain commas, pipes, or equal signs within the group or segment names (ex. Customers=Purchasers, Q1)

 

4. Records have a mismatch between the ID Type and ID value

      a. All records have an ID Type does not match the ID value. (ex: ID Type=HMMD5 but ID is actually a SHA2)

      b. Recommended Action: Review your file and ensure that your IDs match the ID Type listed in the ID column.

           i. HEMMD5: 32-character hexadecimal number. For example, ec55d3e698d289f2afd663725127

           ii. HEMSHA1: 40-character hexadecimal number. For example, A94A8FE5CCB19BA61C4C0873D391E987982FBBD3

           iii. HEMSHA2: 64-character hexadecimal number. For example, 051f26bd6cde782239bf52e56854d3feeca75ae5a84508d1ff9a1868ba167ee5

 

5. More than 2,000 Group=Segment pairs

      a. Resonate only allows up to 2,000 segments per workspace, this file contains more than the allotted 2,000 Group=Segment pairs.

      b. Recommended action: Review segmentation and consider rolling the segments up to another level to reduce the number of segments.

 

6. Invalid ID type

      a. All records have an invalid ID type.

      b. Recommended action: Update the ID Type to be HEMMD5, HEMSHA1, HEMSHA2, MAID, or IP based on the type of ID you have in the ID column.