Summary
Campaigns in Kadince are designed to help you organize complex, multi-channel work into something you can actually see, manage, and report on. Think of a Campaign as the “umbrella,” and Projects/Requests as the “lanes” that run underneath it.
The Associated Campaign field exists on both the Request and Project objects, making it the organizational layer for multi-piece marketing efforts.
Below are practical tips for how to use Campaigns effectively.
Enhanced Tasks Engine
Some of these tips contain features from the Enhanced Tasks Engine. This feature will be launched to all users eventually, so we recommend speaking with a Kadince representative on whether it makes sense for your institution to turn on Enhanced Tasks.
Check out this article if you're thinking about it!
Tips & Tricks
1. What to Use: Campaign or Project?
1. What to Use: Campaign or Project?
Use a Campaign when:
You have multiple pieces of content (e.g., email, direct mail, ads) that share the same overall goal or audience, but need different tasks and approval paths
You have multiple owners approving content or moving work forward
Different parts of the work need to move at different speeds (“different swim lanes”)
You need one place to see: “How are we doing on this initiative overall?”
If the content needs to progress in different swim lanes at different paces, it should be a Campaign.
Stick with a single Project if:
There’s one primary content asset and
A single owner or tightly controlled approval path.
2. Model Each Channel as Its Own Project
2. Model Each Channel as Its Own Project
Instead of forcing everything into one giant project, use one Campaign with multiple Projects, for example:
Campaign: “Fall Home Equity Campaign”
Project 1: Email Campaign
Project 2: Direct Mail Campaign
Project 3: Display Ad Campaign
Benefits of this structure:
Each Project can have its own task sequences, approvals, and owners
You avoid the complexity of trying to run multiple concurrent approval sequences inside a single project
You still get roll-up visibility at the Campaign level (once statuses and dashboards are fully leveraged)
Trying to build multi-owner, multi-lane approvals inside a single project quickly becomes a “matrix nightmare”
Separate “lanes” (Projects) under one Campaign are cleaner to build, support, and explain to users
3. Use Requests for Early-Stage Ideas and Audience Segmentation
3. Use Requests for Early-Stage Ideas and Audience Segmentation
For the “define audience/segmentation” phase, consider using a Request instead of jumping straight into a Project:
Use a Request to:
Propose a new idea or Campaign concept
Define the target audience and segmentation
Run early approvals (e.g., Fair Lending/Fair Banking review) before content work starts
Practical Use Case:
Submit a Request: “Fall HELOC Campaign – Target Audience & Segmentation”
Route it through an approval sequence (compliance, marketing leadership, etc.)
Once approved, generate a Project from the Request and tie it to the Campaign
The approved details (like segmentation) carry over into the project, so users don’t have to chase a separate ticket
4. Standardize on “One Project Owner” for Content Approval
4. Standardize on “One Project Owner” for Content Approval
To avoid confusion and deadlocks:
Assign one primary Project owner for each project under a Campaign
Use tasks, sequences, and approval steps to:
Pull in reviewers
Capture revisions
Track approvals
Why This Matters:
The current approval model is built around one approval content lane per Project
Multiple “equal” owners on the same approval content piece tends to create conflict and ambiguity
In practice, pushing for a single Project owner can lead to a cleaner, workable solution
If more than one owner needs to approve content, that’s a sign you should break work into multiple Projects under a Campaign, not stack all approvals into one Project.
5. Keep Sequences Simple; Let Campaigns Handle Complexity
5. Keep Sequences Simple; Let Campaigns Handle Complexity
Treat task sequences inside a Project as the linear process for that asset:
Creation → Compliance → Deployment
Avoid trying to build:
Multiple approval sequences competing to set the same project status at the same time
Extremely complex “AND/IF both sequences are done then approve” logic inside one project
Instead:
Use multiple Projects under a Campaign to represent distinct approval lanes
If necessary, use:
Tags
In-progress statuses
Simple workflows to handle edge cases
Trying to orchestrate “all horses must finish the race” logic inside one Project is possible, but fragile and hard to support
Campaigns plus multiple Projects are the clean, recommended pattern
6. Campaigns Fields
6. Campaigns Fields
Campaign fields include: Campaign Title, Category, Start/End Run Dates, Date Needed By, Campaign Owner, Tags, Description, Notes, Attachments, and Form Submitted.
That's a lot of surface area most users probably don't fully leverage—especially Category, Tags, and the Run Dates.
7. Deleting vs. Deactivating
7. Deleting vs. Deactivating
Deleting a Campaign will also delete any tasks directly associated with that Campaign—but it does not delete the linked Requests or Projects.
Deactivating a Campaign leaves all existing associations intact. Deactivated Campaigns just get hidden from selection lists, so they can't be newly linked to Requests/Projects (it's enforced by UI visibility, not a hard validation rule).
Using Tags
Using Tags
Example Use Cases
Scenario 1: Multi-Channel Campaign
Scenario 1: Multi-Channel Campaign
A bank wants a multi-channel Home Equity Campaign with strict audience compliance and separate email/direct mail approvals.
Recommended setup:
Campaign: “2025 Home Equity Push”
Request (tied to Campaign): “Define Audience & Segmentation”
Route through compliance/fair banking approval
Once approved, generate Projects
Project 1: “HELOC – Email Campaign”
Tasks & sequences for email copy, design, compliance, deployment
Project 2: “HELOC – Direct Mail Campaign”
Tasks & sequences for print creative, legal review, vendor proof, drop date
Campaign Status:
Moves from “Planning” → “In Production” → “All Assets Approved” → “Launched” as Projects complete
Scenario 2: Campaigns vs Tags
Scenario 2: Campaigns vs Tags
You may have asked, "Should I use Campaigns or Tags to group Marketing Projects that include multiple products?"
If your marketing Projects span multiple products and they need to report across those dimensions simultaneously, Tags might be a more flexible tool.
Campaigns may create limitations when a single piece of work touches multiple initiatives.
