Release Notes

SheerID release notes & announcements. Watch this space for the latest updates.

September 5 Release

In This Release

Security Upgrades for MySheerID

We have made several security upgrades to MySheerID. These upgrades focus on security for SheerID users and your customers’ data.

Security Updates:

  • Deleting a user from an account will immediately disable them.
  • Changing a user’s permissions will immediately take effect and prompt a re-login.
  • Login failure handling has been improved.
  • We no longer store any user information in the browser’s local storage.

Addition of Conversion Tracking scripts to MySheerID

It is now easier for you to integrate Conversion Tracking because we include it directly in the MySheerID installation experience. This feature allows you to populate your ROI Impact Dashboard with sales data and quickly see the ROI of your SheerID programs.

Install program

How it works:

  1. Copy the installation code with the conversion tracking script in order to store the verificationId for any verification in a first-party cookie.
  2. Copy the conversion tracking script and add it to your post-conversion page to read the verificationID from the cookie and send it to SheerID with the spending amount of that verified person’s transaction.
  3. Once in place, you can view the revenue generated by your program in the ROI Impact Dashboard.
Note: At this time the ROI dashboard needs to be explicitly added by SheerID. If you have added tracking, make sure to contact Support with a request to add the dashboard to MySheerID.

Additionally, there are JavaScript and REST API methods that do not utilize a cookie. You can learn more about all these methods in our Conversion Tracking tutorial.

August 14 Release

In This Release

Download large verification reports in MySheerID

In prior releases, you may have experienced a timeout when dowloading reports with large amounts of data. We have addressed your feedback by implementing the following two enhancements:

  1. On the back end, we will no longer timeout your session while a report is downloading, no matter how long it takes.
  2. On the front end, you will see the following spinner as a visual cue that the report is being generated:

Generating Report

One the report is finished generating, it will trigger the download of the finished CSV file.

Note: We recommend selecting shorter date ranges if you think large amounts of data will be included.

August 7 Release

In This Release

Custom campaign analytics tracking

Many of our customers want to tie the performance of verification programs back to the marketing campaigns that drove users to them.

For example, when a user clicks a link in a marketing email or Facebook ad, that link contains a campaign parameter (e.g. utm_campaign). Passing this value through to the verification report helps you identify the best performing campaigns and optimize your marketing efforts.

Now you can track campaign and other custom metadata in MySheerID, without needing to rely on our Professional Services team. Define the metadata to be tracked along with your verifications, such as the utm_campaign or any key-value pair that you wish to include in your reporting.

In your program’s settings page, turn on metadata options and define the keys you wish to track. When calling our verification URL, simply pass us your defined key with the appropriate value as a parameter, e.g., https://services.sheerid.com/verify/<YOUR_PROGRAM_ID>/?utm_campaign=back_to_school and we will store the data alongside the SheerID verificationID for reporting purposes.

Later, you can access this data by downloading a verification report and/or using our API to get the verification metadata.

In the example of passing in utm_campaign, you can download the verification report and run a pivot table to see which traffic sources are yielding the most approved verifications. In the example of passing in a userID, you can also set up a webhook; when that webhook URL is notified of an approved verification, you can query our API to ask for the userID of that approved consumer.

Metadata

Metadata Example

Smart fraud prevention settings for new programs

All programs made in MySheerID going forward will have a default verification limit to ensure smart fraud prevention is in place. The new setting defaults to 1x every 180 days, meaning an individual may only redeem your offer once in a 180-day period.

Default Verification Limit

July 25 Release

In This Release

New, simplified, powerful reporting endpoints

Now you can generate a verification report which can be downloaded later, check the status of the report, and retrieve it when it is ready.

Use the Generate a verification report endpoint to define the start and end dates for the report:

POST /rest/v2/report/verification HTTP/1.1
Content-Type: application/json

{
	"startDate": "2019-08-06",
	"endDate": "2019-08-08",
	"format": "CSV"
}

Use the status endpoint to retrieve your verification status:

GET /rest/v2/report/{reportId}/status HTTP/1.1
Authorization: Bearer YOUR_ACCESS_TOKEN

And finally, retrieve data for a previously-generated report in CSV format:

GET /rest/v2/report//report/{reportId} HTTP/1.1
Authorization: Bearer YOUR_ACCESS_TOKEN

Update verification metadata endpoint

Now you can update verification metadata for an ongoing verification.

PUT /rest/v2/verification​/{verificationId}​/metadata HTTP/1.1
Authorization: Bearer YOUR_ACCESS_TOKEN

{
  "key": "value",
  "anotherKey": "another value"
}

Capture IP address in a verification

ipAddress is now an optional field in some verifications such as Submit Student Verification. You only need to provide an ipAddress in situations where the HTTP requests do not come directly from the end user.

POST /rest/v2/verification/{verificationID}/step/collectStudentPersonalInfo HTTP/1.1
Host: services.sheerid.com
Content-Type: application/json

{
	"firstName": "Jane",
	"lastName": "Ivy",
	"birthDate": "1990-01-01",
	"email": "jane@albanylaw.edu",
	"ipAddress": "204.120.0.15",
	"organization": {
		"id": 4597,
		"name": "ALBANY LAW SCHOOL"
	}
}

July 10 Release

In This Release

Major update to email notifications in MySheerID

This release marks a major upgrade to approval and rejection emails sent through programs created in MySheerID. Emails now:

  • Have fully editable text
  • Inherit theming from the forms (logo, font, color choices)
  • Boast new, default copy reflecting best practices
  • Include a button with redirectUrl (if specified)

This change is available on all new MySheerID programs going forward.

Here is an example of the new UI:

Emails

Compared to the previous experience:

Previous Email UI

Many of our customers ask permission to market to verified consumers on their verification forms, providing a checkbox to opt in. Some of you want to make consent to future marketing a condition of granting access to a promotion.

Today, we added an advanced setting for Marketing Consent, giving you the ability to:

  • Enable a marketing consent checkbox in your verification form
  • Make it an optional or required field
  • Edit the exact language the consumer is agreeing to

This feature is available with all new MySheerID programs created after this release, under Program Settings »» Marketing Consent.

Marketing Consent Card

See Marketing Consent to learn more.

Verifications searchable by phone number

We enhanced the customer service search tool within MySheerID to enable search on phone numbers. This adds to pre-existing search on name, email or verificationID. This is available on all programs (0.5 and 2.0, new and existing) for which a phone number is collected:

Phone Search

Change to minimum age for verification

In order to comply with EU and California regulations, we are eliminating verification for people under age 16. This is a platform change and affects all segments and all geographies. For customers using our master templates and hosted solutions the exact user experience will vary but either the consumer will not have an option to choose a birth year outside the allowable range, or see an error message if they do. For API customers, the APIs will return an error if a birth date for a person under 16 years old is submitted.