TrackDrive Real Time Bidding Integration

The TrackDrive Real Time Bidding (RTB) integration enables you to send bid requests to TrackDrive's marketplace in real-time. This integration allows you to monetize your call traffic by submitting calls to TrackDrive buyers who can bid on them dynamically based on call characteristics, traffic source data, and caller information.

Prerequisites

Before setting up this integration, ensure you have:

• An active TrackDrive account with RTB permissions
• Your TrackDrive subdomain information
• Webhook Name from your TrackDrive account configuration
• Traffic Source ID for your call traffic
• Understanding of your call routing and monetization strategy

Configuration Steps

Step 1: Obtain TrackDrive Account Information

1. Log into your TrackDrive account
2. Navigate to your webhook or integration settings
3. Locate your Subdomain (your unique TrackDrive identifier)
4. Find or create a Webhook Name for this integration
5. Identify your Traffic Source ID for call tracking
6. Ensure your account has API access and RTB permissions

Step 2: Configure CallGrid Integration

Phase 1: Basic Template Setup

1. Navigate to your CallGrid destination settings
2. Click the Webhook tab
3. Enable Webhook Integration
4. Enable Template Mode
5. Switch to Real Time Bidding template type
6. Select TrackDrive from the Real Time Bidding templates
7. Fill in the required fields:

Required Configuration Fields

Subdomain (Required)

• Enter your TrackDrive subdomain
• This is your unique identifier in the TrackDrive system
• Example: yourcompany (if your TrackDrive URL is yourcompany.trackdrive.com)

Webhook Name (Required)

• Enter your TrackDrive webhook name
• This identifies the specific webhook endpoint for your integration
• Example: callgrid-integration

Traffic Source ID (Required)

• Enter your traffic source ID from TrackDrive
• This identifies the source of your call traffic for tracking purposes
• Example: source123

8. Click Save Webhook to proceed to advanced configuration

Phase 2: Advanced Configuration (Optional)

After saving your basic template configuration, you'll be taken to the advanced configuration screen. The system automatically builds the webhook URL and request structure for you.

Request Configuration

URL Structure The webhook URL is automatically generated based on your configuration:

https://Subdomain.trackdrive.com/api/v1/inbound_webhooks/ping/webhook

HTTP Method

• Method: POST (automatically configured)
• Content-Type: application/json (automatically configured)
• Timeout: 10 seconds (default, adjustable)

JSON Request Body The integration automatically includes these parameters in the JSON payload:

{

  "trackdrive_number": "TEMPLATE_TRACKDRIVE_NUMBER",

  "traffic_source_id": "SourceID",

  "caller_id": "[[tag:CallerId]]"

}

Dynamic Parameters:

• trackdrive_number: Template placeholder for TrackDrive tracking number
• traffic_source_id: Your configured Traffic Source ID
• caller_id: Dynamic caller ID from [[tag:CallerId]]

Acceptance Parsing

The most important setting is the acceptance criteria, which determines when bids are accepted.

Parsing Type

• Parse Type: JSON (automatically configured)
• Parse Field: Configure which field from the bid response to evaluate

Default Acceptance Criteria The system is pre-configured to check for offer conversion payouts using the buyers.0.offer_conversion_payout field:

• Field: buyers.0.offer_conversion_payout
• Condition: Greater Than
• Value: 0

This configuration accepts bids when TrackDrive responds with a conversion payout amount greater than 0.

Bid Response Handling

Response Field Options Configure which fields from the TrackDrive bid response to use for acceptance:

• Property Path: Enter the JSON path to the bid data
• Common Fields:
• • buyers.0.offer_conversion_payout - The conversion payout offered for the call
  • buyers.0.buyer_id - ID of the buyer making the offer
  • buyers.0.offer_id - ID of the specific offer
  • buyers.0.destination_number - Phone number for call routing

Testing Your Configuration

To test your integration:

1. Fill in your Subdomain, Webhook Name, and Traffic Source ID
2. In the webhook testing section, provide test values:
3. • tag:CallerId: Enter a test phone number (e.g., 5551234567)
3. Click Run Webhook to test the connection
4. Verify the test passes and shows a proper bid response from TrackDrive
5. Confirm the acceptance parsing works correctly with the response

The built-in webhook test will send a test bid request to TrackDrive and show you whether bids would be accepted based on their response.

How It Works

Real-Time Bid Process

The integration facilitates real-time bidding through TrackDrive's Inbound Webhooks API:

1. Bid Request: CallGrid sends call information to TrackDrive's ping endpoint
2. Buyer Evaluation: TrackDrive evaluates the call against available buyer offers
3. Bid Response: TrackDrive responds with buyer offers and conversion payouts
4. Acceptance Decision: Your system evaluates the bid response against your criteria
5. Call Routing: If accepted, the call is routed to the winning buyer's destination

