Reltio Connect

Hello:

We are seeing some discrepancies with CASS attribute values for specific addresses when we use the "embedded" Loquate system and an "External" Loquate CASS Run.

Example:

External Loquate returns VACANT = Y
Internal Loquate returns VACANT = N
Smarty Streets (our go to tie breaker for address) returns VACANT = Y

The external Loquate run returns the following information in the PS3553 report:

3. Date of Database Product Used
        a. ZIP + 4 File : 06/01/2024
        b. Z4Change : 
        c. eLOT : 06/01/2024
        d. CRIS : 06/01/2024

Is there a way to see what USPS reference data the "internal" Loquate CASS Engine is using?

Hi James,

Reltio updated their CASS dataset on 24th. Can you recheck if the response now matches?

You can check version here https://cleanse.reltio.com/version

Thanks,

Saurabh 

Hello:

We are seeing some discrepancies with CASS attribute values for specific addresses when we use the "embedded" Loquate system and an "External" Loquate CASS Run.

Example:

External Loquate returns VACANT = Y
Internal Loquate returns VACANT = N
Smarty Streets (our go to tie breaker for address) returns VACANT = Y

The external Loquate run returns the following information in the PS3553 report:

3. Date of Database Product Used
        a. ZIP + 4 File : 06/01/2024
        b. Z4Change : 
        c. eLOT : 06/01/2024
        d. CRIS : 06/01/2024

Is there a way to see what USPS reference data the "internal" Loquate CASS Engine is using?