Target Endpoint Documentation
This page outlines the technical details of how Daasity pushes data into Sailthru using the Event, List and Job API to update users and trigger automated emails in Sailthru
Last updated
Was this helpful?
This page outlines the technical details of how Daasity pushes data into Sailthru using the Event, List and Job API to update users and trigger automated emails in Sailthru
Last updated
Was this helpful?
The Daasity Audiences product uses three different endpoints in Sailthru:
to add an event to a user profile that can be used to send a triggered email
to update user profiles that allow you to add / update data to be used to segment users
to create or update users to be part of a list
For both the and , Daasity will update the entire list of users generated by the audience and make an API to Sailthru to add / update those users. The only runs as part of the if we have selected to either update an existing list or create a new list
Daasity updates the user profile in Sailthru based on the data provided by the Sailthru Events target
Endpoint:
Frequency: Daily (available to run On-Demand via the UI)
Event Information
Event name
event
Data Mapping
id
Data Mapping
Source
Property Name from Data Mapping Destination
Daasity creates new users or updates existing users based on the report / query that is used to generate the audience by providing the file to Sailthru and requesting an asynchronous update job to be executed
Frequency: Daily (available to run On-Demand via the UI)
N/A
N/A
file - used to indicated that Daasity is sending a file to process
Data Mapping
JSON flag
Assigns "Simple" or "JSON" to file property
Data Mapping
id
Data Mapping
Source
$value
Frequency: Daily (available to run On-Demand via the UI)
User List Actions
User List
list
This endpoint will only execute if updating a list or adding new users to a list have been selected
Endpoint:
If the selection to "Add user to an existing list" or "Add user to a new list" is made in the the Daasity will execute the List API to perform the appropriate action as part of the User Target
Endpoint: