Retreaver IQ by Audience Acuity

Quick summary: Retreaver IQ enriches inbound calls in real time by retrieving additional caller intelligence using the caller’s phone number through a verified database powered by Audience Acuity.

Overview

Retreaver IQ is a real-time call intelligence solution powered by Audience Acuity that enhances inbound calls with additional caller information before routing or reporting occurs.

When a call enters Retreaver, Retreaver IQ performs a lookup using the caller’s phone number against a verified TransUnion-backed database. The returned enrichment data can then be used throughout the platform for routing, RTB workflows, analytics, reporting, and webhook payloads.

Audience Acuity Website: https://audienceacuity.com/

Retreaver IQ Workflow Types

Retreaver IQ can be configured differently depending on how calls enter the campaign.

The setup requirements vary based on whether the publishers are:

• Sending a ping request first
• Sending the call directly first
• Using both methods on the same campaign

Option 1: Ping Request First (RTB Request / Postback Key Workflows)

Overview

This setup is used when publishers send a ping request before transferring the call.

Typically this occurs when using:

• Retreaver Real Time bidding Postback Keys
• Buyer qualification pre-pings
• Passthrough ping webhooks

In these workflows, Buyers often require information such as ZIP code or location data before deciding whether to accept the call.

Because of this, Retreaver IQ enrichment must occur before the ping response is processed.

Required Setup

Configure a Campaign Webhook

Navigate to the Campaign → Webhooks and create a webhook with:

Trigger

Data Append

URL

https://retreaver.com/webhook-integration/retreaver-iq

Why This Is Required

The Data Append webhook allows Retreaver IQ to enrich the call before passthrough ping webhooks or RTB responses are generated.

This ensures fields such as ZIP code are available during the ping process.

Without this webhook:

• The ping may occur before enrichment completes
• ZIP code or enrichment data may be missing
• Buyers may reject the call due to incomplete payload data

Option 2: Call Transfer First (No Ping Request)

Overview

This setup is used when publishers send calls directly into Retreaver using only the Retreaver phone number.

No ping request or qualification request occurs before the call transfer.

This is the most common setup for standard inbound call campaigns.

Required Setup

Only the Integration setup is required.

Navigate to:

Integrations → Retreaver IQ by Audience Acuity

Enable the campaigns you would like to enrich.

Important Notes

Since the call is already being transferred directly into Retreaver:

• Retreaver IQ enriches the call automatically
• No pre-call ping response is needed
• No passthrough ping webhook dependency exists

Option 3: Campaigns Using Both Ping First AND Call Transfer First

Overview

Some campaigns may receive traffic from multiple publisher types simultaneously.

For example:

• Some publishers may use RTB or ping-first workflows
• Other publishers may directly transfer calls using only the Retreaver number

In these cases, both Retreaver IQ configurations should be enabled.

Required Setup

1. Enable Retreaver IQ in Integrations

Enable the campaign inside:

Integrations → Retreaver IQ by Audience Acuity

2. Configure the Data Append Webhook

Add the following campaign webhook:

Trigger

Data Append

URL

https://retreaver.com/webhook-integration/retreaver-iq

Why Both Are Needed

The Integration setup ensures direct inbound calls are enriched.

The Data Append webhook ensures ping-first workflows receive enrichment data before ping responses are processed.

Where Retreaver IQ Data Appears

Once enabled, Retreaver IQ enrichment data can be viewed within:

• Call flows
• Call detail pages
• RTB workflows
• Webhook payloads
• Reporting and analytics
• Buyer routing logic
• Passthrough ping webhook payloads

The returned data will be stored as caller_zip and can also be used in:

• Buyer conditions
• Routing rules
• Reporting filters
• CRM integrations
• Automation workflows

Common Use Cases

ZIP Code Enrichment for Ping Buyers

Populate ZIP code data before a ping request is sent to external Buyers.

Geographic Qualification

Identify the caller’s geographic region before routing the call to a Buyer.

Enhanced Buyer Targeting

Allow Buyers to receive calls that match specific enrichment criteria.

RTB Optimization

Pass enriched caller information into RTB workflows for improved bidding decisions.

CRM Enrichment

Append additional verified caller information into connected CRM systems automatically.

Best Practices

• Enable Retreaver IQ only on campaigns where enrichment data adds routing or reporting value.
• Test RTB and ping response timing before enabling on latency-sensitive Buyers.
• Review webhook payloads after setup to confirm enrichment data is populating correctly.
• Monitor successful pull counts to estimate monthly enrichment costs.
• Use the Data Append webhook when enrichment data must exist before ping requests are processed.

Pricing

Charges only apply when a successful enrichment lookup is completed.

Additional Resources

• Audience Acuity: https://audienceacuity.com/
• Retreaver Documentation