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?
Yes, you can use a Function or a Custom Webhook connector to address both issues.
A Function connector allows you to write custom code to process data before it is sent to Salesforce. This means that you can use a Function connector to convert non-string attributes to strings, or to delay the sending of data until it is ready.
A Custom Webhook connector allows you to create a custom endpoint that Salesforce can call when a new record is created or updated. This means that you can use a Custom Webhook connector to send data to Salesforce in real time, without having to wait for the next visit.
Which one is a better solution?
The best solution for you will depend on your specific needs. If you need to convert non-string attributes to strings, or if you need to delay the sending of data, then a Function connector is a good option. If you need to send data to Salesforce in real time, then a Custom Webhook connector is a good option.
Pros and cons of each one
Custom Webhook connector
Ultimately, the best way to decide which solution is right for you is to consider your specific needs and requirements.