Lead creation dates use up to 400 inclusive UTC days. Native classifications, score, campaign attribution and call outcomes are preserved. Current profile context ignores dates. Contact identities, recordings, journeys, URLs and monetary values are excluded.
This integration reads WhatConverts data for reports and analysis. Source write actions are not available in Datapipe.
Use your reports in a sheet, a warehouse or a connected assistant, according to your plan and setup.
Examples for your team
Illustrative workflows using the supported capabilities. Connect your own account to work with your data.
Read & report
Inspect lead quality classifications
Keep repeat or unique status, quotable classification and native score together without treating them as verified sales.
Read & report
Review available attribution
Keep source, medium, campaign and keyword beside each lead when supplied. Missing attribution remains empty; this source alone does not supply advertising spend or ROAS.
Reports you can build
2 reporting datasets with their own fields. Choose a dataset in the app, then select the columns you need.
See included datasets and what they report
Profile lead attribution
One lead per row from one connected account and profile, selected by creation time across up to 400 inclusive UTC days. Native lead status, quotable classification and score are not inferred conversions or verified sales. Call duration is seconds. Missing attribution stays empty. Contact identities, phone numbers, IP addresses, click IDs, URLs, notes, messages, recordings, transcripts, journeys and monetary values are excluded. No leads are created or changed.
Connected profile
Current identity of the agency-selected account and profile. Report dates do not reconstruct profile history. Agency master credentials must read both selected resources; the same account and profile remain bound on every read and credential replacement.
Agency master credentials are required for account and profile verification. Provider access and request limits apply. Leads use creation time across at most 400 inclusive UTC days. Native classifications and scores are not verified sales. Contact details, recordings, transcripts, journeys, URLs and monetary values are excluded.
Metrics and dimensions
29 report fields across 2 datasets.
Browse the documented fields below. In the app, choose your project connection to load its field list. Availability depends on API permissions, report type, and compatible field combinations. Property-specific custom fields appear after connecting.
No fields match. Try another search or choose All.
Create a project and choose WhatConverts in Connections.
Paste your agency’s master token and secret, account ID and profile ID. The credentials must read both resources.
Pick where it goes. Choose profile lead attribution and a destination. Lead dates use UTC; profile details describe current state.
Sample report
Sample
Lead ID
Lead created at
Lead type
Lead status
Quotable classification
Native lead score
Marketing source
Marketing medium
1,240
1,240
1,240
Paid
1,240
1,240
1,240
1,240
640
640
640
Pending
640
640
640
640
210
210
210
Refunded
210
210
210
210
Sample numbers, so you can see the shape. Your report uses your accounts.
Read one account/profile’s leads by creation time across up to 400 inclusive UTC days. Includes native classifications, score, available campaign attribution and call outcomes. Current profile identity ignores report dates. Contacts, recordings, transcripts, journeys, URLs and monetary values are excluded. No lead changes or webhooks.
Questions
Free to start. Paid plans add more connections and refresh faster.
Free and Starter refresh once a day. Pro refreshes every hour. Agency refreshes every 15 minutes on the first 50 connections.
No. Name a project, add a connection, then choose a report and destination.
This integration is read-only in Datapipe. You can read the supported reports, share them with reporting destinations and ask a connected assistant about the available data. Sending report output to a destination does not grant editing access to this source. Read-only in Datapipe using an agency-owned WhatConverts master API Token and API Secret. The key must read the selected account and profile and may have broader provider permissions. Agencies provide their own eligible account; Datapipe does not supply a provider subscription. Profile-only keys are not supported by this initial account-verified connector.
This page lists 29 report fields across 2 datasets. You pick the columns when you build the report.
Read one account/profile’s leads by creation time across up to 400 inclusive UTC days. Includes native classifications, score, available campaign attribution and call outcomes. Current profile identity ignores report dates. Contacts, recordings, transcripts, journeys, URLs and monetary values are excluded. No lead changes or webhooks. Account permissions and the records available from the provider determine which rows can be read.
Yes. The same numbers can go to a sheet, a chart, a warehouse, or an assistant.