Fallback Campaigns

Fallback campaigns provide a safety net when a lead can't be delivered to the primary campaign. If qualification fails or delivery caps are hit, fallback campaigns are tried in order.

How Fallbacks Work

1. A lead is qualified for the primary campaign
2. Delivery is attempted but fails (caps hit, schedule outside window, etc.)
3. The system tries each fallback campaign in the configured order
4. The first fallback that can accept the lead is used
5. If no fallback can accept, the lead is queued or disqualified depending on the action configured

When Fallbacks Trigger

Fallbacks are triggered when:

• Delivery caps are hit (daily or lifetime) and the cap action is set to "Next Priority"
• Delivery schedule is outside operating hours and the schedule action is set to "Next Priority"
• Qualification fails for the primary campaign and another qualified client exists

Fallbacks are not triggered when:

• The cap or schedule action is set to "Queue" (lead waits for the primary campaign)
• The cap or schedule action is set to "Specific Campaign" (lead goes to a specific campaign, not the fallback chain)

Configuration

Navigate to the Routing tab on a campaign. The Fallback Campaigns section shows a drag-and-drop priority list.

• Add fallback campaigns from the dropdown
• Drag to reorder — position determines priority (top = tried first)
• Remove with the trash icon

Each fallback shows the campaign name, client, offer, active status, and whether it has a first submission action configured.

Important Notes

• Single level only — A fallback campaign's own fallbacks are not used. This prevents infinite loops.
• Order matters — Fallbacks are tried sequentially. Put your highest-priority backup first.
• Self-reference blocked — A campaign cannot be its own fallback.
• Unique entries — Each campaign can only appear once in the fallback list.