Skip to main content

How to set revenueclickmedia

Written by Luis Colmenares

TrackDrive Ping/Post Integration Guide

This article explains how to integrate with the TrackDrive Ping/Post webhook system, including supported request methods, endpoint URLs, required fields, optional parameters, and tracking tokens.

Ping & Post URLs

TrackDrive supports both GET and POST request methods for Ping and Post submissions.

Ping Endpoint

The Ping endpoint is used to check whether agents are available before sending the full lead data.

Endpoint URL

https://revenueclickmedia-com.trackdrive.com/api/v1/inbound_webhooks/ping/check_for_available_agent_auto_inbound

Example Querystring Request

https://revenueclickmedia-com.trackdrive.com/api/v1/inbound_webhooks/ping/check_for_available_agent_auto_inbound?trackdrive_number=%2B18447600255&traffic_source_id=3990

Post Endpoint

The Post endpoint is used to submit the complete lead information after a successful ping response.

Endpoint URL

https://revenueclickmedia-com.trackdrive.com/api/v1/inbound_webhooks/post/check_for_available_agent_auto_inbound

Required Parameters

The following parameters are required for the integration to function properly.

trackdrive_number

This parameter is required because the webhook uses caller number forwarding.

Example

+18447600255

Static Value

+18447600255

traffic_source_id

Your assigned Traffic Source ID.

Example

3990

Static Value

3990

Core Lead Fields

These are the most commonly used lead fields when submitting data.

caller_id

The consumer’s phone number.

Example

+17194451111

ping_id

The Ping ID returned during the ping request. This value must be passed during the post request.

first_name

Lead first name.

Example

John

last_name

Lead last name.

Example

Smith

email

Lead email address.

Example

[email protected]

The email must follow valid email formatting rules.

address

Primary street address.

Example

123 Fake Street

address2

Secondary address field such as apartment or suite number.

city

Lead city.

Example

Boulder

state

Two-letter US state abbreviation.

Example

WA

Supported values include all US states such as:

  • CA

  • TX

  • FL

  • NY

  • NC

  • etc.

zip

US ZIP code.

TCPA & Compliance Fields

tcpa_opt_in

Indicates whether the consumer agreed to TCPA consent language.

Accepted Values

true / false

tcpa_optin_consent_language

Stores the exact TCPA language shown to the consumer during form submission.

jornaya_leadid

Jornaya Lead ID generated on the original form submission.

trusted_form_cert_url

TrustedForm certificate URL associated with the form submission.

permissiontrust_token

PermissionTrust token used for compliance validation and lead verification.

This field helps validate:

  • Caller ID

  • ZIP code

  • TCPA consent

  • Website authenticity

Date of Birth Fields

You may either submit the full DOB field or split values individually.

dob

Date of birth in YYYY-MM-DD format.

Example

1990-05-15

dob_mm

Birth month.

Range

1 - 12

dob_dd

Birth day.

Range

1 - 31

dob_yyyy

Birth year.

Range

1900 - 2050

Consumer Information Fields

marital_status

Consumer marital status.

Accepted Values

  • single

  • married

  • divorced

  • separated

  • widowed

employment_status

Employment status of the lead.

Accepted Values

  • employed

  • self_employed

  • unemployed

  • homemaker

  • retired

  • disabled

  • separated

gender

Consumer gender.

Accepted Values

  • M

  • F

spoken_language

Preferred language.

Supported Values

  • English

  • Spanish

  • Chinese

  • Tagalog

  • Vietnamese

  • French

  • Arabic

  • Korean

  • Russian

  • German

best_time_to_contact

Preferred contact time.

Accepted Values

  • morning

  • afternoon

  • evening

  • anytime

Tracking & Sub IDs

These fields are commonly used for affiliate tracking and reporting.

sub_id

Primary affiliate or tracking ID.

s1 - s5

Additional custom tracking fields.

traffic_source_lead_id

The lead ID from the originating platform or CRM.

