We are using the AS connector for real-time ongoing Salesforce journeys. With the Journey builder connector, we are only able to send data as strings and not any other type of attribute. Attempting to send over attributes other than strings results in huge errors. Currently, we are sending these attributes (booleans, dates and badges) using the Email Studio. Also, because this connector is set on "In Audience at End of Visit" this results in a ~15 minute delay of data being populated in the data extension. This has caused many users to be removed from the journey prematurely as while they do qualify for the journey fields were not being updated in a timely manner. Can we use a Function or a Custom Webhook connector to address both issues? Which one is a better solution, Functions or Custom Webhook and what are the pros and cons associates with each one?
... View more