Responsys now supports retargeting use cases for mobile apps through the Responsys with Infinity SDK and Infinity Streams. Responsys with Infinity SDK supports all the current functionality of the Responsys Push SDK and also supports retargeting use cases for mobile apps through Infinity Streams. You will be able to retarget your known mobile app users with follow-up promotional messages for the following mobile app behavioral events: Searched Item, Browsed Item, Added Item to Cart, Removed Item from Cart, Cleared Cart, Updated Stage of Cart, and Purchased Cart.
Note: Currently, retargeting is not currently available for unknown mobile app users.
BEFORE YOU BEGIN:
Customers need to purchase the Infinity Streams Cloud Service SKU (Number B88842) and integrate the Responsys with Infinity SDK within their App. To request access to this feature, please log in to My Oracle Support and create a service request. This feature is currently released under our Controlled Availability program.
Your mobile app must use the Oracle Responsys Mobile App Platform Cloud Service SDK version 6.41.0 (19B) or later. Oracle recommends that your mobile app always use the latest SDK.
The Oracle Marketing Cloud SDK that includes the Responsys SDK and Infinity SDK is available on Oracle.com:
To begin, we will review some information that will help you understand what retargeting can do and how it works.
Retargeting, also known as remarketing, is a form of online advertising that can help you keep your brand in front of bounced traffic after they leave your app.
The retargeting tool is designed to help companies reach the 98% of users who don't convert right away.
Mobile app events (or mobile app actions) are activities initiated by mobile app users. Retargeting is designed to listen for events related to searching, browsing, and actions the mobile app user takes with a shopping cart user interface. These activities include:
|Searched||Mobile app user conducted a search using your mobile app’s search function.|
|Browsed||Mobile app user browsed a product details screen or product quick view overlay on a category screen.|
|Added Item to Cart||Mobile app user added an item to a shopping cart by clicking on the Add button on the product category screen, quick view overlay on the product category screen, and/or on the product details screen.|
|Removed Item from Cart||Mobile app user removed product from cart by clicking the Remove/Delete button or updated the quantity to zero next the desired product in the cart view screen.|
|Cleared Cart||Mobile app user removed all products from the shopping cart by clicking the Clear All/Delete All button on the cart view screen.|
|Updated Stage of Cart||Mobile app user proceeded to a different stage in the purchasing process (for example, from Shipping Information screen to Billing Information screen).|
|Purchased Cart||Mobile app user completed the product purchase transaction.|
See Mobile Events for more information about each event types and its attributes.
See the platform specific topics to learn more about implementing retargeting in your app:
A user must be known to be targeted. There is currently no unanimous targeting. Retargeting is only possible for known user where a user ID is provided through
Currently only custom events are supported for retargeting. We are working on enhancing the solution to provide support for pre-defined events.
Currently session life duration cannot be customized. By default this is set to 30 minutes. If marketers has a use case which depends on session life to expire, it will be ran after 30 minutes of the session being closed. For example: If a marketer wants to send a push message to all users who have abandoned a cart (added item to cart, but did not purchase), they can only be targeted 30 minutes after the session closed.