Overview

A campaign takes the companies and contacts from a Target List, applies a workflow, sends messages through connected channels, tracks execution in the Console, and surfaces results through replies, signals, and intent.

Use Campaigns to launch structured, multi-channel outreach to the right target contacts with the right context.

What Campaigns are for

Campaigns help your team answer:

How do we engage this target list

How do we engage this target list

How do we engage this target list

A Target List defines the audience.

A Campaign defines how that audience is engaged.

Use Campaigns to:

1. Select a target list

2. Build a workflow

3. Choose engagement channels

4. Write messages by ICP or persona

5. Send email, LinkedIn, and iMessage steps

6. Add wait steps and conditions

7. Branch based on signals

8. Track execution

9. Review replies and intent

10. Improve future outreach

Campaigns require a paid plan

Campaigns require engagement channels.

Engagement channels are available on paid plans, so campaign execution is available only after your workspace is on a paid plan and the required channels are enabled.

The Free Plan is useful for exploring 1eyeᴬᴵ, setting up the workspace, reviewing signals, and building targeting foundations.

To run campaigns, your workspace needs:

1. A paid plan

2. Enabled engagement channels

3. Connected user accounts or lines

4. A target list

5. A campaign workflow

How Campaigns work

A campaign connects strategy, audience, channels, and execution.

The basic flow is:

Target List → Campaign Setup → Workflow → Channels → Launch → Console → Conversations → Insights

Target List → Campaign Setup → Workflow → Channels → Launch → Console → Conversations → Insights

Target List → Campaign Setup → Workflow → Channels → Launch → Console → Conversations → Insights

1. Target List
   The companies and contacts that will be used in the campaign.

2. Campaign Setup
   The campaign name, purpose, target list, and optional workflow import.

3. Workflow
   The sequence of steps that controls what happens, when it happens, and which channel is used.

4. Channels
   Email, LinkedIn, and iMessage nodes used inside the workflow.

5. Launch
   The campaign starts running against the target contacts.

6. Console
   The execution log showing what ran, what is pending, and what failed.

7. Conversations
   Replies and message activity from target contacts.

8. Insights
   Performance, replies, intent, message counts, ICPs, personas, and channel activity.

Campaign Setup

When you create a campaign, you start with Campaign Setup.

Campaign Setup may include:

1. Campaign name

2. Campaign purpose

3. Target list

4. Optional workflow import

5. Exclude unsubscribe URL setting

6. Preview step

These fields help 1eyeᴬᴵ understand what the campaign is meant to do and which audience it should run against.

Campaign name

The campaign name should be short, clear, and easy to recognize.

Good examples:

RevOps SaaS Outreach
Website Signals Follow-Up
Q2 LinkedIn Engaged Accounts
Growth Stage Companies in SF
Healthcare CIO Campaign

RevOps SaaS Outreach
Website Signals Follow-Up
Q2 LinkedIn Engaged Accounts
Growth Stage Companies in SF
Healthcare CIO Campaign

RevOps SaaS Outreach
Website Signals Follow-Up
Q2 LinkedIn Engaged Accounts
Growth Stage Companies in SF
Healthcare CIO Campaign

Weak examples:

Test
Campaign 1
New Campaign
Outreach
List Send

Test
Campaign 1
New Campaign
Outreach
List Send

Test
Campaign 1
New Campaign
Outreach
List Send

Use a name your team can understand later.

Campaign purpose

The purpose explains what the campaign is meant to achieve and who it is targeting.

A good purpose should include:

1. Target segment

2. Target contact type

3. Campaign goal

4. Message angle

5. Relevant qualification criteria

Example:

Introduce Snowbricks to growth-stage B2B SaaS companies with RevOps leaders who need better account intelligence, enrichment, and signal-led GTM workflows

Introduce Snowbricks to growth-stage B2B SaaS companies with RevOps leaders who need better account intelligence, enrichment, and signal-led GTM workflows

