How to set revenueclickmedia
TrackDrive Ping/Post Integration Guide
Section titled “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
Section titled “Ping & Post URLs”TrackDrive supports both GET and POST request methods for Ping and Post submissions.
Ping Endpoint
Section titled “Ping Endpoint”The Ping endpoint is used to check whether agents are available before sending the full lead data.
Endpoint URL
Section titled “Endpoint URL”Example Querystring Request
Section titled “Example Querystring Request”Post Endpoint
Section titled “Post Endpoint”The Post endpoint is used to submit the complete lead information after a successful ping response.
Endpoint URL
Section titled “Endpoint URL”Required Parameters
Section titled “Required Parameters”The following parameters are required for the integration to function properly.
trackdrive_number
Section titled “trackdrive_number”This parameter is required because the webhook uses caller number forwarding.
Example
Section titled “Example”+18447600255
Static Value
Section titled “Static Value”+18447600255
traffic_source_id
Section titled “traffic_source_id”Your assigned Traffic Source ID.
Example
Section titled “Example”3990
Static Value
Section titled “Static Value”3990
Core Lead Fields
Section titled “Core Lead Fields”These are the most commonly used lead fields when submitting data.
caller_id
Section titled “caller_id”The consumer’s phone number.
Example
Section titled “Example”+17194451111
ping_id
Section titled “ping_id”The Ping ID returned during the ping request. This value must be passed during the post request.
first_name
Section titled “first_name”Lead first name.
Example
Section titled “Example”John
last_name
Section titled “last_name”Lead last name.
Example
Section titled “Example”Smith
Lead email address.
Example
Section titled “Example”[email protected]
The email must follow valid email formatting rules.
address
Section titled “address”Primary street address.
Example
Section titled “Example”123 Fake Street
address2
Section titled “address2”Secondary address field such as apartment or suite number.
Lead city.
Example
Section titled “Example”Boulder
Two-letter US state abbreviation.
Example
Section titled “Example”WA
Supported values include all US states such as:
-
CA
-
TX
-
FL
-
NY
-
NC
-
etc.
US ZIP code.
TCPA & Compliance Fields
Section titled “TCPA & Compliance Fields”tcpa_opt_in
Section titled “tcpa_opt_in”Indicates whether the consumer agreed to TCPA consent language.
Accepted Values
Section titled “Accepted Values”true / false
tcpa_optin_consent_language
Section titled “tcpa_optin_consent_language”Stores the exact TCPA language shown to the consumer during form submission.
jornaya_leadid
Section titled “jornaya_leadid”Jornaya Lead ID generated on the original form submission.
trusted_form_cert_url
Section titled “trusted_form_cert_url”TrustedForm certificate URL associated with the form submission.
permissiontrust_token
Section titled “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
Section titled “Date of Birth Fields”You may either submit the full DOB field or split values individually.
Date of birth in YYYY-MM-DD format.
Example
Section titled “Example”1990-05-15
dob_mm
Section titled “dob_mm”Birth month.
1 - 12
dob_dd
Section titled “dob_dd”Birth day.
1 - 31
dob_yyyy
Section titled “dob_yyyy”Birth year.
1900 - 2050
Consumer Information Fields
Section titled “Consumer Information Fields”marital_status
Section titled “marital_status”Consumer marital status.
Accepted Values
Section titled “Accepted Values”-
single
-
married
-
divorced
-
separated
-
widowed
employment_status
Section titled “employment_status”Employment status of the lead.
Accepted Values
Section titled “Accepted Values”-
employed
-
self_employed
-
unemployed
-
homemaker
-
retired
-
disabled
-
separated
gender
Section titled “gender”Consumer gender.
Accepted Values
Section titled “Accepted Values”-
M
-
F
spoken_language
Section titled “spoken_language”Preferred language.
Supported Values
Section titled “Supported Values”-
English
-
Spanish
-
Chinese
-
Tagalog
-
Vietnamese
-
French
-
Arabic
-
Korean
-
Russian
-
German
best_time_to_contact
Section titled “best_time_to_contact”Preferred contact time.
Accepted Values
Section titled “Accepted Values”-
morning
-
afternoon
-
evening
-
anytime
Tracking & Sub IDs
Section titled “Tracking & Sub IDs”These fields are commonly used for affiliate tracking and reporting.
sub_id
Section titled “sub_id”Primary affiliate or tracking ID.
s1 - s5
Section titled “s1 - s5”Additional custom tracking fields.
traffic_source_lead_id
Section titled “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
Section titled “Media & Traffic Source Fields”media_type
Section titled “media_type”Describes the advertising channel used to generate the lead.
Supported Values
Section titled “Supported Values”-
Google Ads
-
Facebook Lead Ads
-
TikTok
-
YouTube
-
Instagram
-
Twitter
-
SnapChat
traffic_source_platform
Section titled “traffic_source_platform”Identifies the platform generating the traffic.
Supported Platforms
Section titled “Supported Platforms”-
Ringba
-
Retreaver
-
Invoca
-
TrackDrive
-
Marchex
-
CallRail
-
ViciDial
-
Vonage
-
Convirza
-
Phonexa
-
and others
Additional Tracking Tokens
Section titled “Additional Tracking Tokens”The following fields are optional but commonly used for integrations and attribution tracking.
Google Click ID.
fbeventid
Section titled “fbeventid”Facebook Event ID.
msclkid
Section titled “msclkid”Microsoft Click ID.
voluum_cid
Section titled “voluum_cid”Voluum tracking click ID.
redtrack_click_id
Section titled “redtrack_click_id”RedTrack click identifier.
ringba_call_uuid
Section titled “ringba_call_uuid”Ringba call UUID used for postbacks and tracking.
retreaver_call_uuid
Section titled “retreaver_call_uuid”Retreaver call UUID.
retreaver_call_key
Section titled “retreaver_call_key”Retreaver call key.
Optional Operational Fields
Section titled “Optional Operational Fields”use_hold_queue
Section titled “use_hold_queue”Determines whether unanswered inbound calls should enter a hold queue.
Accepted Values
Section titled “Accepted Values”true / false
payment_method_available
Section titled “payment_method_available”Indicates whether the lead has a valid payment method.
Accepted Values
Section titled “Accepted Values”true / false
aged_data
Section titled “aged_data”Indicates whether the lead is aged data.
Accepted Values
Section titled “Accepted Values”true / false
Agent & Transfer Fields
Section titled “Agent & Transfer Fields”traffic_source_agent_id
Section titled “traffic_source_agent_id”Internal ID of the transferring agent.
traffic_source_agent_name
Section titled “traffic_source_agent_name”Full name of the transferring agent.
traffic_source_agent_recording_url
Section titled “traffic_source_agent_recording_url”URL to the original traffic source recording.
ea_disposition
Section titled “ea_disposition”Disposition provided by an external agent or bot.
-
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 ExamplePING Response Example
Section titled “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
Section titled “POST Request Example”POST Response Example
Section titled “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]” }