Adding On-Site Messaging is as easy as it gets, to achieve this tailor made experience for the user you just have to;
To be able to integrate On-site messaging our team needs to enable the access for it. You can request access by writing an email to firstname.lastname@example.org or through your dedicated Delivery Manager. Please refer the Merchant ID (MID) and/or the name of your brand/company (merchant name), the countries you request access and the environment (playground or production).
The On-Site Messaging native view in Android is called KlarnaOSMView. You can create KlarnaOSMView programmatically or inflate from a XML file. Additionally you can also set parameters from the XML.
You can create the native view programmatically and place it in your application with desired layout options.
Optionally you can also create the native view in your XML and get the view instance programmatically either by findViewById or generated DataBinding instance of your layout.
Parameters used for the KlarnaOSMView are set as variables of the View instance or as attributes in the XML declaration. These can be identifier string values, amount or enumeration values.
|clientId||String*||On-Site Messaging Client Identifier gathered from Klarna Merchant Portal.|
|placementKey||String*||Placement key identifier from Klarna Merchant Portal.|
|locale||String*||Locale string for the placement configuration, default value is en-US.|
|purchaseAmount||Long?||Amount for the placement. Set in micro units ($120.00 = 12000), used for amount based credit promotions.|
|environment||KlarnaOSMEnvironment*||Enumerated environment value to specify merchant’s running environment. Default value isDEMOenvironment.|
|region||KlarnaOSMRegion*||Enumerated region value to specify merchant’s running market region.|
|theme||KlarnaOSMTheme*||Enumerated theme value to specify how to stylize the view on light and dark configurations.|
|hostActivity||Activity*||Activityinstance to specify parent activity. Will be used for inner linking for informational pages. The reference will be kept as a weak reference.|
Environment enumeration will be used to define whether to use a demo placement or fetch placement configurations from either playground or production.
|DEMO||This environment ignores all other parameters and shows a demo placement config containing all On-Site Messaging features.|
|PLAYGROUND||This environment is for placement configurations from playground Merchant Portal.|
|PRODUCTION||This environment is for production builds of the app with placement configurations for production merchants.|
Region enumeration will be used to define which endpoint to connect as a source for the placement configurations.
|EU||Region value for Europe.|
|NA||Region value for North America.|
|OC||Region value for Oceania.|
Theme enumeration will be used to define which style of OSM to be used, depending on either the app’s configuration or the system setting.
|LIGHT||Light style for placement view.|
|DARK||Dark style for placement view.|
|AUTOMATIC||Automatic theme that will use the system’s user interface style.|
All of the parameters for On-Site Messaging are stored as variables on the KlarnaOSMView instance. The required ones need to be set before calling the render method, otherwise the RenderResult will return a validation error for the missing parameter.
The parameters can either be set programmatically or from the XML layout file(except the hostActivity parameter). In both cases, values will be stored in the instance but the render method needs to be called explicitly from the merchant application.
Once you have set all the parameters to the KlarnaOSMView, you are ready to render the actual placement view. To do that, you need to call the render method of the view with the RenderResult callback parameter.
Then, once the render method is called, first the view will validate all the parameters. If there is a missing parameter the RenderResult callback will be invoked with corresponding error values. If parameters are valid then the view will try to fetch placement configuration from On-Site Messaging API. Any errors or failures from this network request will also invoke RenderResult callback if necessary. If the placement configuration is fetched and valid then the KlarnaOSMView will render it with native views and invoke the RenderResult callback with a null value.
The RenderResult callback can be used for logging purposes or to make the KlarnaOSMView visible or not, according to the error.
Similar to other parts of the In-App SDK, On-Site Messaging also makes use of the KlarnaMobileSDKError class. To read more about the error handling and error object properties refer to the On-Site Messaging Error Handling guide.
These are the predefined names for errors that can happen during the placement render flow. These names are available as static variables inside KlarnaOSMError class.
|KlarnaOSMErrorMissingClientId||Client ID was not set. Set the |
|KlarnaOSMErrorMissingPlacementKey||Placement key was not set. Set the |
|KlarnaOSMErrorMissingRegion||Region was not set. Set the |
|KlarnaOSMErrorMissingHost||Hosting activity was not set. Set the |
|KlarnaOSMErrorInvalidPlacementConfig||Fetched configuration from the API can not be rendered by the native view.|
|KlarnaOSMErrorPlacementError||On-Site Messaging API has returned an error. Message of this error will contain information sent from the API.|
|KlarnaOSMErrorNetworkError||A network error occurred and the placement will not be rendered.|
|KlarnaOSMErrorDisabled||Native On-Site Messaging has been disabled by Klarna, the placement will not be rendered.|