Skip to main content

Using Custom Fields in Pardot Dynamic Content

Use the correct merge tag syntax for each part of a Pardot Dynamic Content block. This prevents sync errors. It also ensures your custom field values display correctly.

Overview

When you use a custom Pardot field inside a Knak Dynamic Content block, you must use two different merge tag formats.

One merge tag is used for the Dynamic Content condition set. The other is used for the text content block that displays the field value.

Using the wrong syntax can cause one of the following issues:

  • A sync error when you save or sync your content.

  • An empty value when the email renders.

Why Two Merge Tags Are Required

Pardot treats custom fields differently depending on where they are used.

  • The condition set expects the custom field API name.

  • The text content block expects the merge tag that outputs the field value.

Standard Pardot fields, such as First Name, work with the same syntax in both locations. This limitation only applies to custom fields.

Use the Correct Merge Tag

Location

Merge Tag

Dynamic Content condition set

Nickname__c (bare API name, no brackets) or {{Recipient.Nickname__c}}

Text content block

{{Recipient.Nickname}}

Example

Step 1: Create the Merge Tag for the Dynamic Content Condition

  1. Create a merge tag using your custom field API name.

  2. Use either:

    • Nickname__c

    • {{Recipient.Nickname__c}}

  3. Add the merge tag to the Dynamic Content condition.

See Set Up Dynamic Content for Pardot for step-by-step instructions.

Step 2: Create the Merge Tag for the Text Content Block

  1. Create a merge tag that outputs the custom field value.

  2. Use:

    • {{Recipient.Nickname}}

  3. Add the merge tag to a Text content block.

Verify the Setup in Your Email

After you configure the Dynamic Content condition and the Text content block, your email should look similar to the following example.

The Dynamic Content block contains the condition. The Text content block contains the merge tag that displays the custom field value when the email is sent.

Common Sync Error

If the condition set contains the wrong merge tag, you may see an error similar to the following:

"Incorrect tag replacement language detected: We can't save this content because the merge field {{Recipient.Nickname}} is invalid. Update the field and try again."

This error appears because the merge tag in the condition set does not match the format Pardot expects.

Edge Cases

Some organizations sync custom fields from Salesforce instead of creating them directly in Pardot.

In these cases, the Field ID may include __c, such as:

Nickname__c

If your field ID includes __c, you can use:

{{Recipient.Nickname__c}}

for both:

  • The Dynamic Content condition set.

  • The text content block.

This syntax works because the field identifier already matches the value Pardot expects.

Troubleshooting

If your custom field is not working, or you receive the following sync error:

Sync failed: HTML dynamic content validation failed: Group #2: Segments in this group use a different Pardot integration than the one being synced to.; Group #3: Segments in this group use a different Pardot integration than the one being synced to.

"Sync Failed: Dynamic Content Validation Failed" error message

Try these steps:

  1. Verify the custom field API name or Field ID in Pardot.

  2. Confirm you are using the correct merge tag for the condition set.

  3. Confirm you are using the correct merge tag in the text content block.

  4. If your Field ID includes __c, try using {{Recipient.<FieldID>__c}} in both locations.

  5. Sync the content again.

Need more help? Contact support via live chat using the chat bubble in the bottom right corner or email support@knak.com.

Related Articles
Did this answer your question?