This may also contain:

  • External call UUIDs

  • CRM lead identifiers

  • Tracking references

Media & Traffic Source Fields

media_type

Describes the advertising channel used to generate the lead.

Supported Values

  • Google Ads

  • Facebook Lead Ads

  • TikTok

  • YouTube

  • Instagram

  • Twitter

  • SnapChat

traffic_source_platform

Identifies the platform generating the traffic.

Supported Platforms

  • Ringba

  • Retreaver

  • Invoca

  • TrackDrive

  • Marchex

  • CallRail

  • ViciDial

  • Vonage

  • Convirza

  • Phonexa

  • and others

Additional Tracking Tokens

The following fields are optional but commonly used for integrations and attribution tracking.

gclid

Google Click ID.

fbeventid

Facebook Event ID.

msclkid

Microsoft Click ID.

voluum_cid

Voluum tracking click ID.

redtrack_click_id

RedTrack click identifier.

ringba_call_uuid

Ringba call UUID used for postbacks and tracking.

retreaver_call_uuid

Retreaver call UUID.

retreaver_call_key

Retreaver call key.

Optional Operational Fields

use_hold_queue

Determines whether unanswered inbound calls should enter a hold queue.

Accepted Values

true / false

payment_method_available

Indicates whether the lead has a valid payment method.

Accepted Values

true / false

aged_data

Indicates whether the lead is aged data.

Accepted Values

true / false

Agent & Transfer Fields

traffic_source_agent_id

Internal ID of the transferring agent.

traffic_source_agent_name

Full name of the transferring agent.

traffic_source_agent_recording_url

URL to the original traffic source recording.

ea_disposition

Disposition provided by an external agent or bot.

Notes

  • Both GET and POST requests are supported.

  • Some fields may be optional depending on campaign configuration.

  • Compliance fields such as Jornaya and TrustedForm are strongly recommended.

  • Tracking parameters help improve attribution and reporting accuracy.

  • Always preserve the ping_id from the ping response when submitting a post request.
    ​
    PING Request Example

    curl "https://revenueclickmedia-com.trackdrive.com/api/v1/inbound_webhooks/ping/check_for_available_agent_auto_inbound?trackdrive_number=%2B18447600255&traffic_source_id=3990"

    PING Response Example

    {   "success":true,   "status":"accepted",   "errors":[],   "try_all_buyers_ping_id":"f832edec-ad2a-42c9-9c3b-4a95d5a35051",   "try_all_buyers":{     "ping_id":"f832edec-ad2a-42c9-9c3b-4a95d5a35051"   },   "ping_ids_expiry_in_seconds":9999,   "buyers":[     {       "ping_id":"f832edec-ad2a-42c9-9c3b-4a95d5a35051",       "id": 1,       "offer_conversion_payout": "offer_conversion_payout",       "concurrency_cap_limit": "concurrency_cap_limit",       "concurrency_cap_available": "concurrency_cap_available",       "current_conversion_duration": "current_conversion_duration",       "offer_conversion_duplicate_timeframe": "offer_conversion_duplicate_timeframe",     }   ] }

    POST Request Example

    curl "https://revenueclickmedia-com.trackdrive.com/api/v1/inbound_webhooks/post/check_for_available_agent_auto_inbound"

    POST Response Example

    {   "success":true,   "status":"accepted",   "errors":[],   "buyers":[     {       "id": 1,       "offer_conversion_payout": "offer_conversion_payout",       "concurrency_cap_limit": "concurrency_cap_limit",       "concurrency_cap_available": "concurrency_cap_available",       "current_conversion_duration": "current_conversion_duration",       "offer_conversion_duplicate_timeframe": "offer_conversion_duplicate_timeframe",     }   ],   "ping_ids_expiry_in_seconds":3600,   "forwarding_number_status":"accepted",   "forwarding_number":"+18551231234",   "forwarding_number_sip_address":"[email protected]" }
Did this answer your question?