Activate - FAQ

If you are an existing customer the user interface is available as soon as your contract begins. Simply ask your Customer Success Manager or implementation manager to create an account for the users who require access.

An Activate instance is the combination of:

• A monitoring file

• Activate configuration (data points, journeys, delivery frequency)

• Integrations

If more than two monitoring files are being used, multiple Activate instances will be created to house each monitoring file.

Up to 10 instances can exist at one time. If more than 10 Activate instances are needed, please reach out to support@jornaya.com

A customer list can be provided to Jornaya through our user Interface via several different methods.

Please see the Connect a Data Source to Jornaya article under the Activate: Getting Started section of our Help Center.

Jornaya Activate leverages the identifiers in a customer file (hashed email addresses, hashed phone numbers, postal addresses, and LeadiD tokens) to monitor those customers exhibiting shopping behavior across our data network.

When we witness a consumer in your file shopping in our network, we append our consumer-level behavioral data points to the consumer record in your file and provide that data back to your based on your Activate instance setup.

The behavioral data points are based on how often we saw the consumer shopping over and when we saw the consumer shopping over the past 1 & 7 days.

The in-market rate represents the number of consumers Jornaya has seen shopping over the past year across any major life purchase journey.

There are many ways you can increase your in-market rate:

• Provide additional identifiers for the consumers you want Jornaya to analyze. For example, if you initially only provided us 1 phone and 1 email per consumer but have 2 phones and 2 emails per consumer, provide another Monitoring File that includes the additional identifiers you have available.

• Upload a different segment of your consumers. These could be consumers who are nearing the end of their term or have exhibited a lower interaction rate. These consumers may exhibit in-market behaviors if they are considering switching to a different provider.

• Place Jornaya’s Create code on your site. By placing our code on your site, we are more likely to connect your prospects and customers to our network or data. Jornaya customers who have our JavaScript code implemented on their own and operated websites typically see a higher in-market rate for their prospects and customers. Here you can find directions on how to get set up with creating LeadiDs.

• Reach out to VMSCustomerSuccess@verisk.com and we can provide personalized recommendations on how to improve your match rate.

The file upload feature in the user interface is HTTPS which runs over an SSL/TLS connection. The encryption strength is equivalent to our SFTP. HTTPS relies on certificates that are required to be renewed periodically and resigned by the signing authority (all handled automatically), which makes this approach slightly more secure than traditional SFTP as SFTP runs over an SSH connection that only relies on keys. Transfers over HTTPS are based on authentication tokens - there are no usernames or passwords stored.

The maximum file size of a monitoring file uploaded using the file upload feature is 1GB.

Any monitoring files larger than this should be posted to Jornaya through the API endpoint.

The file upload feature allows users to upload a monitoring file with unhashed PII in the email and phone fields and automatically hashed them when selected.

In this case, the PII only exists client-side in the user’s browser. We never send the PII server-side. The only exception to this is if raw PII is included in pass-through fields, which we strongly suggest you not include PII in pass-through fields.

Jornaya Activate delivers signal data each morning by 8 AM EST.

A monitoring file can be replaced as often as necessary barring any contractual limitations.

Please note that our service is not additive and we only monitor one file at a time. Therefore if you have new/more customers to add to your list you must upload a new comprehensive list, not just another file with the newest customers.

For example, if you have 75,000 customers on January 1st and by February 10th you have 10,000 more, the new file would need to have 85,000 records, not just the new 10,000.

Activate supports full file replacements which can be handled by editing an activate instance.

Click into an existing activate instance and either upload a new monitoring file or delete the existing monitoring file integration and set up a new one.

Hashing is the process of generating a value from text input using a one-way algorithm that enables the security of consumer information and data.

To process a customer file for Jornaya Activate, the consumer data must be hashed using MD5 or SHA256 methodologies.

Please see the Jornaya Activate Customer File Specification and Hashing FAQs, Tips, and Examples for more information on the data formatting

Jornaya recommends daily monitoring with the 1-day & 7-day data points, which would require you to select each day of the week for daily monitoring in your instance run settings.

If you only want to receive data once a week, you should only select the 7-day data points within your instance. Selecting the 1-day & 7-day data points with a once-per-week monitoring setting will result in your file only including events in the past 1 day once per week.

Additionally, only selecting 2-6 days will result in missing out on actionable Activate data, depending on the selection.

Customers must opt-in to the email notification for Activate validation.

To do this, click the Account dropdown at the top right of the myJornaya homepage and select “Notifications.” This will open a modal where you can select a checkbox to receive Activate validation email notifications.

By selecting this box, the email address for the user that is logged into the account will be enrolled in validation email notifications for all Activate instances within the account. If other users within your organization need to receive this alert, they will need a myJornaya user account and will need to opt in to receive these alerts.

See the Activate Monitoring File Validation & Notifications article for complete information

We leverage Amazon Web Services (AWS) to enable cloud storage and processing of Jornaya data in a reliable and secure manner.

All direct customer interaction with the Jornaya Activate process happens through the Jornaya User Interface, along with endpoints to post data to get data from from Amazon S3. The following details the different steps of the process, and security measures taken therein.

CREATING THE MONITORING FILE

• Our Customer File Specification details the security requirements of Activate

• Activate requires customers to leverage anonymous identifiers, such as a recordid

• Any identifiers, such as phone number and email address, must be hashed

• Optionally, postal addresses can be included within the monitoring file, which are standardized and hashed by Jornaya. The original postal addresses are held in a
  secure S3 bucket with server-side encryption for 4 days after a successful output file is produced, and then permanently deleted. The Activate product only uses and can work with the hashed version of the postal address.

UPLOADING THE MONITORING FILE TO JORNAYA

• Customers log in to the Jornaya User Interface using the email address and password they’ve chosen

• The file can be uploaded through a file upload wizard, posted through an HTTPS endpoint, or pulled via an automated integration

• Customers can choose to pre-hash email addresses and phone numbers prior to sending the file or use the file upload wizard or automated integrations to hash this data for them.

• If you prefer, Jornaya also supports the use of public key authentication

VALIDATING YOUR MONITORING FILE

• Jornaya validates uploaded files have been properly hashed using MD5 or SHA256

• If PII is detected the file will fail validation and you will be alerted via email

• Files are encrypted at rest, meaning no one has access to your data within AWS

• AWS Key Management Service is used by Jornaya to manage encryption keys

THE ACTIVATE PROCESS

• Your file is posted directly into a secure Amazon Simple Storage Service

• Your file is processed to match the anonymous identifiers to in-market behaviors

• An Activate response file is generated and moved into Amazon Simple Storage Service

• The file can be accessed via direct download through the Jornaya User Interface, File Download Endpoint, or through an outbound integration

JORNAYA INTEGRATIONS

Customers can integrate Jornaya data directly with their marketing platforms to automate the process of uploading a monitoring file or downloading the response.

To support the integration, the customer must allow Jornaya to authenticate with their platform, which allows us to read and write data directly to the chosen system.

Additionally, the customer will go through a data mapping process to indicate which fields to pull data from and establish the fields for Jornaya data to be delivered