---
title: PaperTube Pardot Form-to-Salesforce Integration
type: article
created: '2026-04-05'
updated: '2026-04-05'
source_docs:
- raw/2026-01-22-papertube-asymmetric-marketing-call-116363018.md
tags:
- crm-automation
- pardot
- salesforce
- lead-management
- abm
- papertube
- form-integration
- sales-handoff
layer: 2
client_source: null
industry_context: null
transferable: true
---

# PaperTube Pardot Form-to-Salesforce Integration

## Overview

For PaperTube's ABM campaign, landing page form submissions require a non-standard Salesforce integration pattern. Because the campaign targets a pre-defined list of known prospects, form fills do not create new leads — the leads already exist in Salesforce. Instead, the integration must detect an existing lead and flag it with an engagement status to trigger a sales handoff.

This article documents the intended workflow design, key decisions made, and outstanding mapping work as of the January 2026 campaign review.

---

## Context: Why This Differs from a Standard Form Flow

In a typical inbound flow, a form submission creates a new lead in Salesforce and routes it via round robin or assignment rules. PaperTube's ABM campaign inverts this:

- Traffic to landing pages is **directed**, not organic — only targeted prospects receive the email sequence linking to these pages.
- Those prospects are **already loaded as leads** in Salesforce prior to campaign launch.
- A form fill therefore signals **re-engagement from a known lead**, not a net-new contact.

The integration must account for this distinction to avoid duplicate lead creation and to route the engagement signal correctly to sales.

---

## Intended Workflow

```
Prospect fills out Pardot form on ABM landing page
        ↓
Pardot / Account Engagement receives submission
        ↓
Match submission to existing Salesforce lead (by email)
        ↓
Flag matched lead with "engagement" status
        ↓
Trigger sales handoff notification to assigned rep
        ↓
Rep follows up directly
```

### Key Design Decisions

| Decision | Rationale |
|---|---|
| No new lead creation on form fill | Leads are pre-loaded; duplicates would corrupt pipeline data |
| Engagement status flag (not a new record) | Preserves lead history while surfacing intent signal to sales |
| Sales handoff via status trigger, not round robin | ABM leads are pre-assigned; round robin would break rep ownership |
| Direct booking (Calendly-style) **deferred** | Adds complexity around calendar sync and round robin; revisit post-launch if form fill volume is low |

---

## Implementation Notes

### Pardot Form Setup
- A **new Pardot (Account Engagement) form** will be created specifically for the ABM landing pages — not reusing any existing PaperTube form assets.
- The form will be embedded directly into each vertical landing page (food & beverage, supplements, beauty, etc.).
- All CTA buttons on the landing page anchor-link to this form at the bottom of the page; there is no separate form page.

### Salesforce Lead Matching
- On submission, Pardot should match the prospect to an existing Salesforce lead by **email address**.
- Standard Salesforce duplicate rules (email domain + company name match) are assumed to be active; this should be confirmed before launch. See [[wiki/clients/papertube/_index]] for Salesforce access context.

### Engagement Status Flag
- A checkbox or status field on the Salesforce lead record should be updated to reflect **"engaged with ABM content"** upon form submission.
- This flag is the trigger for the sales rep to initiate outreach.
- The exact field name and workflow trigger had **not been mapped** as of the January 2026 call — this is a required pre-launch task.

> **From the call:** *"We'll want to make sure whenever they fill this out that there's a checkbox or something along those lines that flags new engagement from that lead — to therefore hand off to sales."* — Karly Oykhman

### Sales Handoff
- The assigned rep (pre-set on the lead record via the Super Round Robin workaround — see [[wiki/knowledge/crm-automation/salesforce-super-round-robin-workaround]]) receives the engagement signal and follows up directly.
- No automated meeting booking at launch; reps initiate contact manually.

---

## Outstanding Work (as of 2026-01-22)

- [ ] **Map full Pardot-to-Salesforce form flow** with Parag — field mapping, engagement flag field name, and handoff trigger logic
- [ ] **Confirm Salesforce duplicate rules** are active and will prevent new lead creation on form submission
- [ ] **Build Pardot form** in Account Engagement and embed in landing page staging
- [ ] **Define and configure engagement status field** on Salesforce lead object
- [ ] **Test end-to-end**: submit test form → verify lead match → verify flag update → verify rep notification

---

## Related

- [[wiki/knowledge/crm-automation/salesforce-super-round-robin-workaround]]
- [[wiki/clients/papertube/_index]]
- [[wiki/knowledge/abm/fictitious-sender-persona-strategy]]