Overview
Advanced settings provide precise control over web lead processing, from quality validation to compliance management. While default settings work for most users, these options maximize system capabilities for specific business needs.
General Settings
The General Settings tab establishes your campaign's core identity and functionality. Several settings here become permanent after creation, so careful setup is crucial.
Configuration Points
Campaign Name
What it does: Identifies your campaign across all LeadExec reports and interfaces
Best Practice: Use clear, consistent naming - e.g., "Solar Roofing Leads - FB"
Note: This is one of the few settings you can change later
Status Setting
Options: Active, Closed, Inactive, On Hold, Late, Suspended
Critical Detail: Only the "Active" status allows lead intake. You may also add different statuses based on your company's needs, for example, "Seasonal", if you have campaigns that are explicitly inactive during certain seasons
Pro Tip: You may use the "On Hold" status for temporary pauses instead of "Inactive"
Price per Lead
Purpose: Tracks cost (incurred by your company) for accurate ROI calculation and reporting
Setting: $0.00+ (it's recommended that you set it even if $0 for complete tracking)
Example: If you pay $15 per lead, set the price to $15.00
Note: Remember this is the cost you're incurring on every incoming lead, taking into account marketing efforts, platforms, etc.
Revenue Share - Percentage
Purpose: Allows you to determine what percentage of the lead's final selling price will be paid to your lead source.
Example: If a lead is sold for $30 and the percentage here is set to 50%, you'll pay your lead source $15 for this lead.
Revenue Share - Price Per Sale
Purpose: Allows you to set a fixed price per lead to pay your lead source.
Example: If you set this to $10, you'll pay $10 to your lead source for each lead sold, regardless of the final selling price or how many times this lead is sold to multiple buyers.
Step-by-Step Setup
Navigate to Campaigns → Select your Web Lead campaign
Click Edit → navigate to the General Settings tab
Configure each field:
Campaign Name: Descriptive and consistent
Status: Set to "Active" for live campaigns
Price: Actual cost per lead from source
Authentication: Enable only if you'll be using API credentials
Save changes and verify the status is "Active" before going live
Best Practices
Documentation: Consider keeping a master list of campaign names and purposes
Cost Tracking: Always set accurate prices for ROI reporting
Security: Consider enabling authentication for all third-party lead sources
Status Management: Use "On Hold" instead of "Inactive" for temporary pauses. You can also add different statuses that reflect internal exceptions, such as "Seasonal", for campaigns that are seasonally active and remain paused during the rest of the year
Troubleshooting
Leads are not arriving: Verify that the status of your campaign is set to "Active"
Authentication errors were detected when sending a lead into LeadExec: Check that the Lead Source API credentials you are using are correct
Price discrepancies: Check that the price field and revenue options match your needs
2. Delivery Options
The Delivery Options tab will let you configure how the campaign will deliver leads to clients:
Any Client: The campaign will route incoming leads to any eligible client
Single Client: The campaign will route leads exclusively to one client account.
Multiple Clients: You'll be able to select multiple specific clients or select an exclusive group.
Distribution Settings:
The Distribution Settings let you configure how LeadExec should prioritize clients during delivery:
System Default: Uses the system-wide distribution settings.
Price: Prioritizes highest-bidding clients
Priority: Follows predefined client ranking (e.g., 0 = highest, then 1, 2, 3, etc.)
Round Robin: Cycles leads sequentially between clients
Weighted: Allocates leads proportionally to assigned weights
Percentage: Distributes fixed lead shares within timeframes
Geolocation: Distributes based on specific geographic location preferences
Maximum Delivery Count:
This setting lets you configure how many times leads can be delivered to one or several clients.
Troubleshooting
Leads are being routed to the wrong clients: Verify that you select the correct setting, Single Client or Multiple Clients, if you need to target specific clients.
One of my clients hasn't received a lead, but the rest have: Check that automation method you're using is the correct one. Besides that, it's always a good idea to verify the criteria in your client's Delivery Account to determine if their criteria are too strict.
3. Quality Options Setup
Enhance lead data integrity and value
Overview
Quality Options provides tools to validate, clean, and enhance incoming lead data. Several services have per-lead costs but significantly improve conversion rates.
Duplicate Checks
Time Window: Set to a default of 30 days (you may adjust as needed)
Check Rejected Leads: Include previously rejected leads in the duplicate check scan
Append Duplicate Data: Update existing records (duplicate leads) with new information
Allow PING Duplicate API Check: The Campaign will run a duplicate-check API call to ensure no duplicates before final submission.
Resend Deliveries: This will trigger a redelivery of existing leads if the system detects a lead as a duplicate.
Criteria
You can add specific lead fields, regular expressions, and calculated expressions to set criteria that incoming leads must match to be detected as a valid lead.
Quantity Limits
Allows you to set hourly, daily, and monthly limits for how many leads this campaign can receive within those timeframes.
Lead Validation
Quality Control:
When enabled, this setting will make it so that every incoming lead is sent to Quality Control for manual review before delivery, requiring manual validation from your team. This is best suited for new lead sources, high-value leads, and specific compliance requirements that may require human input.
Default Reject Action:
Lets you control how the system handles a lead rejected by the buyer.
Reject back to Lead Source: the lead is returned to the Lead Source (a rejection reason can be seen in the Lead Source Portal)
Move to Quality Control: the lead is placed in Quality Control for further review
Forward to Delivery: forces the lead to be delivered to other eligible clients
Additional Validation Services:
Standardize Address: applies USPS-standardized delivery address format to the lead's address.
Append City and State: leads with a postal code and country will attempt to append a city and state if not included with the incoming information
Mobile Check: This checks whether the lead's primary phone number is registered as a mobile number.
Geolocate IP Address: The IP address of the lead will be geolocated
Lead Grading:
This feature allows you to evaluate and grade leads against system-wide settings or campaign-specific settings and score based on different validation services.
Step-by-Step Setup
Access the Quality Options tab in campaign settings
Enable Quality Control if manual review is needed
Set Duplicate Day Setting — 30 days recommended start. Remember that setting up a duplicate check field in your lead type is a prerequisite
Toggle validation services based on needs:
Address standardization for all campaigns
City/State append if postal data is available
Mobile check for phone-centric businesses
Save settings and test with sample leads
Best Practices
Start Essential: Begin with address standardization and duplicate checking
Cost-Benefit: Use paid services for higher-value lead campaigns
Progressive Enablement: Add services gradually while monitoring impact
Validation Priority: Enable mobile check for primarily phone-based businesses
Troubleshooting
High Duplicate Rate: Increase the number of days in the duplicate day lookback setting
Address Errors on Incoming Leads: Enable the address standardization
Invalid Phone Number: Enable the check service to confirm the phone number is a valid mobile number
Cost Overruns: disable paid services for lower-value campaigns
3. Compliance Configuration
Legal and regulatory requirement management
Overview
Compliance settings ensure your lead processing meets legal requirements like TCPA (US) and GDPR (EU). Proper configuration prevents legal issues and builds consumer trust.
TCPA Compliance (US Regulations)
Requirement: Obtain consent for automated calls/texts
Components:
Enable TCPA Services toggle
Custom consent text (default provided)
Notification email for issues
Reject leads without consent option
GDPR Compliance (EU Regulations)
Retention Policy: Days before automatic lead deletion
Rejected Retention: Separate policy for rejected leads
Note: Rejected policy overrides the main policy for rejected leads
FCC 1-to-1 Compliance
Feature: "Return Client Offers" for specific consent requirements
Best For: Ping-Post campaigns rather than web leads
Requirement: Revenue share settings must be configured
Step-by-Step Setup
TCPA Setup:
Enable "TCPA Services"
Review default consent text or add custom text
Set notification email address
Enable "Reject Lead for No Consent" if required
GDPR Setup:
Set "Retention Policy" days (e.g., 30, 60, 90)
Configure "Rejected Retention Policy" if different
Ensure proper disclosure in lead capture forms
FCC 1-to-1:
Enable "Return Client Offers" if using ping-post
Configure revenue share settings
Test with sample lead responses
Best Practices
Default Text: Use provided TCPA text unless legal counsel advises otherwise
Consent Tracking: Document all consent mechanisms and timing
Regional Settings: Apply GDPR only for EU-targeted campaigns
Email Notifications: Use group email (e.g., compliance@company.com)
Troubleshooting
Consent Errors: Review TCPA text and enablement
TCPA/GDPR violations: Verify the validity and accuracy of the TCPA settings and ensure you're rejecting leads with no consent
Integrations and Postback
For detailed views on available integrations and how to set up each one of them, visit our LeadExec Integrations Index.
For a detailed guide on setting up the postback feature, visit our Postback Overview article.