Lesson 1.4.5
Push a finished list into your campaign without emailing anyone twice
What this costs
Free. The push itself costs nothing, which is why there is no excuse for skipping the protections.
Before you start
A connected sequencer, and a list carrying the six fields below.
This is the end of every sourcing session: the table goes into the campaign with no CSV, no download and no reformatting. Two things decide whether it goes well, the field mapping and the four import protections, and both take about a minute.
The six fields a campaign actually needs
| Field | Why the campaign needs it |
|---|---|
| Without it the row cannot be sent to at all | |
| first_name | Every opener merges it, and it must be its own column |
| last_name | Separate from first_name, never one combined name field |
| company_name | Merged into the body of almost every sequence |
| website | What the campaign and your CRM both dedupe against |
| linkedin_url | The only thing that makes a LinkedIn step possible later |
The four import protections, and what each one prevents
| Protection | What it prevents |
|---|---|
| Skip leads already in this campaign | A second email to the same person |
| Skip leads in any other campaign | Two of your campaigns hitting one prospect in the same week |
| Skip leads that previously bounced | Sending domain damage you cannot undo quickly |
| Skip unsubscribed leads | The one that is not optional, under any circumstance |
Reconcile out loud, every time
After the push, read three numbers back: how many rows were in the table, how many were pushed, and how many were skipped and for which reason. Rows in the table 412, pushed 389, skipped 23, all already in another campaign. If those three numbers do not add up, something silently dropped and you want to know now rather than in a week.
Fewer rows arrive than you pushed
- What you see
- The campaign count is lower than the table count
- The fix
- Usually the protections working as intended. Read the skip reasons before assuming a bug.
Merge fields are empty in the campaign
- What you see
- Emails send with blank names
- The fix
- The mapping put a combined name column into first_name. Split the column and re push only the affected rows.
Somebody gets two emails from two campaigns
- What you see
- A prospect replies confused
- The fix
- Skip leads in any other campaign was left off. It is off by default in most setups.
Check yourself
0 of 3 answered1.Which import protection is described as not optional?
2.Why must first_name and last_name be separate columns?
3.After a push, which three numbers do you read back?
Try it yourself
Push fifty rows into a campaign with all four protections on, then read back the three reconciliation numbers.
- You have done it when
- The three numbers add up, and you can name the reason for every skipped row.
- Credit budget
- Free.