Activate Monitoring File Specification

09 Jul 2024
4 Minutes to read

Dark
Light

Activate Monitoring File Specification

Updated on 09 Jul 2024
4 Minutes to read

Dark
Light

Article summary

Did you find this summary helpful?

Thank you for your feedback

Format & Content

Item	Description	Notes
Type	CSV (comma delimited file) or Compressed CSV (.zip and .gz)
Name	CompanyName_YYYY_MM_DD.csv	Example: joesleadshack_2018_06_28.csv
Content	A header must be present as specified in the row below. Every other line will be CSV data that is delimited by a commaeven if the row is empty, and match the order of the headers.	No footers, blank lines, descriptions, etc can be present. Example: Arow with 1 email identifier and no other identifiers 11,,,,,55502f40dc8b7c769880b10874abc9d0,,
Header	The first line of the file with the column names to the right even if that row value is blank.	recordid,phone01,phone02,phone03,phone04,email01,email02,email03

Data Details

Field	Column Name	Description	Data Type	Format	Example Values	Integrations Support	Notes
RecordiD	recordid	Your unique record or customer identifier. The recordid will be included in the Activate Output so you can associate activity with consumers in your internal databases.	String	Alphanumeric, including hyphens and periods Max length 100 characters	12345678	Yes	The recordid will be included in the Activate Output so you can associate activity with consumers in your internal databases.
Phone Numbers	phone01, phone02, phone03, phone04	Non-numeric characters and spaces must be stripped from phone numbers prior to hashing	String	MD5 or SHA256 hash	2674607287	Yes	Phone numbers should be limited to 10 digits Additional or non-numeric characters stripped from phone numbers prior to hashing.
Email addresses	email01, email02, email03	List up to 3 email addresses associated with the customer record; one email per column, up to three.	String	MD5 or SHA256 hash	test@gmail.com	Yes	Must be in lowercase before hashing. Any leading or trailing spaces must be stripped before hashing.

Field

Column Name

Description

Data Type

Format

Example Values

Integrations Support

Notes

RecordiD

recordid

Your unique record or customer identifier. The recordid will be included in the Activate Output so you can associate activity with consumers in your internal databases.

String

Alphanumeric, including hyphens and periods
Max length 100 characters

12345678

Yes

The recordid will be included in the Activate Output so you can associate activity with consumers in your internal databases.

Phone Numbers

phone01,
phone02,
phone03,
phone04

Non-numeric characters and spaces must be stripped from phone numbers prior to hashing

String

MD5 or SHA256 hash

2674607287

Yes

Phone numbers should be limited to 10 digits
Additional or non-numeric characters stripped from phone numbers prior to hashing.

Email addresses

email01,
email02,
email03

List up to 3 email addresses associated with the customer record; one email per column, up to three.

String

MD5 or SHA256 hash

test@gmail.com

Yes

Must be in lowercase before hashing.
Any leading or trailing spaces must be stripped before hashing.

NOTE!

If no value exists, leave the field blank.
- Do not insert placeholder values like "null", "n/a", or any variation of these values.
- Any value that is not a hashed email or phone, a LeadiD token, or a postal address should be removed from the file before hashing and sending the file to Jornaya

Corresponding Identifier

To receive a monitoring response for each recordid, every row must contain at least 1 of the values below. Please see our Hashing FAQs, Tips, and Examples.

Hashed email
Hashed phone

NOTE!

If one of these identifiers is missing, that recordid will NOT be included in the Activate signal file.

Optional Identifiers

The fields below are optional identifiers that can be included that are defined below.

LeadiD token
Postal address

Optional Fields

