You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a custom UI for in-app messages, and thus have implemented all tracking & logging using the exposed methods. One thing that we haven't found functionality for, are the "custom event" and "custom attribute" on-click behavior for in-app messages and content cards, as is provided by your dashboard.
The Web SDK provides this in the form of handleBrazeAction, but we cannot find an equivalent in the iOS documentation.
Workarounds
We are thinking about using the key-value pair feature of in-app customisation to specify the "custom event"/"custom attribute" to log out on click, but that involves substantial changes on our part.
Ideal Solution
No response
Other Information
No response
The text was updated successfully, but these errors were encountered:
As noted in the documentation linked, the Braze Actions feature is added as of version 5.4.0 of the Braze Swift SDK. In order to take advantage of that new feature on the iOS side, reference these docs to migrate from the Appboy SDK (ObjC) to the Braze SDK (Swift). The on-click behavior would then be triggered automatically without any further code integration on your end.
What problem are you facing?
We have a custom UI for in-app messages, and thus have implemented all tracking & logging using the exposed methods. One thing that we haven't found functionality for, are the "custom event" and "custom attribute" on-click behavior for in-app messages and content cards, as is provided by your dashboard.
The Web SDK provides this in the form of handleBrazeAction, but we cannot find an equivalent in the iOS documentation.
Workarounds
We are thinking about using the key-value pair feature of in-app customisation to specify the "custom event"/"custom attribute" to log out on click, but that involves substantial changes on our part.
Ideal Solution
No response
Other Information
No response
The text was updated successfully, but these errors were encountered: