Set up Array credit check

This article shows how to connect Array (Array.com Offers Engine) for soft credit inquiry and offer qualification, turn it on for a campaign, and use the results in filters or reject rules.

Array runs during the credit-check stage of lead ingest. It can enrich the lead only, or reject leads that fail your rules.

Prerequisites

• An Array.com account with Server Token, App Key, and Product Code
• The Integrations feature on your Datahubb plan
• A campaign that collects US leads with the fields Array needs (name, address, DOB, SSN, email, phone, and a consent / page URL)

Configure Array globally

1. Open Integrations in the sidebar.
2. Click Array.
3. On Credentials, enter:
   • Server Token
   • App Key
   • Product Code
4. On Settings, set:
   • Environment — sandbox while testing, production when live
   • Timeout — start at 10–15 seconds (credit pulls are slower than most validators)
5. Review field mapping if shown. Defaults map common lead fields to Array (first_name → firstName, address → address.street, state normalized to a 2-letter US code, page_url → consent URL, and so on).
6. Save.

Expected result: Array shows as configured and is available to assign on campaigns.

Enable Array on a campaign

1. Open the campaign → Integrations tab.
2. Find the Array card and toggle it ON.
3. Optional: click Override Settings to change mappings for this campaign only.
4. Save.

Map results into enriched fields

Array returns boolean result keys (for example a credit-score band) plus an offerId when the lead qualifies. HTTP 204 means not qualified (qualified = false).

1. In global or campaign Override Settings, open Result Mapping.
2. Map Array keys to named fields (for example a true creditScore_581_590 band → _array_credit_score = 581).
3. Optional: use pattern mapping for numeric ranges embedded in Array key names.
4. Save.

Those mapped fields become available in filters, distribution, and postback tokens after a successful pull.

Optional: reject unqualified leads

1. Add Credit Check Integration Rules for Array.
2. Example REJECT rule: qualified is false.
3. Or REJECT / ACCEPT on specific results.* keys or offerId.
4. Save and send a test US lead.

With no REJECT rules, Array enriches only and the lead continues.

Verify it worked

1. Open Integrations → Array → Usage Log.
2. Confirm a recent call with a success response and reasonable latency.
3. Open the test lead and check enriched data for your mapped _array_* fields.

Troubleshooting

• Array never runs — campaign toggle is off, Integrations feature is missing, or the lead country is not US.
• Timeouts — raise Timeout; credit pulls often need more than a few seconds.
• Missing enriched fields — result mapping is empty or the Array key names do not match what Array returned.
• Leads rejected unexpectedly — review Credit Check Integration Rules; remove or loosen REJECT conditions while testing.