Introduce Snowbricks to growth-stage B2B SaaS companies with RevOps leaders who need better account intelligence, enrichment, and signal-led GTM workflows

A clear purpose helps your team build better workflows and messages.

Target list

Every campaign starts from a Target List.

The Target List supplies the campaign audience, including:

1. Target companies

2. Target contacts

3. ICP matches

4. Persona matches

5. Contact data

6. Company context

7. List readiness

Before launching a campaign, make sure the Target List is clean and ready.

Review:

1. Companies

2. Contacts

3. ICP fit

4. Persona fit

5. Contact status

6. Email availability

7. LinkedIn availability

8. Phone availability

9. Exclusions

A campaign is only as good as the list behind it.

Import workflow from another campaign

You can optionally import a workflow from an existing campaign.

Use this when you want to reuse a campaign structure that already works.

For example, you may reuse:

1. A proven email sequence

2. A LinkedIn-first workflow

3. A signal-based follow-up workflow

4. A persona-specific campaign structure

5. A multi-channel campaign template

After importing a workflow, review and edit it for the new audience before launching.

Do not blindly reuse a workflow without checking that the target list, personas, channels, and message context still fit.

Exclude unsubscribe URL

Some campaigns may include an option to exclude an unsubscribe URL.

Use this carefully and follow your company’s compliance requirements.

For most outbound email campaigns, teams should include appropriate unsubscribe or opt-out handling.

If your team has legal, compliance, or deliverability requirements, review them before changing unsubscribe behavior.

Campaign statuses

Campaigns can move through different statuses.

Common statuses include:

Use campaign status to understand where each campaign is in the lifecycle.

Draft campaigns

A campaign is in Draft when it is still being built.

Draft campaigns may need:

1. A target list

2. Workflow steps

3. Channel setup

4. Message content

5. Sender selection

6. Preview review

7. Final launch approval

Draft campaigns do not execute until launched.

Running campaigns

A campaign is Running when 1eyeᴬᴵ is actively executing the workflow.

Running campaigns may be:

1. Sending messages

2. Waiting between steps

3. Checking conditions

4. Tracking responses

5. Updating conversation signals

6. Logging activity in Console

You can monitor running campaigns from Insights, Workflow, Console, Companies, Contacts, Target List, Files, and Notes.

Paused campaigns

A campaign is Paused when execution is temporarily stopped.

Pause a campaign when you need to:

1. Review message quality

2. Fix a workflow issue

3. Update the target list

4. Check channel connections

5. Investigate replies

6. Stop sending without ending the campaign

Paused campaigns can be resumed when ready.

Ended campaigns

A campaign is Ended when it has completed or has been stopped permanently.

Ended campaigns are useful for reviewing:

1. Final message counts

2. Replies

3. Intent

4. Channel performance

5. ICP performance

6. Persona performance

7. Lessons for future campaigns

Do not end a campaign unless you are done with it.

Channels inside campaigns

Campaigns use enabled engagement channels.

Available campaign channels may include:

1. Email

2. LinkedIn

3. iMessage

Only channels that are enabled for the workspace and connected for users will appear in campaign workflows.

For example:

1. If Email is enabled and a mailbox is connected, email nodes can be used.

2. If LinkedIn is enabled and an account is connected, LinkedIn nodes can be used.

3. If iMessage is enabled and a line is connected, iMessage nodes can be used.

If a channel is disabled, not included in the plan, or not connected, it will not be available for campaign execution.

Email in campaigns

Email nodes let you send campaign emails from connected Google Workspace Gmail mailboxes.

Email can be used for:

1. Intro emails

2. Follow-up emails

3. Final emails

4. Persona-specific messages

5. ICP-specific messages

6. Replies and intent tracking when available

Email is often the core channel in outbound campaigns.

LinkedIn in campaigns

LinkedIn nodes let you send connection requests and LinkedIn messages from connected LinkedIn accounts.

