Follow

eBureau: Lead Scoring

ActiveProspect partners with eBureau to offer their predictive analytics and information solutions directly through LeadConduit.

This integration enables LeadConduit customers to perform lead qualification against scores and information provided by eBureau, returning a range of data such as eScores and eVerify messages. This information can be used to effectively prioritize and qualify a lead.

What you'll need to get started:

  • eBureau account - This is a Standard Integration
  • User ID - The User ID that will be used to transact with the eBureau service
  • Password - The password for the eBureau User ID
  • SID - Security Identifier

Lead Specific Required Fields:

  • First Name
  • Last Name
  • Address 1
  • City
  • State
  • Postal Code

 

Adding and Configuring eBureau

From your selected Flow, choose Edit, scroll to the bottom of the Steps tab, select the Add Enhancement option, and search for/scroll to eBureau and select.

Next, you'll need to provide some information so LeadConduit can communicate with eBureau.

From within the eBureau UI, you'll need to find the following:

  • User ID - The User ID that will be used to transact with the eBureau service
  • Password - The password for the eBureau User ID
  • SID - Security Identifier

Once you've found these three items, expand the eBureau step, click the Edit Field Mappings button, then copy+paste the into the appropriate rows.

Click Ok and Save the flow.

The rest of the required fields you collect with the lead will automatically be sent to the eBureau API and you don't need to manually map them in the field mapping section.

Congrats!

//--//

 

Advanced Configuration Options

The following Optional fields are also supported:

  • subuser_id - The purpose of this id is to separate billing and identify sub-users (a branch, region, store, etc.)
  • source_id - A Source ID (order type, delivery type, channel, etc.) for reporting purposes
  • group_id - A Group ID (order type, delivery type, channel, etc.) for reporting purposes.
  • account - A unique transaction identifier for reporting purposes
  • email - The Email address
  • phone_1 - The phone number
  • ssn - The social security number of the consumer
  • dob - The date of birth. Allowed Format: YYYYMMDD
  • ip_address - The IP address of the computer the consumer
  • company.name - The Consumer Employer Name
  • company.address_1 - The Company address
  • company.city - The Company address city
  • company.state - The Company address state
  • company.postal_code - The Company address postal code
  • company.phone - The Company phone number
  • date - The date of the transaction request. Allowed Format: YYYYMMDD
  • time - The time of the transaction. Allowed Format: HH:MM:SS
  • pay - The net pay per check of the consumer who is the subject of the transaction. Allowed Format: Integer
  • interval - The pay frequency. Allowed values: 
    • w (weekly) 
    • bi (biweekly)
    • (monthly)
    • sm (semimonthly)
  • type - The payroll type. Allowed values:
    • dd (direct deposit)
    • pc (paper check)
    • bf (benefit)

These field values are available from the Right-Hand menu in the eBureau field mapping section. 

Interpreting the Results

What does a success response represent?

A success response will mean that the API call to eBureau returned.

A Success means the API call to eBureau was successful and data was returned and successfully appended to the lead.

What does a failure response represent?

A Failure means the API call to eBureau was successful, but no data was returned. This is equivalent to a no match transaction.

What fields does the integration return?

  • Outcome - Integration outcome (success, failure, or error)
  • Reason - If outcome is error or failure, the reason
  • eScore Name - The eScore name
  • eScore Range - The range is the minimum and maximum values for the eScore (or Estimated Income).
  • eScore Score - The Estimated Income value
  • eScore Adjusted - This is returned if an adjusted eScore is provided
  • Messages - This is an array of the message block returned by eBureau
  • Status  Result - Status of the request made
  • Status Count - An internal eBureau value that can be ignored
  • Status UUID - A unique value, assigned by the eBureau system, for the transaction
  • Status Latency - The length of time it takes eBureau to process the transaction measured from receipt of the transaction by eBureau to when eBureau initiates the return of the results

//--//

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

You must be logged in to comment.