You can include personalized relational table (RT) data to your simple mobile app message draft by adding a formatted placeholder to the appropriate field. You cannot use child relational table data.

Here's how it works:

1. Go to Data and associate the relational table with the organization's mobile app database. You may need to import a new relational table first.
2. On the Relational Table tab, select and open the relational table and create a relational table query.
3. Now, you can go to the mobile app message draft and personalize your message that uses relational table personalization tags in various fields.

The general format for this placeholder is %%RT::path to query::field name%%. You can find additional examples below, but first, review the rules to ensure that you are formatting the tag correctly and placing the tag in the correct fields.

Formatting the tag

• %%RT denotes relational table personalization. RT is case-sensitive.
• Specify the full location of the relational table query. /Shared and /Private is not case-sensitive.
• The relational table must be associated with the contact source that is selected on the first page of the mobile send experience.
• Use an existing relational table query.

Note: Although you can add relational table personalization to in-app, data, and extension templates, you must make sure that the tags are correct as inline error validation is not available.

Where to use relational table personalization mobile app messages

Push notifications

Supported fields:

• Title
• Subtitle (iOS only)
• Notification message

APIs

Supported activities:

• Push to Segment/Contact Source APIs. Error validation is not available.
• Push to Contact/Device API (inline or with published messages).

Rich / Inbox messages

Inbox, in app, and push extension fields and templates are are not supported by relational table personalization:

• HTML content built in content builder
• Inbox only message fields in the send experience
• Inbox templates fields added to a simple message in the send experience

Examples of relational table personalization tags

Personalization referencing one relational table

In this example, All_Mobile_Users is the relational table query and Favorite_Team is the column name where personalized data is pulled and added to your message.

Special offer just for you! All %%RT::/Shared/All_Mobile_Users::Favorite_Team%% gear is on sale + free shipping when you order through the app!

Result: Special offer just for you! All Broncos gear is on sale + free shipping when you order through the app!

Multiple relational table personalizations

You can add more that one relational table personalization tag in the same field.

%%RT::/Shared/All_Mobile_Users::Member_Level%% member, check out all the latest rewards! Use promo code %%RT::/Shared/All_Parents_New::Member_Code%% on your next reservation.

Result: Gold member, check out all the latest rewards! Use promo code GOLD2018 on your next reservation.

Relational table personalization with other personalization types

You can use relational table personalization with regular personalization in the same field.

Hi %%First Name%%, still interested in seeing %%RT::/Shared/All_Mobile_Users::Last_Country_Page%%? A special offer is waiting for you in our app.

Result: Hi Paul, still interested in seeing Italy? Check out a special offer in our app.

Relational table personalization with OrderBy clause

It is possible that the relational table query can return multiple rows. Use the OrderBy clause to make sure that only one row is displayed in the message. If you use OrderBy in the query, the format is %%RT::path to query::field name::order by fields (separated by comma)[asc/desc]%%.

Multiple OrderBy fields are supported if they are separated by a comma. Specify asc or desc for each OrderBy field.

Save %%RT::/Shared/All_Services_New::Price::Location asc%% off your next mobile app order!

Result: Save $10 off of your next mobile app order!