Campaigns and lead sources

Lead sources, campaigns, and sub-campaigns track where your applications come from and let you route each stream of applications through the right product, decision workflow, and lender offer table automatically. Use them to measure channel performance and to make sure applications from a given partner or promotion are underwritten the way you intend.

---

How the hierarchy works

LendAPI organizes inbound applications into three levels, from broadest to most specific:

• Lead source — a partner, channel, or integration that sends you applications (for example, a specific aggregator or your own website).
• Campaign — a specific push or promotion under a lead source, identified by a campaign name and a campaign ID you choose.
• Sub-campaign — a finer split under a campaign (for example, a specific landing page, ad set, or geography), identified by its own sub-campaign ID.

Each level has its own status, schedule, application limit, notes, activity history, and integration keys. You can configure routing (product, decision workflow, and offer table) at the campaign and sub-campaign level, so applications tagged with a given campaign or sub-campaign ID are processed automatically without manual tagging.

Lists and identifying fields

• The lead sources list shows: source name, number of applications received, number of active sub-campaigns, number of active campaigns, last modified date, and status.
• The campaigns list under a lead source shows: campaign name, number of sub-campaigns, campaign ID, and status.
• The sub-campaigns list under a campaign shows: sub-campaign name, sub-campaign ID, and status.

A campaign’s detail page shows a breadcrumb of Lead Gen > [lead source name] > [campaign name], with a Sub Campaigns tab and an Activity tab on the left, and Overview and Notes tabs on the right. The Overview tab shows the campaign’s name, campaign ID, and last modified date, along with whichever product, workflow, and offer table are assigned to it. The Notes tab shows a count of notes attached to the campaign.

---

Routing applications automatically

At the campaign and sub-campaign level, you can assign:

• A product — the loan product the application is evaluated against.
• A workflow — the decision rules the application runs through.
• An offer table — the lender routing/pricing table used to generate offers.

Once assigned, applications tagged with that campaign’s or sub-campaign’s ID are routed through the assigned product, workflow, and offer table without any manual step.

---

Schedule and volume limits

Each lead source, campaign, and sub-campaign has its own schedule configuration, made up of:

• A toggle for whether the entity uses a custom schedule. When no custom schedule has been set, the default is Monday through Friday active from 00:00 to 23:59, with Saturday and Sunday inactive.
• Per-day settings for active/inactive, start time, and end time, for each day of the week.
• A toggle to limit applications, plus a number of applications and a limit period.

If a day is marked active but its start time is not earlier than its end time, the configuration is invalid and the system flags that day.

---

Status, notes, and activity

• Each lead source, campaign, and sub-campaign has a status you can toggle to pause or resume the flow of applications through it. Toggling shows a confirmation (for example, “Campaign status updated”).
• You can add free-text notes to a lead source, campaign, or sub-campaign for internal record-keeping.
• Each level keeps an activity log. Recorded event types include creation, enabled/disabled, campaign paused/resumed, sub-campaign paused/resumed, assign/unassign/replaced (for workflow, product, or offer table changes), and general updates.

---

Integration keys

Each level exposes identifiers you use to attribute applications submitted through an API integration:

• A lead source shows its Source ID and an API key (which can be masked, revealed, and copied).
• A campaign shows the API key, Source ID, and Campaign ID.
• A sub-campaign shows the API key, Source ID, Campaign ID, and Sub Campaign ID.

Tag inbound applications with the appropriate combination of these values so they’re attributed to the correct source, campaign, or sub-campaign.

---

Worked example

A marketing team at a lending operation wants to run a paid social campaign for debt consolidation loans and track it separately from other traffic.

1. An admin opens Lead Gen in the sidebar and creates a new lead source named Facebook Ads – Debt Consolidation, entering only the name. The system creates the source and confirms with “Lead source added.”
2. The admin opens the new lead source and creates a campaign named Q3 2026 – 36 Month Consolidation Offer, giving it the campaign ID FB-DC-Q3-36MO.
3. On the campaign’s Overview tab, the admin assigns the product Debt Consolidation Loan – Standard, the workflow Standard Underwriting Workflow, and the offer table Consolidation Lender Waterfall.
4. The admin clicks the configure icon on the campaign, turns on a custom schedule, sets Monday–Friday active from 08:00 to 20:00, leaves Saturday and Sunday inactive, and turns on the application limit.
5. From that point on, applications submitted with campaign ID FB-DC-Q3-36MO are routed through the Standard Underwriting Workflow and Consolidation Lender Waterfall automatically, and the campaign’s Activity tab records the workflow assignment and any later pause/resume events.

---

Use cases

Comparing two lead aggregators feeding the same product. A lender buys leads from two aggregator partners for the same personal loan product. It sets up each aggregator as a separate lead source, so the applications-count and active-campaigns figures on the Lead Gen list let operations staff compare volume per partner at a glance, without touching underwriting configuration.

Pausing one partner’s traffic without affecting others. During a compliance review, an operations lead needs to stop applications from one aggregator temporarily while other lead sources keep flowing normally. They toggle that lead source’s status to pause it, add a note explaining why, and toggle it back on once the review is complete — leaving the source’s ID, API key, and history intact.

Running multiple rate promotions from one website. A regional bank has a single lead source (its own site) but wants three separate rate promotions running at once, each tied to a different underwriting workflow and offer table. It creates three campaigns under the one lead source, each with its own campaign ID and its own assigned product, workflow, and offer table, so applications route correctly based on which promotion a customer applied through.

---

Best practices

• Use a lead source for each distinct partner, channel, or integration. Use campaigns for specific pushes or promotions under that partner. Use sub-campaigns only when you need a finer split, such as separate landing pages or ad sets.
• Choose a clear, unique campaign ID or sub-campaign ID before creating it — this is the value used to attribute inbound applications, so it should be easy to recognize in reporting later.
• Assign a product, workflow, and offer table at the campaign or sub-campaign level so applications route automatically, instead of relying on manual tagging after the fact.
• Use the schedule and application-limit settings to control when and how much volume a source, campaign, or sub-campaign accepts, rather than manually pausing and resuming status for routine hourly or volume-based control.
• When you need to stop a partner’s traffic temporarily, toggle its status off rather than trying to remove it, so its history, notes, and API key remain available.
• Add a note whenever you pause, resume, or reconfigure a source or campaign, so other operations staff can see why the change was made.

---

Unclear or not covered by source

• What happens to applications submitted after a source, campaign, or sub-campaign hits its configured application limit is not described in the available source.
• The specific values accepted for the limit period (for example, daily vs. weekly) are not enumerated in the available source.
• The default status of a newly created lead source, campaign, or sub-campaign (active or inactive) is not confirmed in the available source.
• Whether a lead source itself (as opposed to only campaigns and sub-campaigns) can be assigned a product, workflow, and offer table through the UI is not confirmed, even though the underlying data structure supports it.