LinkedIn can be used for:

1. Connection requests

2. Follow-up messages

3. Messages after connection accepted

4. Persona-specific outreach

5. Multi-channel reinforcement

6. Replies and intent tracking when available

LinkedIn works well when the target contact has a strong LinkedIn profile and the message is relevant.

iMessage in campaigns

iMessage nodes let you send messages from connected iMessage-enabled lines.

If the target contact does not have an iMessage-compatible device, the message may be sent as SMS.

iMessage can be used for:

1. Direct outreach

2. Follow-up messages

3. High-intent contact engagement

4. Time-sensitive follow-up

5. Replies and intent tracking when available

iMessage should be used carefully because it is a direct channel.

Workflows

The Workflow tab is where you build the campaign logic.

A workflow controls:

1. Which message gets sent

2. Which channel is used

3. Which sender is used

4. How long to wait between steps

5. What happens after a signal

6. What happens after a reply

7. Where the campaign ends

Workflows can include nodes such as:

1. Start

2. Email

3. LinkedIn

4. iMessage

5. Signal condition

6. Wait

7. End

A workflow is the operating system of the campaign.

Channel nodes

Channel nodes are the action steps inside a workflow.

Examples:

Only enabled and connected channels can be used.

If a channel is missing, check Settings → Engagement Channels and user channel connections.

Signal conditions

Signal conditions let workflows branch based on activity.

For example, a workflow can check:

LinkedIn accepted

LinkedIn accepted

LinkedIn accepted

Then branch:

1. Yes → Send LinkedIn message

2. No → Send final email

Signal conditions help campaigns adapt instead of sending the same sequence to everyone.

Wait steps

Wait steps control timing between actions.

Examples:

Wait for 1 day
Wait for 3 days
Wait before checking LinkedIn accepted
Wait before sending final email

Wait for 1 day
Wait for 3 days
Wait before checking LinkedIn accepted
Wait before sending final email

Wait for 1 day
Wait for 3 days
Wait before checking LinkedIn accepted
Wait before sending final email

Wait steps help campaigns feel more natural and avoid sending too many messages too quickly.

Branching

Branching lets a campaign respond differently based on what the target contact does.

Example:

Send LinkedIn connection request
Wait 1 day
Check if LinkedIn accepted
If yes, send LinkedIn message
If no, send final email

Send LinkedIn connection request
Wait 1 day
Check if LinkedIn accepted
If yes, send LinkedIn message
If no, send final email

Send LinkedIn connection request
Wait 1 day
Check if LinkedIn accepted
If yes, send LinkedIn message
If no, send final email

Branching helps campaigns become more contextual.

Message personalization by ICP and persona

Campaign messages can be crafted by ICP and persona.

This is important because different target companies and target contacts care about different things.

For example, you may write a different email for:

1. Hospitality ICP

2. Schools ICP

3. Healthcare ICP

4. Corporate ICP

You may also write different messages for:

1. CEO persona

2. Revenue persona

3. IT persona

4. Operations persona

This helps your campaign speak to the right context instead of sending one generic message to everyone.

Same message vs different message

When configuring a message step, you may be able to choose:

1. Same message to all

2. Different message by ICP

3. Different message by persona

Use same message when the audience is very focused.

Use different messages when the list includes multiple ICPs or personas with different pain points.

Same message to all

Use Same message to all when every target contact should receive the same message.

This works best when:

1. The target list is narrow

2. The ICP is consistent

3. The persona is consistent

4. The message angle is the same

5. The campaign goal is simple

Example:

All contacts are RevOps leaders at B2B SaaS companies

All contacts are RevOps leaders at B2B SaaS companies

All contacts are RevOps leaders at B2B SaaS companies

Different message by ICP

Use Different message by ICP when companies in the list belong to different ICPs.

For example, Snowbricks may want different messaging for:

1. B2B SaaS Companies

