Leadspedia Real Time Bidding Integration

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

Prerequisites

Before setting up this integration, ensure you have:

• An active Leadspedia account with RTB permissions
• Your Leadspedia subdomain information
• Campaign ID from your Leadspedia account
• Campaign Key (authentication token) from Leadspedia
• Understanding of your call routing and monetization strategy

Configuration Steps

Step 1: Obtain Leadspedia Campaign Credentials

1. Log into your Leadspedia account
2. Navigate to your campaign management section
3. Locate the campaign you want to send bid requests to
4. Note the Campaign ID (numeric identifier)
5. Generate or locate your Campaign Key (authentication token)
6. Identify your Subdomain (your unique Leadspedia identifier)

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 Leadspedia from the Real Time Bidding templates
7. Fill in the required fields:

Required Configuration Fields

Subdomain (Required)

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

Campaign ID (Required)

• Enter the Campaign ID from your Leadspedia account
• This identifies which campaign will receive your bid requests
• Example: 12345678

Campaign Key (Required)

• Enter your Campaign Key (authentication token) from Leadspedia
• This authenticates your requests to the Leadspedia RTB system
• Example: abc123def456ghi789jkl012

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.leadspediatrack.com/call-preping.do?lp_campaign_id=CampaignID&lp_campaign_key=CampaignKey&caller_id=[[tag:CallerId]]&zip_code=[[tag:InboundZipCode]]

HTTP Method

• Method: GET (automatically configured)
• Timeout: 10 seconds (default, adjustable)

URL Parameters The integration automatically includes these query parameters:

• lp_campaign_id: Your Leadspedia Campaign ID
• lp_campaign_key: Your Campaign Key for authentication
• caller_id: Dynamic caller ID from [[tag:CallerId]]
• zip_code: Dynamic zip code from [[tag:InboundZipCode]]

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 bid payouts using the payout field:

• Field: payout
• Condition: Greater Than
• Value: 0

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

Bid Response Handling

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

• Property Path: Enter the JSON path to the bid data
• Common Fields:
• • payout - The payout amount offered for the call
  • destination - Phone number where the call should be routed
  • campaign_id - The Leadspedia campaign that accepted the bid
  • status - Response status indicating bid acceptance

Testing Your Configuration

To test your integration:

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

The built-in webhook test will send a test bid request to Leadspedia 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 Leadspedia's RTB system:

1. Bid Request: CallGrid sends call information to your specified Leadspedia campaign
2. Campaign Evaluation: Leadspedia evaluates the call against campaign criteria
3. Bid Response: Leadspedia responds with payout information and routing details
4. Acceptance Decision: Your system evaluates the bid response against your criteria
5. Call Routing: If accepted, the call is routed to Leadspedia's destination

Bid Response Structure

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

{

  "payout": 25.50,

  "destination": "18005551234",

  "campaign_id": "12345678",

  "status": "accepted",

  "caller_id": "15551234567",

  "zip_code": "90210",

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

}

Advanced Configuration Examples

Example 1: Basic Payout Acceptance

Acceptance Criteria:

• Field: payout
• Condition: Greater Than
• Value: 0

This configuration accepts calls when Leadspedia offers any payout amount.

Example 2: Minimum Payout Threshold

Acceptance Criteria:

• Field: payout
• Condition: Greater Than
• Value: 20.00

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

Example 3: Status-Based Acceptance

Acceptance Criteria:

• Field: status
• Condition: Equals
• Value: accepted

This configuration accepts bids based on Leadspedia's status response.

Example 4: Multiple Acceptance Criteria

You can add multiple criteria to ensure both successful status and minimum payout:

Criteria 1:

• Field: status
• Condition: Equals
• Value: accepted

Criteria 2:

• Field: payout
• Condition: Greater Than
• Value: 15.00

Advanced Use Cases

Multi-Campaign Strategy

Configure multiple CallGrid destinations, each targeting different Leadspedia campaigns to maximize bid competition and revenue.

Geographic Optimization

Leverage the automatic zip code parameter to route calls to campaigns optimized for specific geographic regions.

Payout Optimization

Use payout thresholds to ensure calls are only routed when they meet your minimum revenue requirements.

Troubleshooting

Common Issues

Authentication Failures

• Verify your Campaign Key is correct and current
• Ensure your Leadspedia account is active and has RTB permissions
• Check that the Campaign ID exists and is properly configured

Invalid Subdomain

• Confirm your subdomain matches your Leadspedia account
• Verify the subdomain is spelled correctly
• Check that your Leadspedia account is accessible

No Bid Responses

• Ensure your Leadspedia campaign is active and accepting calls
• Verify the campaign has budget and capacity available
• Check that your call types match the campaign's buying criteria

Low Payout Issues

• Review your payout thresholds to ensure they're realistic
• Check Leadspedia's campaign requirements and adjust call quality
• Verify that your geographic targeting aligns with campaign needs

Testing the Integration

Template Configuration Test:

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

Built-in Webhook Test:

1. In the advanced configuration screen, provide test values:
2. • tag:CallerId: Enter a test phone number (e.g., 5551234567)
   • tag:InboundZipCode: Enter a test zip code (e.g., 90210)
2. Click Run Webhook to test the connection
3. Verify the bid response contains expected payout 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 payout acceptance conditions

Best Practices

Campaign Optimization

• Monitor payout trends and adjust thresholds accordingly
• Test different geographic markets to maximize revenue
• Ensure consistent call quality to maintain campaign performance

Revenue Maximization

• Set competitive but realistic payout thresholds
• Track performance metrics across different campaigns
• Adjust routing strategies based on campaign response patterns

Call Quality Management

• Maintain high call quality standards to ensure campaign approval
• Monitor call completion rates and buyer feedback
• Implement quality controls to protect campaign 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