Understanding the Problem

The problem arises because the Data Extension (DE) created for the campaign membership only shows campaign member fields, and not contact fields. This is because the DE is automatically generated based on the campaign membership, and does not include additional contact information by default.

The root cause of the issue is that the automatically generated DE for the campaign membership does not include contact fields, and the personalization string %%CampaignMember:Contact:Email%% is not a valid field.

Step-by-Step Solution

To resolve the issue, follow these steps:

1. Select the required fields in the Entry Data tab when configuring the Journey Campaign Entry Source.
2. Save the journey and check the associated DE to ensure that the required fields are included.
3. Use the corresponding personalization string, such as %%CampaignMember:FirstName%%, in the email.

Using AMPScript

Alternatively, you can use AMPScript in the email to pull in the required data. However, this approach requires more expertise and may not be necessary if the required fields can be selected in the Entry Data tab.

AMPScript example

%%[

var @firstName

set @firstName = CampaignMember:FirstName

]%%

Best Practices

To avoid similar issues in the future, make sure to carefully review the fields included in the DE and select the required fields in the Entry Data tab.

Heads up: Always save the journey and check the associated DE to ensure that the required fields are included.

Checklist

• Select the required fields in the Entry Data tab.
• Save the journey and check the associated DE.
• Use the corresponding personalization string in the email.
• Consider using AMPScript as an alternative approach.
• Review the fields included in the DE to avoid similar issues in the future.

What is the purpose of the Entry Data tab in Journey Builder?

The Entry Data tab allows you to select the fields that will be included in the DE for the campaign membership.

Can I use AMPScript to pull in data from other sources?

Yes, AMPScript can be used to pull in data from other sources, but this approach requires more expertise and may not be necessary if the required fields can be selected in the Entry Data tab.

What is the difference between %%CampaignMember:FirstName%% and %%CampaignMember:Contact:Email%%?

%%CampaignMember:FirstName%% is a valid field that corresponds to the first name of the campaign member, while %%CampaignMember:Contact:Email%% is not a valid field and will result in an error.

How do I troubleshoot issues with personalization strings in Journey Builder?

To troubleshoot issues with personalization strings, check the fields included in the DE and ensure that the correct personalization string is being used.