2. Data Infrastructure Companies

3. AI-Native GTM Companies

4. Enterprise Sales Organizations

Each ICP may have a different business problem, so the message should reflect that.

Different message by persona

Use Different message by persona when contacts in the list have different roles.

For example, Snowbricks may want different messaging for:

1. Revenue Operations Leader

2. Head of Data

3. VP Sales

4. Founder or CEO

Each persona cares about a different outcome, so the message should match the person.

Sender selection

Campaign messages need a sender.

The sender must have the required channel connected.

For example:

1. Email steps require a connected Google Workspace Gmail mailbox.

2. LinkedIn steps require a connected LinkedIn account.

3. iMessage steps require a connected iMessage line.

If a sender is not available, check the user’s connected channels.

Variables

Messages may support variables.

Variables help insert contact, company, or campaign context into the message.

Examples may include:

1. Contact name

2. Company name

3. Title

4. Industry

5. Sender name

6. Website or signal context when available

Use variables carefully.

A good variable makes the message more relevant. A bad or missing variable can make the message feel automated.

Campaign preview

Before launch, review the campaign preview.

The preview helps you check:

1. Campaign name

2. Purpose

3. Target list

4. Workflow

5. Channels

6. Senders

7. Message content

8. Timing

9. Audience readiness

Do not launch until the preview looks right.

Campaign Insights

Insights show what is happening across the campaign.

Insights may include:

1. Target companies

2. ICP counts

3. Target contacts

4. Persona counts

5. Conversations

6. Positive replies

7. Neutral replies

8. Negative replies

9. Message counts by channel

10. Email performance

11. LinkedIn performance

12. iMessage performance

13. Average response time

14. Average open time when available

Use Insights to understand campaign performance and improve future campaigns.

Companies inside a campaign

The Companies tab shows the target companies connected to the campaign.

Use it to review:

1. Company count

2. ICP fit

3. Company status

4. Website

5. Industry

6. Employee count

7. Created date

8. Updated date

This helps you understand the account audience behind the campaign.

Contacts inside a campaign

The Contacts tab shows the target contacts connected to the campaign.

Use it to review:

1. Contact count

2. Persona fit

3. Contact status

4. Company

5. Title

6. Email

7. Phone

8. LinkedIn availability

9. Created date

10. Updated date

This helps you understand the people being engaged.

Target List tab

The Target List tab shows the source audience behind the campaign.

Use it to understand:

1. Which list powers the campaign

2. How companies were added

3. How contacts were added

4. Whether the list is Ready

5. Whether the list needs changes before launch

Campaigns should run from clean target lists.

Files and Notes

Campaigns may include Files and Notes.

Use Files for:

1. CSV imports

2. Campaign source files

3. Supporting research

4. Event lists

5. Planning documents

Use Notes for:

1. Campaign strategy

2. Message angle

3. Targeting assumptions

4. Launch notes

5. Follow-up reminders

6. Lessons learned

Good notes make campaigns easier to review and improve later.

Console

The Console shows campaign execution.

Use Console to see:

1. What executed

2. What is pending

3. What failed

4. Which contact is on which node

5. Which channel was used

6. When the next action is scheduled

7. Message details

8. Node status

Console is useful when a campaign is running and you want to understand exactly what is happening.

Campaign execution statuses

Console activity may include statuses such as:

Use the Console to investigate campaign execution and troubleshoot issues.

Launch requirements

Before launching a campaign, make sure:

1. Workspace is on a paid plan

2. Required channels are enabled

3. Required user accounts or lines are connected

4. Target List is ready

5. Contacts are in Target status

6. Contacts have required channel data

7. Workflow is complete

8. Messages are written

9. Senders are selected

10. Timing looks correct

11. Exclusions are handled

Do not launch a campaign from an unfinished target list or incomplete workflow.

Campaign lifecycle

A typical campaign lifecycle looks like this:

1. Build or select a Target List

