Consumer | Business

Widgets

Widgets are two things: a front-end UI, and a configuration.

For example, a vehicle parts retailer may employ two widgets:

Widget #1: Public Service Discounts

  • Pre-Verification enables Military and First Responder
  • Post-Verification release a discount code to the customer
  • Installation provides HTML for installing a page to host the discount, linked from the footer

Customers find the verification page, verify and receive their discount code. This is the most standard and simplest integration for retailers. However, not all businesses are retailers, and some retailers may need to go further:

Widget #2: Pro Program

  • Pre-Verification enables a Automotive Mechanic only
  • Post-Verification tags the customer account as verified
  • Advanced → Status is set to Private

After verification, the business applies discounts automatically for verified Automotive Mechanics. Setting the Status to Private ensures only customers verifying from their internal customer account are able to complete verification.

Pre-Verification

What happens before verification: a simple Display Message to Applicants, along with who (Eligible Communities) can complete verification. Learn more about Pre-Verification.

Post-Verification

Determine the Action which occurs after a positive verification. This varies by business and use-case. Businesses can release discount codes (common for retailers) or select Custom for a customized experience. Learn more about Post-Verification.

Installation

Businesses can direct Applicants to their verification Widgets in a variety of ways. Ultimately, all Applicants arrive at a verification URL. VerifyPass provides several methods to direct Applicants to Widgets as quickly as possible. Learn more about Installation.

Testing

Every business should test their Widget(s) prior to going live. Learn more about Testing.

Advanced

Take more control of your Widgets in ways which are not typical for most businesses. Learn more about Advanced.

Limits

There is a maximum of 10 widgets per account. When used properly, a business should never approach this limit.

Why?

A widget is effectively an outcome.

For example, a business may offer 1) a public service discount, 2) a separate outcome (different value discount) for Seniors and Students, and 3) a separate value discount for industry professionals. This would total three Widgets on the aggressive end—and leaves plenty of room for development widgets.

Note that consolidating communities into fewer widgets does not change your capabilities.

  • Within Activity, you can still generate custom reports based on both Widget and Community.
  • Within our most popular Post-Verification Actions (Discount Code: Unique (Integration)), generated codes are always prefixed with a Community Key, even when multiple Communities are within the same Widget. This is often useful for measuring e-commerce performance within a Community.