Technology / API

Lead delivery through dashboard, CRM, API, or call routing.

aventia Performance supports modern lead intake and delivery with API/webhook ingestion, call routing, CRM workflows, duplicate checks, buyer matching, and dashboard reporting.

1

POST /lead

JSON intake

2

route.match

category + ZIP + buyer

3

crm.push

buyer dashboard

4

status.update

accepted / invalid

Delivery

API + webhook + CRM + calls

Routing

Category + ZIP + buyer rules

Reporting

Live dispositions + dashboards

Integration map

API intake, routing, CRM delivery, and feedback.

Lead delivery can move through webhooks, CRM fields, call routing, dashboard records, and status updates.

1

POST /lead

JSON or webhook

2

route.match

ZIP, category, buyer

3

crm.push

Buyer dashboard

4

status.update

Accepted or invalid

Delivery

API + CRM

Routing

Rules-based

Feedback

Live dispositions

Example intake payload

API-ready lead structure

JSON
{
  "lead_type": "phone_call",
  "category": "garage_door",
  "state": "CA",
  "zip": "90025",
  "source_url": "https://source.example/request",
  "consent": {
    "tcpa": true,
    "trustedform_cert_url": "https://cert.trustedform.com/..."
  },
  "routing": {
    "mode": "live_call",
    "buyer_capacity": "open",
    "appointment_window": "same_day"
  }
}

Integration pipeline

Delivery can be simple or connected.

1

Intake

HTTPS POST, webhook, call tracking, CRM import

2

Normalize

Category, ZIP, timestamp, source, consent, duplicate key

3

Match

Category fit plus buyer rules

4

Deliver

Call route, CRM push, appointment handoff, dashboard record

5

Feedback

Accepted, booked, invalid, duplicate, no-answer, dispute

Lead intake

Approved buyer and publisher workflows can use structured lead intake through HTTPS POST, webhooks, JSON payloads, CRM delivery, email fallback, and direct call routing.

Call tracking and recording support
Form lead intake
Booked appointment delivery
Buyer assignment and routing rules
Real-time lead status updates
Duplicate, wrong-category, and quality checks

Reporting

Reporting can include accepted, duplicate, wrong category, outside coverage area, booked, sold, no answer, invalid, dispute status, call duration, buyer assignment, and revenue feedback.

Testing path

Technical integrations usually start with test payloads, sample calls, API key setup, field mapping, and a small pilot before larger volume.