2. Create a campaign

3. Add a name and purpose

4. Select the Target List

5. Import a workflow or build one from scratch

6. Configure channel nodes

7. Write messages by ICP or persona when needed

8. Preview the campaign

9. Launch the campaign

10. Monitor Console

11. Review Conversations and Insights

12. Pause, edit, or end the campaign when needed

13. Use results to improve future campaigns

Example campaign

Here is an example for Snowbricks.

This campaign uses a target list, multiple channels, signal conditions, and persona-specific messaging.

Example workflow

A simple multi-channel campaign may look like this:

Start
↓
Email: Intro Email
↓
Wait 1 Day
↓
LinkedIn: Connection Request
↓
Signal: LinkedIn accepted?
   Yes → LinkedIn: Send Message
   No → Email: Final Email
↓
End

Start
↓
Email: Intro Email
↓
Wait 1 Day
↓
LinkedIn: Connection Request
↓
Signal: LinkedIn accepted?
   Yes → LinkedIn: Send Message
   No → Email: Final Email
↓
End

Start
↓
Email: Intro Email
↓
Wait 1 Day
↓
LinkedIn: Connection Request
↓
Signal: LinkedIn accepted?
   Yes → LinkedIn: Send Message
   No → Email: Final Email
↓
End

This workflow uses email first, then LinkedIn, then branches based on whether the LinkedIn connection request was accepted.

Recommended setup workflow

Use this workflow when creating a new campaign.

1. Confirm your workspace is on a paid plan

2. Confirm the required channels are enabled

3. Confirm senders have connected accounts or lines

4. Open Campaigns

5. Select Add

6. Enter campaign name

7. Enter campaign purpose

8. Select a Target List

9. Import an existing workflow or build a new one

10. Configure workflow nodes

11. Write messages

12. Preview the campaign

13. Launch when ready

Recommended review workflow

Use this workflow before launching.

1. Review campaign setup

2. Review Target List

3. Review Companies

4. Review Contacts

5. Confirm ICPs and personas

6. Confirm channel availability

7. Confirm sender availability

8. Review all messages

9. Review waits and branches

10. Review exclusions

11. Preview the campaign

12. Launch only when clean

Recommended monitoring workflow

Use this workflow after launch.

1. Open the campaign

2. Review Insights

3. Open Console

4. Check Executed, Pending, and Failed steps

5. Review replies

6. Review positive, neutral, and negative intent

7. Pause the campaign if something looks wrong

8. Update future workflows based on results

Best practices

1. Start with a clean Target List
   Campaign quality depends on audience quality.

2. Use paid plans for campaigns
   Campaign execution requires enabled engagement channels.

3. Enable only the channels you plan to use
   Keep the workflow focused and operationally clean.

4. Connect senders before building workflows
   Missing senders can block campaign steps.

5. Write messages by ICP or persona when needed
   Different audiences need different context.

6. Avoid generic outreach
   Use company, persona, and signal context.

7. Use wait steps
   Give contacts time to respond before sending another message.

8. Use branching
   Campaigns should adapt based on signals and replies.

9. Preview before launch
   Catch workflow, sender, and message issues before the campaign runs.

10. Monitor Console after launch
    Console shows what is actually happening.

11. Pause when something looks wrong
    Do not let a bad workflow keep running.

12. Use replies to improve targeting
    Positive and negative replies both teach you what to change.

13. Track performance by ICP and persona
    Some segments will perform better than others.

14. Keep campaign notes
    Document assumptions, changes, and learnings.

Troubleshooting

I cannot launch a campaign

Check:

1. Workspace is on a paid plan

2. Target List is selected

3. Target List has contacts

4. Contacts are in Target status

5. Workflow is complete

6. Messages are written

7. Required channels are enabled

8. Required senders are connected

9. Required contact data exists

10. Exclusions are handled

I do not see Email nodes

Check:

1. Email is enabled in Settings → Engagement Channels

