Skip to main content

Introduction

WhatConverts is a lead and conversion tracking platform that records calls, form submissions, chats, transactions, and other lead types together with the source, medium, and campaign that produced them. The connector authenticates with an API token and secret, fetches one row per individual lead through the WhatConverts REST API (v1), and exposes lead attributes as both metrics and breakdowns in dashboards. As a lead-tracking connector, lead attributes, source attribution, and currency values are standardized so widgets can aggregate alongside ad-platform sources without additional configuration. To connect this data source, see How to connect WhatConverts to Adriel.

Data refresh strategy

WhatConverts is a daily-cache connector: a fixed window of recent days is refreshed on every scheduled run rather than fetched live at dashboard load. Initial fetch. On first connection, the last 390 days of historical lead data are pulled. Refresh schedule. The cache refreshes twice per day, at 00:00 UTC and 05:00 UTC. On each run, the most recent 390 days are re-fetched and any new or updated leads are upserted. Cache pattern. Leads are stored as JSON rows in the leads collection and deduplicated by lead_id. Each /leads page returns 2,500 records; pagination continues until all pages are consumed before any row is written to the cache.

Architecture levels

WhatConverts exposes a single level: individual leads. Each row in a dashboard represents one lead.

Date range limits

Data requested outside these ranges may be truncated for the corresponding time breakdown.

Metrics

How to read the columnsCode style like lead_id is the literal WhatConverts API field name. Italic text describes how a value is produced when it doesn’t map cleanly to a single WhatConverts field or when it’s derived by Adriel.Data type vocabulary: Number, Currency, Percentage, Ratio, Duration, Date, Text, URL, Array, Boolean.

Leads & volume

Conversions & value

Lead sources & attribution

Call, form & chat activity

Applicable to phone_call and, where noted, text_message leads.

Caller & geography

Breakdowns

How to read the columnsCode style like lead_type is the literal WhatConverts API field name. Italic text describes a grouping produced by Adriel rather than returned by WhatConverts.

Leads & volume

Conversions & value

Lead sources & attribution

Call, form & chat activity

Caller & geography

Time & grouping

These groupings are provided by Adriel rather than returned by WhatConverts.

Limitations

Based on the current connector, WhatConverts has:
  • Single lead level — the connector exposes one row per lead; there is no separate architecture or account-summary level.
  • Lead Summary empty on the “All” breakdown — Lead Summary is a per-lead attribute extracted from each lead’s AI analysis, so it is intentionally returned as null when the dashboard breakdown is set to All.
  • Recording is a synthesized field — the Recording audio cell is constructed on demand from the asset ID and lead ID, so requesting Recording implicitly requests lead_id and play_recording from the cache.
  • Country returned as ISO alpha-2 — country values are normalized to ISO 3166-1 alpha-2 codes (for example, US, KR, GB); already-valid two-letter uppercase values pass through unchanged, and unrecognized values are returned as-is.
  • Invalid breakdown returns no rows — a breakdown that is not recognized returns an empty result set instead of an error.
  • 401 auto-disconnect — a 401 response from WhatConverts is mapped to INVALID_CREDENTIALS and automatically disconnects the data source. Reconnect with a corrected API Token and API Secret after the cause is addressed in WhatConverts.
  • No deleted-data exclusion at source — leads removed in WhatConverts after import are not provided again on subsequent refreshes.

API references

See also