ARIVE Integration

Overview

Experience.com’s ARIVE integration solution allows enterprise customers to automatically send surveys to loan customers during and after key moments in the lending/homebuying process. The ARIVE integration allows you to:

• Ingest loan transaction data from ARIVE into Experience.com.

• Map ingested data to campaigns within the account

• Automate campaigns and surveys to loan customers based on role, transaction type, or location.

Transactions ingested from ARIVE into the XMP are labeled as verified transactions.

Prerequisites for Configuring an ARIVE Integration

Several prerequisites must be met before Experience.com can access and ingest transaction data from ARIVE for a specific organization. ARIVE uses Zapier’s technology to integrate with Experience.com and other integrations. To integrate with ARIVE via Zapier, you will need:

• A Zapier Starter package plan ($19.99/mo)

• An API key from your organization’s ARIVE instance

• An API key from your account’s ingestion set up in the XMP

Obtain an API Key from your Account’s Ingestion Setup

1. To create a new configuration, navigate to the Account Settings page and open the Ingestion Settings. Find and select ARIVE, and then click the blue “New Connection” button.

Open

2. Once the connection is created, some information is required to verify and activate it.

   1. Give the connection a name.

   2. Enter a point of contact for the integration. This is someone that Experience.com may contact if an ingestion error occurs or if a re-configuration is needed for the integration.

Open

3. Once a connection name and point of contact have been established, click the blue Verify & Connect button.

4. When the ARIVE configuration has been verified and connected, click back into it to access the API Key.

   1. Locate the API Key and click the copy button to copy it to your computer’s clipboard.

Configuring the ARIVE Integration

To configure the integration between ARIVE and Experience.com, you will first need to create a Zap within Zapier. Then, a filter should be added so that transactions are only ingested when a loan status is funded. Once a filter has been added, a zap can be created for Experience.com to retrieve the information. Finally, the data from ARIVE has to be mapped to fields available via Zapier. Once the fields are mapped properly, the connection can be finalized.

Take the following steps to get started:

Create an ARIVE Zap in Zapier

1. Log in to Zapier, then click Create Zap.

2. Click 1. Trigger to start building the Zap.

steps need to be entered here for connecting with ARIVE in Zapier, as it is not a public app, and an invite link is required in order to access the private app.

Add a Filter to the Zap

7. Click 2. Action, then search for and select Filter (only proceed when a condition is set).

8. Under the Filter setup & testing section, set the condition to only continue if the field loan status equals funded.

Create an Action for Experience.com to Retrieve the Data

9. Once the condition has been set, Add another action by clicking the + button below the filter.

10. Search for and select Experience.com. For the event, enter Retrieve LendingPad Transactions.

11. Click Continue. When the Account menu expands, click Sign in to log in to your Experience.com account.

Map LendingPad Fields to XMP Fields

12. When the Action menu expands, each field from LendingPad needs to be mapped to an Experience.com field. For each field provided on the screen by Zapier, type or insert the corresponding field from LendingPad:

13. When the fields have all been mapped, click Retest & Continue to test that data is pulling into all of the places it should be.

14. Finally, click Done Editing, then turn the Zap on with the toggle at the top of the page.

Once the Zap is enabled, data will be pulled in from LendingPad and into Experience.com for transaction ingestion. Because of the API connection within the integration, data is transferred more often than on a daily basis. Transactions will typically be processed within hours of the status update.