2. Workspace is on a paid plan

3. A Google Workspace Gmail mailbox is connected

4. The sender is available

5. Contacts have email addresses

I do not see LinkedIn nodes

Check:

1. LinkedIn is enabled in Settings → Engagement Channels

2. Workspace is on a paid plan

3. A LinkedIn account is connected

4. Contacts have LinkedIn profiles when needed

5. The sender is available

I do not see iMessage nodes

Check:

1. iMessage is enabled in Settings → Engagement Channels

2. Workspace is on a paid plan

3. An iMessage line is connected

4. Contacts have phone numbers

5. The line is available

Messages are not sending

Check:

1. Campaign is Running

2. Workflow is saved

3. Sender is connected

4. Contact has required channel data

5. Contact is in Target status

6. Send limits are available

7. User schedule allows sending

8. Console does not show failures

Campaign is running but nothing is happening

Check:

1. Workflow has pending wait steps

2. Campaign schedule

3. Sender schedule

4. Channel limits

5. Console pending queue

6. Target contacts

7. Whether the campaign is waiting for a signal condition

A workflow step failed

Open Console and review the failed step.

Common causes include:

1. Missing email

2. Missing LinkedIn profile

3. Missing phone number

4. Disconnected sender

5. Channel disabled

6. Send limit reached

7. Invalid message content

8. Contact excluded

9. Campaign paused or ended

I need to stop a campaign

Use Pause Campaign to stop execution temporarily.

Use End Campaign only when the campaign is complete or should not run again.

I changed a workflow but it did not apply

Make sure you save the workflow.

If the campaign is already running, review whether changes apply to future steps only.

Replies are not showing

Check:

1. The channel is connected

2. The reply had time to process

3. The conversation is connected to the campaign

4. Filters are not hiding replies

5. Console does not show failed nodes

Insights look empty

Insights may populate after campaign activity starts.

Check:

1. Campaign is Running

2. Messages have been sent

3. Replies or opens have occurred

4. Target companies and contacts are present

5. Filters are not hiding activity

FAQ

What is a campaign?

A campaign is a workflow that engages contacts from a Target List across enabled channels such as email, LinkedIn, and iMessage.

Do campaigns require a paid plan?

Yes. Campaign execution requires engagement channels, and engagement channels are available on paid plans.

What is required before launching a campaign?

You need a paid plan, enabled channels, connected senders, a target list, target contacts, a workflow, and message content.

What is a Target List in a campaign?

The Target List is the audience for the campaign. It contains the companies and contacts the campaign will use.

Can I import a workflow from another campaign?

Yes. You can import a workflow from an existing campaign and edit it for the new audience.

Can I use multiple channels in one campaign?

Yes. A campaign can use email, LinkedIn, and iMessage when those channels are enabled and connected.

Why do only some channels show up in the workflow?

Only enabled and connected channels are available in workflow nodes.

Can I write different messages by ICP?

Yes. You can write different messages for different ICPs when the campaign audience includes multiple company segments.

Can I write different messages by persona?

Yes. You can write different messages for different personas when the campaign audience includes multiple target contact types.

What is the Workflow tab?

The Workflow tab is where you build the campaign sequence, including channel nodes, wait steps, signal conditions, branches, and end states.

What is the Console?

The Console shows campaign execution, including executed, pending, and failed steps.

What are Insights?

Insights summarize campaign performance across companies, contacts, ICPs, personas, conversations, messages, channels, and reply intent.

Can I pause a campaign?

Yes. Use Pause Campaign when you want to stop execution temporarily.

Can I end a campaign?

Yes. End a campaign when it is complete or should no longer run.

What should I review after a campaign launches?

Review Console, replies, Conversation Signals, positive intent, failed steps, and performance by ICP, persona, and channel.

Next step

Next, go to Workflows to learn how to build campaign logic with channel nodes, wait steps, signal conditions, branching, and message personalization.