You may also sync columns from your source to Userflow's object properties. You have the option
of mapping to attributes that already exist on the Userflow object, or to create new attributes for current
and future use.
*NOTE: Aside from groups and memberships on User objects, all other fields will be associated with the Group or User object's attributes field within Userflow.
The Userflow API allows you to create/update both groups and memberships through creating/updating
a user by including the appropriate groups/memberships as fields on the user object in the
request payload.
However, please be aware that their inclusion is not required and at most only one of either groups
or memberships can be set on a user per request. If your intention is only to sync group information,
it may be best to sync Group objects instead.
For more information on groups and memberships, including how they are properly formatted on a User object,
please consult the Userflow API documentation:
Hightouch also supports the ability to prune memberships of a user upon sync through the prune_memberships
property in the request payload. As per the Userflow API documentation:
"By default, the API will only update the memberships/groups that's included in the request. Existing memberships that aren't included will not be removed, unless you set prune_memberships to true. Only set prune_memberships to true, if the groups or memberships list is set and contains all the groups the user belongs to. When a membership is deleted, the group itself is left intact."
When either groups or memberships are chosen to be synced to the destination, Hightouch will give you
the option to toggle membership pruning on or off.
*NOTE: By default, membership pruning is disabled.
Ready to get started?
Jump right in or a book a demo. Your first destination is always free.