Once you've created your custom action, you're ready to clear the smell of wine and cheap perfume, hold on to that feeling and roll the dice - just one more time.

First, you'll read the audience profiles into the journey, this will need to be throttled at up to 1,000 records per second

Next, you will add the phraseeRealtimeAPI Custom Action into the journey canvas from the Actions section of the menu:

Now, you will configure the Action.

No further access configuration is required so set this to none.

The crucial step is with the endpoint configuration, specifically the configuration of the three query parameters:

Campaign_id is taken from the Phrasee UI, if you're not sure where, check this out.

Recipient_id and Delivery_id are populated by AJO fields, specifically some Journey Properties:

It'll look like this once done:

Now that the Action is configured, you are able to use the response to this API call for personalization in messages.

Let's start with using the Phrasee generated language in an email subject line, but the same process applies for other content types.

Opening the Personalization Dialog next to the subject field, you need to navigate to the Contextual attributes > Journey Properties > Actions menu to access the phraseeRealtimeAPI content

The attribute you need to use bring the content into the subject line is variant_text. You will need to wrap the attribute in a third set of handlebars in order to render the text correctly (without any html encoded funny business - see below for an explanation of this.)

But what if you have replacer variables in your subject lines, like first name, or product? Things get a little smoky in this room and you have to use some other functions to replace the merge tags.

For example, Phrasee generated language contains a placeholder variable (helpfully named NAME_MERGE_TAG in this example) that needs to be replaced with a customer's first name.

First, add the let helper function to the canvas:

Rename the variable to subject, and add the third set of handlebars to the output:

Replace the expression with the replace helper function (found under string functions):

Replace the first string within the replace function with the variant text from the phraseeRealtimeAPI (found via the contextual attributes menu as above):

Note the ` around the action-id if copying from elsewhere.

Replace the second string with the placeholder variable (remember this example uses NAME_MERGE_TAG), noting the " marks that turn the value red:

Finally, replace the third string placeholder with the customer's first name from the profile attributes:

This code snippet is reusable as the action-ID won't change between journeys, so it's recommended to save this snippet as a Fragment for convenience.

If you have multiple replacer tags in use, you can repeat the process with a new let/replace function, just be sure to update the outputting variable to the fully replaced one:

Now, you've got personalized Phrasee-generated content into your subject lines, but they're just out there in the lonely world. But, don't stop believing, there's one more code snippet that's living just to find the opens and send them on the midnight train back to Phrasee's optimization engine.

You need to add a small code snippet into the email html, just above the closing </body> tag.

Whether you are coding in HTML, or using the drag and drop interface, the code snippet required is:

You will need to replace the src in the above. You can find the statistics_url in the same Contextual attributes > Journey Properties > Actions menu as before:

We also recommend saving this snippet as a Fragment for ease of reuse.

That's streetlights, people. Publish the journey and stop searching the night for optimized, performant content.