Contact Us

June 11, 2024

May 13, 2026 2:49 pm

Passing Einstein Engagement Split Personas using AMPscript

Share with

Watch related videos on YouTube — Search results for: Passing Einstein Engagement Split Personas using AMPscript

Understanding the Challenge

The Einstein Engagement Split in Journey Builder categorizes subscribers into personas such as Loyalists, Window Shoppers, and Dormant. To pass the persona value using an AMPScript personalization string, teams need a more integrated approach.

Possible Solutions

A community member asked about using an Update Contact activity to set the correct value in a data extension for every path/persona. However, this approach has its limitations, as it may not apply to the current journey’s context.

Another possible solution is to use send logging and ensure that the feeder data extension has the Einstein Engagement Split personas available. This approach allows for further segmentation to third-party services.

Technical Implementation

To implement this solution, teams can use a combination of AMPScript and Server-Side JavaScript (SSJS). The following code snippet demonstrates how to use AMPScript to get the Einstein Engagement Split persona data:

AMPScript example

%%[ var @persona = LookupRows('Einstein_MC_Predictive_Scores', 'ContactKey', _subscriberkey) ]%%

This code snippet uses the LookupRows function to retrieve the Einstein Engagement Split persona data for the subscriber.

The root cause of this challenge is the lack of a native and integrated way to pass Einstein Engagement Split persona values using AMPScript in Journey Builder.

Best Practices and Recommendations

To ensure a smooth implementation, teams should follow these best practices:

Checklist

  • Use a combination of Update Contact activity and AMPScript to set the correct value in a data extension for every path/persona.
  • Ensure that the feeder data extension has the Einstein Engagement Split personas available.
  • Use send logging to write the Einstein Engagement Split persona attributes to the send log.
  • Test and validate the implementation to ensure that the persona data is being passed correctly.
  • Monitor and analyze the results to optimize the Journey Builder configuration.

Frequently Asked Questions

What is the Einstein Engagement Split in Journey Builder?

The Einstein Engagement Split in Journey Builder categorizes subscribers into personas such as Loyalists, Window Shoppers, and Dormant.

How can I pass the Einstein Engagement Split persona value using an AMPScript personalization string?

Use a combination of Update Contact activity and AMPScript to set the correct value in a data extension for every path/persona.

What is the benefit of using send logging to write the Einstein Engagement Split persona attributes to the send log?

This approach allows for further segmentation to third-party services.

How can I ensure a smooth implementation of the Einstein Engagement Split persona passing?

Follow best practices, such as using a combination of Update Contact activity and AMPScript, and testing and validating the implementation.

Genetrix Technology · Salesforce Marketing Cloud Partner

Need help shipping this in production?

Genetrix builds and untangles Salesforce Marketing Cloud and Agentforce setups for teams that want it done right the first time. If anything in this post sounds familiar, talk to us before it ships.

Get in Touch with Genetrix →

Blogs for the

Business-Savvy!​

Let’s Connect

A 30 min no cost strategy session
with cloud support expert

Let’s Connect

A 30 min no cost strategy session
with cloud support expert