Send query results to SAP Emarsys¶
SAP Emarsys is an omnichannel customer engagement platform for personalizing customer interactions across channels to increase customer engagement and lifetime value.
Use contact lists in SAP Emarsys as an alternative to segments when selecting the recipient source for a campaign.
You can configure Amperity to maintain contact lists in SAP Emarsys using the SAP Emarsys REST API. Amperity updates the contact list in SAP Emarsys to match the audience sent from Amperity. Amperity:
Adds contact lists when they don’t exist in SAP Emarsys.
Updates contact attributes and profile information for contacts already in a contact list to match what is sent from Amperity.
Adds contacts to a contact list when they don’t exist in SAP Emarsys.
Removes contacts from a contact list when they don’t exist in the audience sent from Amperity.
Caution
This destination is available for sending query results to SAP Emarsys after it is configured by a Datagrid Operator or your Amperity representative.
If this destintion cannot be selected from the campaigns editor or activations canvas ask your Datagrid Operator or Amperity representative to configure a destination for sending query results to SAP Emarsys.
Build query¶
Build a query that returns an email address or a phone number, along with up to 400 additional profile attributes.
Profile attributes sent to SAP Emarsys must match any of the SAP Emarsys system fields or any custom fields that you have defined.
The name of the system or custom field sent from Amperity must match the name of the system attribute or custom field in SAP Emarsys.
Amperity will automatically pass the Amperity ID to the contact list when a custom field named external_id exists in the contact list.
Important
Log in to SAP Emarsys to find the correct string value for the system or custom field. Choose Management and open the Field Editor.
Use the Field String ID column to indentify the correct system or custom field name. System fields are available from the System fields tab and custom fields are available from the Custom fields tab.
Example
The following query returns an audience with profile attributes mapped to system fields in SAP Emarsys and a custom field named external_id for the Amperity ID. The WHERE clause ensures that only records with an email address are part of the audience.
1SELECT
2 amperity_id AS 'external_id'
3 ,given_name AS 'first_name'
4 ,surname AS 'last_name'
5 ,email AS 'email'
6 ,phone AS 'phone'
7 ,address AS 'address'
8 ,city AS 'city'
9 ,state AS 'state'
10 ,postal AS 'zip_code'
11 ,country AS 'country'
12 ,birthdate AS 'birth_date'
13FROM Merged_Customers mc
14WHERE (
15 LOWER(mc.email) IS NOT NULL
16)
Important
Test the connection with SAP Emarsys by using an audience with a very small membership. For example: 10 or 100 members or the minimum audience size recommended by SAP Emarsys. Send the test audience to SAP Emarsys and verify the audience is correct in SAP Emarsys. Make adjustments if necessary. Only send full audiences after validation is complete.
Add orchestration¶
An orchestration defines the relationship between query results and a destination, including the destination and the frequency at which an orchestration runs.
To add an orchestration
Open the Activations page, select the Orchestrations tab, and then click the Add orchestration button. This opens the Add orchestration dialog box.
From the Object type dropdown, select Query.
From the Object dropdown, select the query for which results is sent to SAP Emarsys.
From the Destination dropdown, select a destination that is configured for sending data to SAP Emarsys.
Verify all settings.
Set the workflow to Manual. You can change this to automatic later, after verifying the end-to-end workflow.
Click Save.
Run orchestration¶
Run the orchestration manually to validate that it works.
To run the orchestration
Open the Activations page, select the Orchestrations tab, and then open the menu for the SAP Emarsys orchestration. Select Run.
The Status column for the orchestration updates to say “Waiting to start”, after which the notifications pane updates to include a notification that shows the current status.
When the orchestration has run successfully, the status is updated to “Completed”.