Bid Response Structure

TrackDrive's RTB API returns bid responses in the following format:

{

  "buyers": [

    {

      "buyer_id": "buyer123",

      "offer_id": "offer456",

      "offer_conversion_payout": 25.50,

      "destination_number": "18005551234",

      "traffic_source_id": "source123"

    }

  ],

  "trackdrive_number": "tracking123",

  "caller_id": "5551234567",

  "timestamp": "2025-09-23T15:30:00Z"

}

Advanced Configuration Examples

Example 1: Basic Conversion Payout Acceptance

Acceptance Criteria:

• Field: buyers.0.offer_conversion_payout
• Condition: Greater Than
• Value: 0

This configuration accepts calls when TrackDrive offers any conversion payout.

Example 2: Minimum Payout Threshold

Acceptance Criteria:

• Field: buyers.0.offer_conversion_payout
• Condition: Greater Than
• Value: 20.00

This setup ensures calls are only accepted when the conversion payout exceeds $20.00.

Example 3: Buyer Validation

Acceptance Criteria:

• Field: buyers.0.buyer_id
• Condition: Not Equals
• Value: null

This configuration ensures calls are only accepted when a valid buyer is matched.

Example 4: Multiple Acceptance Criteria

You can add multiple criteria to ensure both valid buyers and minimum payouts:

Criteria 1:

• Field: buyers.0.offer_conversion_payout
• Condition: Greater Than
• Value: 15.00

Criteria 2:

• Field: buyers.0.destination_number
• Condition: Not Equals
• Value: null

Traffic Source Management

Traffic Source Configuration

Traffic Source IDs in TrackDrive help categorize and track different sources of call traffic:

• Organic Traffic: organic-web
• Paid Search: google-ads, bing-ads
• Social Media: facebook-ads, linkedin-ads
• Direct Traffic: direct-calls
• Affiliate Traffic: affiliate-network

Custom Traffic Sources

You can create custom traffic source IDs in TrackDrive to match your specific traffic categories and tracking requirements.

Advanced Use Cases

Multi-Source Strategy

Configure multiple CallGrid destinations, each targeting different TrackDrive traffic sources to maximize coverage and optimize bidding strategies.

Conversion Optimization

Use conversion payout data to route calls to buyers offering the best conversion rates and highest payouts.

Performance Tracking

Leverage TrackDrive's tracking capabilities to monitor call performance and optimize traffic source strategies.

Troubleshooting

Common Issues

Invalid Subdomain or Webhook Name

• Verify your subdomain matches your TrackDrive account
• Ensure the webhook name exists and is properly configured in TrackDrive
• Check that your TrackDrive account is active and accessible

Traffic Source ID Issues

• Confirm your Traffic Source ID exists in your TrackDrive account
• Verify the source ID is active and properly configured
• Check that the traffic source has associated buyer offers

No Buyer Responses

• Ensure there are active buyers in your TrackDrive marketplace
• Verify buyer offers are available for your traffic source
• Check that call characteristics match buyer requirements

Low Conversion Payout Issues

• Review your payout thresholds to ensure they're realistic
• Check TrackDrive buyer requirements and adjust call quality
• Verify that your traffic source aligns with buyer preferences

Testing the Integration

Template Configuration Test:

1. After entering all required fields, click Save Webhook
2. Review the auto-generated URL and JSON payload structure

Built-in Webhook Test:

1. In the advanced configuration screen, provide test values:
2. • tag:CallerId: Enter a test phone number (e.g., 5551234567)
2. Click Run Webhook to test the connection
3. Verify the bid response contains expected buyer data
4. Test different acceptance criteria using the webhook test feature

Live Integration Test:

1. Monitor CallGrid logs for successful bid requests
2. Verify bid responses are being parsed correctly
3. Test call routing based on conversion payout acceptance conditions

Best Practices

Traffic Source Optimization

• Use descriptive traffic source IDs that clearly identify your call sources
• Monitor performance metrics for different traffic sources
• Adjust traffic source strategies based on buyer response patterns

Revenue Optimization

• Set competitive but realistic conversion payout thresholds
• Track performance metrics across different buyers and offers
• Monitor conversion rates to optimize call routing decisions

Call Quality Management

• Maintain high call quality standards to ensure buyer satisfaction
• Monitor call completion rates and buyer feedback
• Implement quality controls to protect marketplace relationships

CallGrid Support

If you need assistance with this integration:

1. Check the CallGrid logs for error messages
2. Verify all configuration parameters
3. Test the integration using the built-in webhook test feature
4. Contact CallGrid support with integration details