ZapBounce

ZapBounce and Pardot

Pardot, now Account Engagement, syncs bidirectionally with Salesforce. That sync is the thing to plan around before writing any new field.

A verdict written into Pardot syncs to Salesforce, which may sync it back, and a badly configured field can loop between them consuming API calls on both sides.

A bidirectional sync can loop a derived field

Pardot and Salesforce sync mapped fields in both directions. A field updated by an external process in one system propagates to the other, and depending on the sync behavior setting it can propagate back.

That consumes Salesforce API calls and Pardot sync capacity for no benefit, and it is difficult to spot because both systems report the field as current.

The fix is to set the field's sync behavior deliberately: one system is the master, and the other accepts.

How the data moves

  1. Decide the master system before creating the field

    Salesforce usually, since that is where the verification job is easier to schedule. Set the sync behavior to match.

  2. Write the verdict once, to the master

    Never to both. Two writers on a synced field is the loop.

  3. Use the verdict in Pardot's dynamic lists

    Dynamic lists read prospect fields, so the verdict becomes a segmentation input without further work.

  4. Verify before prospects are created where possible

    Form handlers and the API both give you a point before the prospect exists.

Setting it up

  1. Choose Salesforce or Pardot as the master for the verdict field.
  2. Create the field in both and set the sync behavior explicitly rather than leaving the default.
  3. Run the verification job against the master system only.
  4. Build Pardot dynamic lists filtering on the verdict for send segmentation.
  5. Verify new prospects at the form handler before creation.
  6. Monitor the sync queue after the first bulk write to confirm nothing is looping.

Pardot: common questions

Where should the verdict field live?

One master system, with sync behavior set explicitly. Two writers on a synced field is how a loop starts.

How fast does a verdict reach Pardot?

At sync speed, which is not instant. Plan segment builds around that latency.

Can I verify at the form handler?

Yes, and it is the better place. A prospect created with a verdict avoids the whole sync question for new records.

Reference

Check a Pardot export today

100 free checks a month, no card. Unknown results and duplicates are never billed.

Get an API keySee pricing