Welcome to Phrasee's Leanplum guide! If you're looking for our Chubbyapple documentation, you've come to wrong place.

Let's start by getting the ever-important back-end connections configured just right so you can start sending with aplum... sorry. Aplomb.

Phirst things phirst: We need to get Linked Data setup up properly so your Leanplum account can dynamically pull in Phrasee language.

Everything about optimizing brand language with Phrasee in Leanplum hinges on Linked Data. So, it's very important we set up everything correctly.

Feel free to browse Leanplum's Linked Data documentation before continuing here if you'd like a little more context. Go ahead! We'll wait here.

Now that you've read up on Linked Data, we're ready to get started with setup. If you don't have one already, it's very important to request a Phrasee Real-Time Server Token from your Phrasee Customer Success Manager.

They'll provide you with your token in a txt file in a secure folder when it's ready.

Let's get your unique Phrasee connection configured!

Navigate to Linked Data by hovering over the Data Control menu at the top of your Leanplum window and clicking Linked Data.

Click Add New Source.

Paste the following in to the URL field under Source Properties:

Now, we'll need that token you requested from your Phrasee Customer Success Manager earlier. We're going to add your token so Leanplum passes it back to Phrasee during your live sends.

Saving the token is like embedding a password into your data source, so make sure you keep it safe and don't share it with anyone.

Click Add Header under HTTP Headers.

In the first text box that appears, type Authorization. In the second text box type Bearer. Then, type one space and paste your token.

When you're finished it should look something like this:

Don't worry, that's not a real token. No need to avert your gaze.

Let's move on!

Ensure the radio button next to GET is selected under Type. Under Cache results, select Do not cache results.

A little warning will pop up when you do that asking you to ensure the endpoint can handle this load. Our phirst-class engineers spent innumerable hours over myriad sleepless nights ensuring we can. Don't you worry. We got this.

Great! Everything should be all configured and looking something like this:

When you're satisfied, click Save source in the upper-right corner.

Now, it's time to give your brand new Linked Data Source a name. We suggest something simple and clear written in camel case (i.e. camelCase). You'll be using this name later directly in your emails.

You'll see we've used phraseeCampaign in our example below.

Now, click Save source.

Once you save and name your source, you'll be able to send a preview request. This will allow you to test the connection and see when the JSON object the Phrasee API returns looks like.

All you need to do this quick verification is an experiment_id for an active experiment in your Phrasee account. You can pop the experiment_id into the blank and just throw any old numbers in for the recipient_id and delivery_id for testing purposes.

If it's successfully connected, you should see something like the below:

Wow! Incredibly exciting to have a Linked Data Source all your own. Let's talk really quickly about what those three parameters included in the source URL do.

Each of those placeholders corresponds to a variable we'll be passing along to the Phrasee API. Each one works to help Phrasee determine which subscriber should be served what subject line in real time.

The recipient_id and delivery_id will be populated by system fields in Leanplum. The experiment_id will be provided by you for each new Phrasee experiment you create.

We'll talk about this more later. For now, just know that the existence and correct population of these variables is what makes the entire integration work properly.

Now that we've set up your Linked Data Source, we're going to build a special experiment deployment template for you to use with Phrasee sends. Let's learn why before we do.