Simon connects to [Oracle Responsys](🔗) so you can send triggered emails and sync content to your Responsys profile extension tables (PET).
Automate core lifecycle email campaigns based on change in segment state
Drive rich personalized emails based on customer data and custom content
### Before You Begin
Review [Flows and Channel Actions: How They Work](🔗)
# Getting Started
## Understanding Lists & Profile Extension Tables
Marketing channels keep master lists of contacts. Responsys calls these [Profile Lists](🔗). These lists can be large. Every extra piece of new information per customer can slow things down exponentially. To solve this, channels may use smaller, lighter tables as addendums to your main table to store these extra details about your customers so you can more nimbly retrieve the most relevant information. In Responsys, these are known as _Profile Extension Tables_ (PET).
Profile Extension Tables are used to "store additional attributes that define behavioral, demographic or profile preference characteristics of your contacts" and are filterable. Visit the [Responsys Help Center](🔗) to learn more about PETs.
We sync to Responsys Profile Extension Tables (PET) so that you can leverage this extra data when targeting your customers and orchestrating your campaigns.
## Setup Syncing
To prepare Responsys for syncing:
**Setup a PET in Responsys** - You first need to [**Create a PET**](🔗), in Responsys, with one column that corresponds to each column in custom contexts. All fields in that PET should be set up as a [**Long Text** data type.](🔗)
**Ensure your contacts exist in Responsys** - To sync a contact from Simon to a PET in Responsys, the contact must already exist in Responsys with an assigned Recipient ID (RIID), [a unique identifier assigned in Responsys and found in a profile list.](🔗) Without an RIID we can't sync the contact and it'll be skipped.
**Ensure your contacts in Responsys have an email address** - In Responsys, the contact must also have email address in the PET or list chosen for sync'ing. Without an email address, an email message will not be sent.
**Choose the action** - When building flows in Simon, use the Responsys PET action that works with your organization's setup and needs
## Setup Triggered Messaging
To prepare Responsys for triggered messaging:
**Triggered messaging using Profile Lists** - If you're only sending a triggered message to members of a Profile List _and_ your only use that Profile List, just make sure the data you need exists in it.
**Triggered messaging using PETs** - If you're sending triggered messages to members of a PET and the emails live in that PET, make sure the table exists first with an email mapped to an RIID (see **Considerations** below).
**Data Ingestion Timelines** - Data is ingested from Responsys hourly, so if you recently added a new template or table it may not be available to you right away in Simon.
**One-to-One Identifiers** - We **_highly recommend_** contacts have **_one email per RIID_**. Responsys sends email through an operation that _merges_ contacts. RIIDs with multiple emails addresses cause issues and if multiple recipients are found we can't send a message to any of those emails associated with that RIID.
**PET Expirations** - If you set a PET to expire in Responsys, you also need to stop the corresponding flow in Simon (flows don't have an _end date_ concept so this has to happen manually). To help track this, you can [configure alerts in Simon to be notified if the PET is missing](🔗).
# Action Types
|[Send Triggered Email To Contact](🔗)||Send triggered messages to your contacts using one of your Oracle Responsys templates.||✅||✅||❌||✅|
|[Sync Contact to Profile Extension Table (PET)](🔗)||Add or remove contacts from a PET||✅||✅||✅||✅|
|[Add to and Update Profile Extension Table (PET)](🔗)||Update contacts in a PET||✅||❌||❌||✅|