Field	Column Name	Description	Data Type	Format	Example Values	Integrations Support	Notes
LeadiD Tokens	leadid01, leadid02, leadid03	If you are currently leveraging other Jornaya solutions and receiving LeadiD tokens, you can submit up to three LeadiDs for each recordid.	String	36-character GUID as created by a Jornaya campaign script	11111111-1111-AAAA-BBBB-CCCC-DDDDDDDDDDDD	Yes	LeadiD tokens should immediately follow the headers detailed above Header Names: leadid01,leadid02,leadid03
Postal Address	address01	If you have a postal address for the consumer you are monitoring, you can optionally add the address to the monitoring file.	String	Format	Examples	SFTP, API upload & File upload Integrations	We currently accept one postal address per record The full address must be included as a single value. Jornaya will standardize and hash the postal address on your behalf prior to being used in the product. There should only be 3 commas separating the data as a quick way to check
Passthrough Fields	N/A	Additional fields that your team would like to pass in conjunction with your recordids at the end of your file. These fields will be appended to your Activate results and could include	String	Any format accepted, EXCEPT unhashed PII	N/A	SFTP, API upload & File upload Integrations	Passthrough fields should immediately follow the headers detailed above. We accept any header names. Examples: recordids segment identifiers control group indicators

Field

Column Name

Description

Data Type

Format

Example Values

Integrations Support

Notes

LeadiD
Tokens

leadid01,
leadid02,
leadid03

If you are currently leveraging other Jornaya solutions and receiving LeadiD tokens, you can submit up to three LeadiDs for each recordid.

String

36-character GUID as created by a Jornaya campaign script

11111111-1111-AAAA-BBBB-CCCC-DDDDDDDDDDDD

Yes

LeadiD tokens should immediately follow the headers detailed above
Header Names: leadid01,leadid02,leadid03

Postal Address

address01

If you have a postal address for the consumer you are monitoring, you can optionally add the address to the monitoring file.

String

Format

Examples

SFTP, API upload & File upload Integrations

We currently accept one postal address per record
The full address must be included as a single value.
Jornaya will standardize and hash the postal address on your behalf prior to being used in the product.
There should only be 3 commas separating the data as a quick way to check

Passthrough Fields

N/A

Additional fields that your team would like to pass in conjunction with your recordids at the end of your file.
These fields will be appended to your Activate results and could include

String

Any format accepted, EXCEPT unhashed PII

N/A

SFTP, API upload & File upload Integrations

Passthrough fields should immediately follow the headers detailed above.
We accept any header names.
Examples:
- recordids
- segment identifiers
- control group indicators

Postal Address Continued

Postal Format

Must Not be hashed
Order: street, city, state, zip
Must be wrapped in quotes, allowing commas to separate the components of the address.
- NOTE!
  - If you are using Microsoft Excel to create/save your monitoring file, you do not need to add double quotes to the address01 values as the CSV created in Microsoft will do this automatically.
If an apartment or suite number is used within the address it must be included in the street address before the first comma.
A space can be included, optionally, after the comma. This will also work if there are no spaces.

Post Address Examples

Without Suite
- ”1001 East Hector Street,Conshohocken,PA,19428”
With Suite
- “1001 East Hector Street Suite 101, Conshohocken, PA, 19428”
No Space After Comma
- "1001 East Hector Street,Conshohocken,PA,19428"
Space After Comma
- "1001 East Hector Street, Conshohocken, PA, 19428”

Validation

Each time a new monitoring file is sent to Jornaya, the file will run through the Activate validation process to ensure the data provided passes our file specification. This process includes automated validation logic, where if 50% or more of the records pass validation and meet our file specification requirements we will continue to produce Activate data for those valid records; any records or values within a record that do not meet our file specification will be suppressed and not be used to produce Activate data. Any full records that have been suppressed will not be included in billing. The following invalid errors will be suppressed in this use case:

Duplicate recordids: the first one will be kept and the others will be suppressed
Incorrectly formatted hashed emails: we will suppress any email value that does not have a properly formatted MD5 or SHA256 hashed value will be suppressed
Incorrectly formatted hashed phone numbers: any phone number value that does not have a properly formatted MD5 or SHA256 hashed value will be suppressed
Incorrectly formatted LeadiD tokens: any inauthentic LeadiD token value will be suppressed
Incorrectly formatted postal address: any postal address that does not conform to our specification prior to the address being standardized & hashed will be suppressed

Send the File to Jornaya

Head over to our Connect a Data Source article for options and instructions on how to send the file to Jornaya!

Questions?

Was this article helpful?

What's Next

Activate Monitoring File Validation & Notifications

Table of contents