Sources

Sources are how leads get into the system. They represent where leads came from—usually a lead form on a website you control, but sometimes a partner you’re buying leads from. Sources can be assigned to partners to organize them by business relationship. This helps you track which vendor or affiliate is responsible for which lead flows.

​

Authentication

When you create a source, an API key and API secret are automatically generated for basic authentication. You can also use a bearer token if you prefer.

​

Source types

Sources can be either internal or vendor. This setting affects several behaviors:

​

Ping responses

• Internal: Returns a more detailed response from pings
• Vendor: Returns a simplified response

See the API Reference for specifics, or click the “API spec” button on a source to view its documentation. This generates a link that displays the basic auth credentials for up to one week, after which the credentials are hidden.

​

Subscription threshold behavior

When you’ve reached your subscription threshold:

• Internal: Pings are still accepted. Leads are held in a “withheld” status and won’t be processed until capacity frees up.
• Vendor: Pings are automatically rejected so you don’t purchase leads you can’t distribute.

To avoid hitting your threshold entirely, consider enabling auto-upgrade to automatically move to the next plan tier when you reach your limit.

​

Payout percentage

If you’ve negotiated a profit-sharing arrangement with a vendor, use the payout percentage to adjust what’s reported to them. For example, if you split profits 50/50, set the payout percentage to 50%. A $100 lead will be reported to the vendor as $50.

​

Test mode

Vendor sources can have test mode enabled, allowing vendors to test their integration without affecting production data. When test mode is on:

• Pings and leads submitted through the source are marked as test data
• Test data is hidden from normal views by default—use the “Test Mode” filter to see it
• Five reserved zip codes return deterministic responses, making it easy to verify different scenarios
• Any other zip code goes through normal routing but the lead is forced to Audit status and won’t be distributed to customers

​

Testing with zip codes

When test mode is enabled, the system returns predictable responses based on the zip code submitted: This lets vendors test every outcome—successful distribution, duplicates, rejections, no-match scenarios, and marketplace routing—without needing real buyer coverage in those areas.

​

Source-level fields

You can define fields at the source level. These fields are appended to the fields from the lead category associated with the source, allowing you to capture more precise information for specific sources. If you create a source-level field with the same title as a field on the lead category, the source configuration overrides the lead category configuration.

​

Source pricing

Beyond the payout percentage, you can configure specific pricing for each lead type within a source. This is found in the Pricing tab when viewing a source. The pricing table shows all lead types in the source’s lead category. For each lead type, you can set:

​

Pricing types

• Fixed: The source always receives this price, regardless of what customers bid. Useful for guaranteed payouts to vendors.
• Fallback: The source receives the payout percentage of the winning bid when bids are received. If no bids come in, this price is used instead.

​

Copying pricing from another source

If you have multiple sources with similar pricing structures, you can copy pricing from one source to another. Click Copy from source in the pricing table header and select the source to copy from. Only lead types that don’t already have a price configured will be copied.

​

Source-level duplicate checks

Duplicate checks can also be configured at the source level. When set here, the check only applies to leads coming through that source—just like source-level fields only apply to that source.

​

Deleting sources

When you delete a source, it’s soft-deleted rather than permanently removed. This preserves data integrity—leads, submissions, and pings that came through that source still need to reference where they originated. After deletion:

• The source no longer appears in dropdowns when creating or editing records
• Historical records (leads, submissions, pings) display the source name (with “(Deleted)” appended in list views)
• You can still filter by deleted sources when viewing historical data tables
• The source’s API credentials are deactivated