With the release of Custom Task Types last year, it is also possible to create dedicated task types for better user experience, for example an SMS (or Twilio SMS) task type.
When custom task types are used, outbound data specifies data elements needed for channel activation, for example a mobile phone number, and a marketing user can then specify where that values should come from - a customer profile, recent event or somewhere else.
Any data elements captured as part of Outbound data on task Delivery tab are passed to connector function as part of "outboundProperties" JSON element. For example:
"properties": {
"subject_id": "2987",
"externalCode": "TSK_168",
"channel_user_type": "subject_id",
"parent_event": "external",
"event_datetime_utc": "1666274457377",
"parent_eventname": "external-crm"
},
"outboundProperties": {
"properties": {
"mobile": "+19195551212"
},
},
"identity": {
"identityId": "805bfeca-d9e3-378f-a533-bf5597199652",
"identityType": null
},
With this in mind, in the example above, one would reference mobile phone number as:
mobile_phone = event_body["outboundProperties"]["properties"]["mobile"]
More information about setting up and using custom task types can be found in my post:
Tutorial: SAS Customer Intelligence 360 Custom Task Types
... View more
