Requirements
- Minimum Android version supported
19+
SDK Installation
Dengage SDK is available on JitPack package repository. If you haven't done so yet, add the JitPack repository in your project's build.gradle
file:
buildscript {
repositories {
...
maven { url 'https://jitpack.io' }
}
}
The Dengage SDK is organized into three modules, allowing you to import only what you need:
- Core SDK: If you don’t plan to use the geofence feature or Huawei messaging service, simply include the
sdk
module. - Geofence: To enable geofence functionality, add the
sdk-geofence
module in addition to thesdk
module. - Huawei Messaging Service: If you want to use Huawei messaging service, include the
sdk-hms
module along with thesdk
module.
Module | Description |
---|---|
sdk | Core module required for analytics, in-app messaging and Firebase messaging service integration. |
sdk-geofence | Enables geofence features. |
sdk-hms | Huawei messaging service integration. |
Lates SDK version: 6.0.76
dependencies {
implementation 'com.github.dengage-tech.dengage-android-sdk:sdk:6.0.76'
}
Endpoint Configuration
For the initial setup, if you have been provided with URL addresses by the Dengage Support Team, you need to configure these URLs in the AndroidManifest.xml
file.
Refer to the API Endpoints By Datacenter section to correctly set your API endpoints.
Here’s an example configuration:
<meta-data
android:name="den_event_api_url"
android:value="https://your_api_endpoint" />
<meta-data
android:name="den_push_api_url"
android:value="https://your_api_endpoint" />
<meta-data
android:name="den_device_id_api_url"
android:value="https://your_api_endpoint" />
<meta-data
android:name="den_in_app_api_url"
android:value="https://your_api_endpoint" />
<meta-data
android:name="den_geofence_api_url"
android:value="https://your_api_endpoint" />
<meta-data
android:name="fetch_real_time_in_app_api_url"
android:value="https://your_api_endpoint" />
Note: Ensure the URLs match the ones provided by the Dengage Support Team and are appropriate for your data center.
Integration
Register Lifecycle Callbacks
To ensure the proper functionality of the Dengage SDK, you need to register activity lifecycle callbacks with DengageLifecycleTracker
. This step is crucial for:
- Fetching specific content from the API, such as the in-app message list.
- Calculating session and visit-related analytics.
You can register the callbacks using the following code in your Application
class:
registerActivityLifecycleCallbacks(DengageLifecycleTracker())
Initialization
init
method should be called once during the application's lifecycle to initialize the Dengage SDK. It is recommended to place it inside the onCreate
method of your Application
class.
Dengage.init(
context = applicationContext,
firebaseIntegrationKey = "your-firebase-integration-key",
deviceConfigurationPreference = DeviceConfigurationPreference.Google,
disableOpenWebUrl = false
)
Parameter Name | Description |
---|---|
context | The application context used for local cache operations. |
firebaseIntegrationKey | The integration key generated by the CDMP Platform while defining the application. It is a hash string containing application details. |
deviceConfigurationPreference | Specifies the configuration preference. For Google Play applications, it should be set to Google . |
disableOpenWebUrl | Set this parameter to true if you want to prevent the browser from opening when a push notification is clicked. |
Logging
You can enable or disable logs comes from Dengage sdk to your Logcat.
Dengage.setLogStatus(enable = true)
User Profiles
setContactKey
The Contact Key serves as a bridge between Devices and Contacts. Devices can be categorized into two types:
- Anonymous Devices
- Contact Devices (which include a Contact Key)
To associate devices with their respective contacts, the Contact Key must be set in the SDK.
Recommended Usage:
You should call this method if you have user information.
It is recommended to call this method during every app launch, as well as on login and logout pages.
Dengage.setContactKey(contactKey = "contact-key")
setDeviceId
You can set a unique device id of for current device. This id will be used to identify the device in the Dengage system.
Dengage.setDeviceId(deviceId = "unique-identifier-of-device")
setCountry
You can set country of current user subscription.
Dengage.setCountry(country = "country-code")
User Events
In order to collect app events and use that data to create behavioral segments in Dengage you have to determine the type of events and data that needs to collect. Once you have determined that, you will need to create a “Big Data” table in Dengage. Collected events will be stored in this table. Multiple tables can be defined depending on your specific need.
Any type of event can be collected. The content and the structure of the events are completely flexible and can be changed according to unique business requirements. You will just need to define a table for events.
Once defined, all you have to do is to send the event data to these tables. Dengage SDK has only 2 functions for sending events: sendDeviceEvent
and sendCustomEvent
. Most of the time you will just need the sendDeviceEvent function.
For eCommerce accounts, there are predefined event tables. And you can feed these tables by using eCommerce event functions.
Login
If the user logs in or you have user information, this means you have contact_key for that user. You can set contact_key in order to match user with the device. There are two functions for getting and setting contact_key.
setContactKey
If user logged in set user id. This is important for identifying your users. You can put this function call in every page. It will not send unnecessary events.
Dengage.setContactKey(contactKey = "contact-key")
getSubscription
If you need to get current user information from SDK use this function. contactKey
is a property of Subscription
object.
Dengage.getSubscription()
eCommerce Events
If your Dengage account is an eCommerce account, you should use standard eCommerce events in the SDK. If you need some custom events or your account is not a standard eCommerce account, you should use custom event functions.
Dengage SDK includes standard eCommerce events:
- Page View Events:
- Home page view
- Product page view
- Category page view
- Promotion page view
- ...
- Shopping Cart Events:
- Add to cart
- Remove from cart
- View cart
- Begin checkout
- Order Events:
- Order
- Cancel order
- Wishlist Events:
- Add to wishlist
- Remove from wishlist
- Search Event
Each event corresponds to related tables in your account.
Page View Events
Page view events are sent to the page_view_events
table. If you've added new columns to this table, include them in the event data.
// Home page view
val data = hashMapOf<String, Any>(
"page_type" to "home"
// ... additional columns in page_view_events table can be added here
)
Dengage.pageView(data)
// Product page view
val data = hashMapOf<String, Any>(
"page_type" to "product",
"product_id" to 123
// ... additional columns in page_view_events table can be added here
)
Dengage.pageView(data)
//Category page view
val data = hashMapOf<String, Any>(
"page_type" to "category",
"category_id" to 123
// ... additional columns in page_view_events table can be added here
)
Dengage.pageView(data)
// Promotion page view
val data = hashMapOf<String, Any>(
"page_type" to "promotion",
"promotion_id" to 123
// ... additional columns in page_view_events table can be added here
)
Dengage.pageView(data)
// Custom page view
val data = hashMapOf<String, Any>(
"page_type" to "custom"
// ... additional columns in page_view_events table can be added here
)
Dengage.pageView(data)
For other pages you can send anything as page_type
Shopping Cart Events
These events are stored in shopping_cart_events
and shopping_cart_events_detail
tables. The following functions are available for shopping cart events:
addToCart
removeFromCart
viewCart
beginCheckout
// Add To Cart
val data = hashMapOf<String, Any>(
"product_id" to "123",
"product_variant_id" to "1222",
"quantity" to 1,
"unit_price" to 9.99,
"shipping" to 5,
"discounted_price" to 9.99,
"coupon_code" to ""
// ... extra columns in shopping_cart_events table, can be added here
)
Dengage.addToCart(data)
// Remove From Cart
val data = hashMapOf<String, Any>(
"product_id" to "123",
"product_variant_id" to "1222",
"quantity" to 1,
"unit_price" to 9.99,
"shipping" to 5,
"discounted_price" to 9.99,
"coupon_code" to ""
// ... extra columns in shopping_cart_events table, can be added here
)
Dengage.removeFromCart(data)
// View Cart
val data = hashMapOf<String, Any>(
// ... extra columns in shopping_cart_events table, can be added here
)
Dengage.viewCart(data);
// Begin Checkout
val data = hashMapOf<String, Any>(
// ... extra columns in shopping_cart_events table, can be added here
)
Dengage.beginCheckout(data);
Order Events
Order events are stored in order_events
and order_events_detail
tables.
// Paid Order
val data = hashMapOf<String, Any>(
"order_id" to "123",
"item_count" to 1,
"total_amount" to 99.9,
"payment_method" to "card",
"shipping" to 5,
"discounted_price" to 29.99, // use total price if there is no discount
"coupon_code" to "" // use if necessary
// ... extra columns in order_events table, can be added here
)
Dengage.order(data)
// Cancel Order
val data = hashMapOf<String, Any>(
"item_count" to 1,
"total_amount" to 99.9,
"discounted_price" to 29.99 // use total price if there is no discount
// ... extra columns in order_events table, can be added here
)
Dengage.cancelOrder(data)
Search Event
Search events are stored in the search_events
table.
val data = hashMapOf<String, Any>(
"keywords" to "hello",
"result_count" to 123,
"filters" to "q=keywords" // you can send extra filters selected by the user here
// ... extra columns in search_events table, can be added here
)
Dengage.search(data)
Wishlist Events
These events are stored in wishlist_events
and wishlist_events_detail
tables. The available functions are:
addToWishlist
removeFromWishlist
You can send all items in the wishlist for every event, simplifying the tracking of the current wishlist items.
// Add To Wishlist
val data = hashMapOf<String, Any>(
"product_id" to 123
// ... extra columns in wishlist_events table, can be added here
)
Dengage.addToWishList(data)
// Remove From Wishlist
val data = hashMapOf<String, Any>(
"product_id" to 123
// ... extra columns in wishlist_events table, can be added here
)
Dengage.removeFromWishList(data)
Custom Events
Use the sendDeviceEvent
function to send events specific to a device. Events are sent to a big data table defined in your D·engage account, which must have a relation to the master_device
table. If you set a contact_key
for that device, collected events will be associated with the user.
// For example, if you have a table named "events"
// and the events table has "key", "event_date", "event_name", "product_id" columns
// You only need to send the columns except "key" and "event_date", as those are sent by the SDK
val data = hashMapOf<String, Any>(
"event_name" to "page_view",
"product_id" to "12345"
// ... extra columns in events table, can be added here
)
Dengage.sendDeviceEvent("events", data)
Push Notifications
FCM setup
-
Complete the FCM Android Setup to configure your Android application for Firebase integration.
-
Download the
google-services.json
configuration file and place it in your app's directory. -
To ensure the values in your
google-services.json
configuration file are accessible to Firebase SDKs, you need to include the Google Services Gradle Plugin (google-services
) in your project.- In your root-level (project-level) Gradle file
<project>/build.gradle
, add the following dependency::
dependencies { classpath("com.google.gms:google-services:4.4.2") }
- In your module (app-level) Gradle file
<project>/app/build.gradle
, apply the Google Services plugin as follows:
plugins { id("com.google.gms.google-services") }
- In your root-level (project-level) Gradle file
-
To handle push messages, you need to include the FcmMessagingService in your
AndroidManifest.xml
file. Place the following block inside the<application>
tag of yourAndroidManifest.xml
file to ensure proper integration:<!-- Add the FCM Messaging Service to handle push notifications from Firebase --> <service android:name="com.dengage.sdk.push.FcmMessagingService" android:exported="false" > <intent-filter> <action android:name="com.google.firebase.MESSAGING_EVENT" /> </intent-filter> </service>
Subscription
Subscription
is self-managed by SDK.
Definition: Subscription is a process which is triggered by sending subscription event to Dengage. It contains necessary information about application to send push notifications to clients.
The SDK automatically sends subscription events in the following scenarios:
- Initialization
- Setting Contact Key
- Setting Token
- Setting User Permission (if permissions are manually managed)
User Permission Management (optional)
If you manage your own user permission states on your application you may send user permission by using setUserPermission
method.
// Use to set permission of current subscription
Dengage.setUserPermission(permission = true)
// Use to get permission of current subscription
Dengage.getUserPermission() // Boolean?
Notification Channels
Starting with Android O, every notification must be assigned a valid notification channel; otherwise, it will not be displayed.
The SDK automatically assigns a default channel named "General". This default channel can be customized using the setNotificationChannelName
method provided by the SDK.
To override the default channel, call the setNotificationChannelName
method with your desired channel name.
Dengage.setNotificationChannelName("your-custom-channel-name")
getToken
Retrieve the token for the current user's subscription using this method.
val token = Dengage.getToken()
Action Buttons
Dengage Android SDK allows you to add clickable buttons under notifications.
If you need to handle action buttons manually, you must define a custom receiver in your AndroidManifest.xml
that extends com.dengage.sdk.NotificationReceiver
. Otherwise, the SDK will handle button clicks automatically.
<receiver android:name=".MyReceiver"
android:exported="false"> <!-- Replace NotificationReceiver with .MyReceiver -->
<intent-filter>
...
<action android:name="com.dengage.push.intent.ACTION_CLICK" /> <!-- Add this line -->
</intent-filter>
</receiver>
To handle intents fired by the SDK, use the following function in your launcher activity:
PushDataParser.parseIntent(intent, pushMessageCallback = object : PushMessageCallback {
override fun dataFetched(message: Message) {
// Handle fetched data
}
override fun onActionClick(intent: Intent, message: Message, clickedId: String) {
// Handle action button click
}
})
Carousel Push
Carousel Push functionality allows you to show your notification with a slideshow.
Defining Custom Receiver
Before you start, you need to define your receiver in your AndroidManifest.xml
file.
<!-- For handling push notifications comes to messaging service classes -->
<receiver
android:name=".push.PushNotificationReceiver"
android:exported="false" >
<intent-filter>
<action android:name="com.dengage.push.intent.RECEIVE" />
<action android:name="com.dengage.push.intent.OPEN" />
<action android:name="com.dengage.push.intent.DELETE" />
<action android:name="com.dengage.push.intent.ACTION_CLICK" />
<action android:name="com.dengage.push.intent.ITEM_CLICK" />
<action android:name="com.dengage.push.intent.CAROUSEL_ITEM_CLICK" />
</intent-filter>
</receiver>
Preparing Custom Layouts
The SDK utilizes custom layouts for carousel functionality. You need to set up these layouts in your res
folder. Pre-built layouts are available for both landscape and portrait orientations.
- Landscape Layout: Add
_den_carousel_landscape.xml
to yourlayouts
directory. - Portrait Layout: Add
den_carousel_portrait.xml
to yourlayouts
directory.
Note: Ensure you replace placeholder drawable items with your own resources.
den_carousel_landscape.xml
:
<?xml version="1.0" encoding="utf-8"?>
<RelativeLayout xmlns:android="http://schemas.android.com/apk/res/android"
android:layout_width="match_parent"
android:layout_height="wrap_content">
<include
android:id="@+id/den_carousel_collapsed"
layout="@layout/den_carousel_collapsed"
android:layout_width="match_parent"
android:layout_height="wrap_content" />
<FrameLayout
android:id="@+id/den_carousel_frame"
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:layout_below="@id/den_carousel_collapsed"
android:layout_gravity="center"
android:paddingLeft="16dp"
android:paddingRight="16dp">
<ImageView
android:id="@+id/den_carousel_landscape_image"
android:layout_width="match_parent"
android:layout_height="160dp"
android:layout_gravity="center"
android:scaleType="centerCrop" />
<ImageView
android:id="@+id/den_carousel_left_image"
android:layout_width="44dp"
android:layout_height="44dp"
android:layout_gravity="start|center_vertical"
android:layout_marginStart="5dp"
android:layout_marginLeft="5dp"
android:scaleType="fitXY"
android:src="@drawable/ic_arrow_left" />
<ImageView
android:id="@+id/den_carousel_right_image"
android:layout_width="44dp"
android:layout_height="44dp"
android:layout_gravity="end|center_vertical"
android:layout_marginEnd="5dp"
android:scaleType="fitXY"
android:src="@drawable/ic_arrow_right" />
</FrameLayout>
<LinearLayout
android:id="@+id/den_carousel_item_title_container"
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:layout_below="@id/den_carousel_frame"
android:layout_marginTop="5dp"
android:orientation="vertical">
<TextView
android:id="@+id/den_carousel_item_title"
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:gravity="center"
android:text="Item Title" />
</LinearLayout>
<LinearLayout
android:id="@+id/den_carousel_item_description_container"
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:layout_below="@id/den_carousel_item_title_container"
android:layout_marginTop="5dp"
android:layout_marginBottom="5dp"
android:orientation="vertical">
<TextView
android:id="@+id/den_carousel_item_description"
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:gravity="center"
android:text="Item Description" />
</LinearLayout>
</RelativeLayout>
den_carousel_portrait.xml
:
<?xml version="1.0" encoding="utf-8"?>
<RelativeLayout xmlns:android="http://schemas.android.com/apk/res/android"
android:layout_width="match_parent"
android:layout_height="wrap_content">
<include
android:id="@+id/den_carousel_collapsed"
layout="@layout/den_carousel_collapsed"
android:layout_width="match_parent"
android:layout_height="wrap_content" />
<FrameLayout
android:id="@+id/den_carousel_body_portrait"
android:layout_width="596dp"
android:layout_height="wrap_content"
android:layout_below="@id/den_carousel_collapsed"
android:layout_gravity="center"
android:layout_marginBottom="8dp"
android:paddingLeft="16dp"
android:paddingRight="16dp">
<RelativeLayout
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:layout_gravity="center">
<RelativeLayout
android:id="@+id/den_carousel_left_container"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_toStartOf="@+id/den_carousel_portrait_current_container"
android:layout_toLeftOf="@+id/den_carousel_portrait_current_container">
<ImageView
android:id="@+id/den_carousel_portrait_left_image"
android:layout_width="192dp"
android:layout_height="130dp"
android:layout_centerInParent="true"
android:scaleType="centerCrop" />
<RelativeLayout
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_alignStart="@+id/den_carousel_portrait_left_image"
android:layout_alignLeft="@+id/den_carousel_portrait_left_image"
android:layout_alignTop="@+id/den_carousel_portrait_left_image"
android:layout_alignEnd="@+id/den_carousel_portrait_left_image"
android:layout_alignRight="@+id/den_carousel_portrait_left_image"
android:layout_alignBottom="@+id/den_carousel_portrait_left_image"
android:background="#BFffffff" />
</RelativeLayout>
<RelativeLayout
android:id="@+id/den_carousel_right_container"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_toEndOf="@+id/den_carousel_portrait_current_container"
android:layout_toRightOf="@+id/den_carousel_portrait_current_container">
<ImageView
android:id="@+id/den_carousel_portrait_right_image"
android:layout_width="192dp"
android:layout_height="130dp"
android:layout_centerInParent="true"
android:scaleType="centerCrop" />
<RelativeLayout
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_alignStart="@+id/den_carousel_portrait_right_image"
android:layout_alignLeft="@+id/den_carousel_portrait_right_image"
android:layout_alignTop="@+id/den_carousel_portrait_right_image"
android:layout_alignEnd="@+id/den_carousel_portrait_right_image"
android:layout_alignRight="@+id/den_carousel_portrait_right_image"
android:layout_alignBottom="@+id/den_carousel_portrait_right_image"
android:background="#B0ffffff" />
</RelativeLayout>
<RelativeLayout
android:id="@+id/den_carousel_portrait_current_container"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_centerInParent="true">
<ImageView
android:id="@+id/den_carousel_portrait_current_image"
android:layout_width="212dp"
android:layout_height="130dp"
android:cropToPadding="true"
android:paddingLeft="10dp"
android:paddingRight="10dp"
android:scaleType="centerCrop" />
</RelativeLayout>
</RelativeLayout>
<FrameLayout
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:layout_gravity="center"
android:layout_marginLeft="5dp"
android:layout_marginRight="5dp">
<ImageView
android:id="@+id/den_carousel_left_arrow"
android:layout_width="44dp"
android:layout_height="44dp"
android:layout_gravity="start|center_vertical"
android:scaleType="fitXY"
android:src="@drawable/ic_arrow_left" />
<ImageView
android:id="@+id/den_carousel_right_arrow"
android:layout_width="44dp"
android:layout_height="44dp"
android:layout_gravity="end|center_vertical"
android:scaleType="fitXY"
android:src="@drawable/ic_arrow_right" />
</FrameLayout>
</FrameLayout>
<LinearLayout
android:id="@+id/den_carousel_item_title_container"
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:layout_below="@id/den_carousel_body_portrait"
android:orientation="vertical">
<TextView
android:id="@+id/den_carousel_item_title"
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:gravity="center"
android:text="Item Title"
android:textColor="@color/purple_200" />
</LinearLayout>
<LinearLayout
android:id="@+id/den_carousel_item_description_container"
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:layout_below="@id/den_carousel_item_title_container"
android:layout_marginBottom="8dp"
android:orientation="vertical">
<TextView
android:id="@+id/den_carousel_item_description"
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:gravity="center"
android:text="Item Description"
android:textColor="@color/purple_200" />
</LinearLayout>
</RelativeLayout>
den_carousel_collapsed.xml
:
<?xml version="1.0" encoding="utf-8"?>
<RelativeLayout xmlns:android="http://schemas.android.com/apk/res/android"
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:paddingLeft="16dp"
android:paddingTop="16dp"
android:paddingRight="16dp">
<ImageView
android:id="@+id/den_carousel_image"
android:layout_width="36dp"
android:layout_height="36dp"
android:layout_alignParentEnd="true"
android:layout_alignParentRight="true"
android:layout_gravity="top|end"
android:layout_marginStart="12dp"
android:layout_marginLeft="12dp"
android:scaleType="centerCrop"
android:src="@drawable/ic_launcher_foreground" /> <!-- Your App Icon -->
<TextView
android:id="@+id/den_carousel_title"
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:layout_toStartOf="@+id/den_carousel_image"
android:layout_toLeftOf="@id/den_carousel_image"
android:text="Remote Title"
android:textColor="@color/purple_200"
android:textSize="15dp"
android:textStyle="bold" />
<TextView
android:id="@+id/den_carousel_message"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_below="@id/den_carousel_title"
android:layout_alignStart="@+id/den_carousel_title"
android:layout_alignLeft="@+id/den_carousel_title"
android:layout_alignEnd="@+id/den_carousel_title"
android:layout_alignRight="@+id/den_carousel_title"
android:layout_marginBottom="16dp"
android:layout_toLeftOf="@id/den_carousel_image"
android:ellipsize="end"
android:lineSpacingMultiplier="1.2"
android:maxLines="1"
android:text="Remote message"
android:textColor="@color/purple_200"
android:textSize="14dp" />
</RelativeLayout>
Building Carousel Notification
To use a custom layout for the notification requires building a message by the developer with the layout.
First, please create your receiver class extends from NotificationReceiver
and override the method onCarouselRender
. This method will be called when a carousel push notification is received.
class PushNotificationReceiver : NotificationReceiver() {
override fun onCarouselRender(
context: Context,
intent: Intent,
message: Message,
leftCarouselItem: CarouselItem,
currentCarouselItem: CarouselItem,
rightCarouselItem: CarouselItem
) {
super.onCarouselRender(
context,
intent,
message,
leftCarouselItem,
currentCarouselItem,
rightCarouselItem
)
val itemTitle = currentCarouselItem.title
val itemDesc = currentCarouselItem.description
// set intents (right button, left button, item click)
val itemIntent = getItemClickIntent(intent.extras, context.packageName)
val leftIntent = getLeftItemIntent(intent.extras, context.packageName)
val rightIntent = getRightItemIntent(intent.extras, context.packageName)
val deleteIntent = getDeleteIntent(intent.extras, context.packageName)
val contentIntent = getContentIntent(intent.extras, context.packageName)
val carouseItemIntent = getPendingIntent(context, 0, itemIntent)
val carouselLeftIntent = getCarouselDirectionIntent(context, 1, leftIntent)
val carouselRightIntent = getCarouselDirectionIntent(context, 2, rightIntent)
val deletePendingIntent = getDeletePendingIntent(context, 4, deleteIntent)
val contentPendingIntent = getPendingIntent(context, 5, contentIntent)
// set views for the layout
val collapsedView = RemoteViews(
context.packageName,
R.layout.den_carousel_collapsed
)
collapsedView.setTextViewText(R.id.den_carousel_title, message.title)
collapsedView.setTextViewText(R.id.den_carousel_message, message.message)
val carouselView = RemoteViews(
context.packageName,
R.layout.den_carousel_portrait
)
carouselView.setTextViewText(R.id.den_carousel_title, message.title)
carouselView.setTextViewText(R.id.den_carousel_message, message.message)
carouselView.setTextViewText(R.id.den_carousel_item_title, itemTitle)
carouselView.setTextViewText(R.id.den_carousel_item_description, itemDesc)
carouselView.setOnClickPendingIntent(R.id.den_carousel_left_arrow, carouselLeftIntent)
carouselView.setOnClickPendingIntent(
R.id.den_carousel_portrait_current_image,
carouseItemIntent
)
carouselView.setOnClickPendingIntent(R.id.den_carousel_item_title, carouseItemIntent)
carouselView.setOnClickPendingIntent(R.id.den_carousel_item_description, carouseItemIntent)
carouselView.setOnClickPendingIntent(R.id.den_carousel_right_arrow, carouselRightIntent)
val channelId = createNotificationChannel(context, message)
loadCarouselImageToView(
carouselView = carouselView,
imageViewId = R.id.den_carousel_portrait_left_image,
carouselItem = leftCarouselItem,
onComplete = {
// you can call notificationManager.notify for devices that could not show carousel image contents
}
)
loadCarouselImageToView(
carouselView = carouselView,
imageViewId = R.id.den_carousel_portrait_current_image,
carouselItem = currentCarouselItem,
onComplete = {
// you can call notificationManager.notify for devices that could not show carousel image contents
}
)
loadCarouselImageToView(
carouselView = carouselView,
imageViewId = R.id.den_carousel_portrait_right_image,
carouselItem = rightCarouselItem,
onComplete = {
// you can call notificationManager.notify for devices that could not show carousel image contents
}
)
val notification = NotificationCompat.Builder(context, channelId)
.setSmallIcon(R.mipmap.ic_launcher)
.setCustomContentView(collapsedView)
.setCustomBigContentView(carouselView)
.setContentIntent(contentPendingIntent)
.setDeleteIntent(deletePendingIntent)
.setSound(message.sound.getSoundUri(context))
.build()
// show message again silently with next, previous and current item.
notification.flags = Notification.FLAG_AUTO_CANCEL or Notification.FLAG_ONLY_ALERT_ONCE
// show message
val notificationManager = NotificationManagerCompat.from(context)
intent.extras?.getInt("requestCode")?.let { notificationManager.notify(it, notification) }
}
}
App Inbox
App Inbox is a screen within a mobile app that stores persistent messages. It's kind of like an email inbox, but it lives inside the app itself. App Inbox differs from other mobile channels such as push notifications or in-app messages. For both push and in-app messages, they're gone once you open them.
In other words, Dengage admin panel lets you keep selected messages on the platform and Mobile SDK may receive and display these messages when needed.
In order to save messages into App Inbox, you need to select the "Save to Inbox" option when sending messages in D·engage the admin panel by assigning an expiration date to it.
After selecting your Push content, you must activate the "Save To Inbox" option.
To use the app inbox feature, please send an email to [email protected].
Inbox messages are kept in the memory storage of the phone until the app is completely closed or for a while and Dengage SDK provides functions for getting and managing these messages.
Methods
When a push message is received with the addToInbox
parameter, the message is saved during the notification building stage, allowing users to access these messages later. The following methods facilitate interaction with these messages:
Getting Inbox Messages
Retrieve stored inbox messages with pagination:
Dengage.getInboxMessages(
limit = 20, // Number of messages to retrieve
offset = 0, // Starting point for retrieval
dengageCallback = object : DengageCallback<MutableList<InboxMessage>> { // Callback for handling retrieved messages
override fun onResult(result: MutableList<InboxMessage>) {
// Handle the result
Toast.makeText(context, "Inbox Messages: ${result.size}", Toast.LENGTH_SHORT)
.show()
}
override fun onError(error: DengageError) {
// Handle the error
Toast.makeText(context, "Error: ${error.errorMessage}", Toast.LENGTH_SHORT)
.show()
}
})
Removing an Inbox Message
Delete a specific inbox message:
Dengage.deleteInboxMessage(
messageId = "message-id" // ID of the message to delete
)
Marking an Inbox Message as Clicked:
Mark a message as clicked to update its status:
Dengage.setInboxMessageAsClicked(
messageId = "message-id" // ID of the message to mark as clicked
)
receiveDate
property is used to store inbox message receive date. It keeps date as a UTC time format ("yyyy-MM-ddTHH:mm:ss.fffZ"). The applications which are using our SDKs need to convert this UTC date to the client time zone if the applications want to display the message receive date to their users.
In-App Messaging
An in-app message is a type of mobile message where the notification is displayed within the app. It is not sent at a specific time but it is shown to users when the user is using the app.
Examples include popups, yes/no prompts, banners, and more.
In order to show in-app messages, there is no permit requirement.
Methods
Created messages will be stored in Dengage backend and will be served to mobile SDKs.
If you integrated mobile SDK correctly for push messages, for using in-app features you just have to add setNavigation
function to every page navigation.
If you want to use a screen name filter, you should send the screen name to setNavigation
function in every page navigation.
You should pass the current activity to setNavigation function.
// Without screen filter
Dengage.setNavigation(
activity = activity as AppCompatActivity // For showing ui of in app message
)
// With screen filter
Dengage.setNavigation(
activity = activity as AppCompatActivity, // For showing ui of in app message
screenName = "screen-name" // For filtering in app messages with respect to current screen in your app
)
Real Time In-App Messaging
You can use the real time in-app functionality by using the function.
val customParams = hashMapOf<String, String>()
Dengage.showRealTimeInApp(
activity = activity as AppCompatActivity, // For showing ui of in app message
screenName = "screen-name", // For filtering in app messages with respect to current screen in your app(optional)
params = customParams // For filtering in app messages with respect to custom parameters(optional)
)
// Set category path for using in real time in app comparisons
Dengage.setCategoryPath(path = "category-path")
// Set cart item count for using in real time in app comparisons
Dengage.setCartItemCount(count = "cart-item-count")
// Set cart amount for using in real time in app comparisons
Dengage.setCartAmount(amount = "cart-amount")
// Set state for using in real time in app comparisons
Dengage.setState(name = "state-name")
// Set city for using in real time in app comparisons
Dengage.setCity(name = "city-name")
In-App Inline
The In-App Inline feature allows you to seamlessly integrate inline in-app messages into your app's content, dynamically populating specific parts of your app for a better user experience.
Define the layout in your XML file to include the InAppInlineElement
view, which will display the inline content.
InAppInlineElement
: The placeholder view where the inline content will be displayed.
<?xml version="1.0" encoding="utf-8"?>
<layout xmlns:android="http://schemas.android.com/apk/res/android">
<LinearLayout
android:layout_width="match_parent"
android:layout_height="match_parent"
android:layout_margin="20dp"
android:orientation="vertical">
<com.dengage.sdk.ui.inappmessage.InAppInlineElement
android:id="@+id/inapp_inline_element"
android:layout_width="match_parent"
android:layout_height="200dp"
android:layout_marginTop="12dp" />
</LinearLayout>
</layout>
In your fragment or activity, set up the inline in-app messaging using the Dengage.showInlineInApp
method.
class InAppInLineFragment : BaseDataBindingFragment<FragmentInappInlineBinding>() {
override fun getLayoutRes(): Int {
return R.layout.fragment_inapp_inline
}
override fun init() {
val customParams = hashMapOf<String, String>()
Dengage.showInlineInApp(screenName = "screen-name",
inAppInlineElement = binding.inappInlineElement,
propertyId = "property-id",
activity = requireActivity(),
customParams = customParams,
hideIfNotFound = true
)
}
}
Parameters:
inAppInlineElement
TheInAppInlineElement
view defined in the XML layout where the inline content will appear.propertyId
The Android selector linked to the in-app inline campaign created in the Dengage panel.customParams
(optional) AHashMap
of custom parameters used for filtering inline messages.screenName
(optional) Specifies the screen where the inline in-app message will be displayed.hideIfNotFound
(optional, default:false
) If set totrue
, theInAppInlineElement
will be hidden if no inline message is found.
App Stories
The App Stories feature allows you to display story-like content within your app.
Define the layout in your XML file to include the StoriesListView
view, which will display the story content.
StoriesListView
: The placeholder view where the app stories will be displayed.
<?xml version="1.0" encoding="utf-8"?>
<layout xmlns:android="http://schemas.android.com/apk/res/android">
<LinearLayout
android:layout_width="match_parent"
android:layout_height="match_parent"
android:layout_margin="20dp"
android:orientation="vertical">
<com.dengage.sdk.ui.story.StoriesListView
android:id="@+id/stories_list_view"
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:layout_marginTop="12dp" />
</LinearLayout>
</layout>
In your fragment or activity, set up the app stories using the Dengage.showStoriesList
method.
class AppStoryFragment : BaseDataBindingFragment<FragmentAppStoryBinding>() {
override fun getLayoutRes(): Int {
return R.layout.fragment_app_story
}
override fun init() {
val customParams = hashMapOf<String, String>()
Dengage.showStoriesList(screenName = "screen-name",
storiesListView = binding.storiesListView,
storyPropertyId = "property-id",
activity = requireActivity(),
customParams = customParams
)
}
}
Parameters:
screenName
(optional) Specifies the screen where the app stories should be displayed.storiesListView
TheStoriesListView
defined in the XML layout where the stories will appear.storyPropertyId
The story property ID associated with the app stories campaign created in the Dengage panel.customParams
(optional) AHashMap
of custom parameters used for filtering stories.
Geofence
The Dengage Android Geofence SDK enhances the Dengage Android SDK by integrating geofence capabilities through the Play Services Location library.
Geofence Installation
The Dengage Android Geofence SDK is available via JitPack. To install the SDK, include the following dependencies in your build.gradle
file. Ensure the sdk-geofence
version matches the core SDK version.
dependencies {
implementation 'com.github.dengage-tech.dengage-android-sdk:sdk:6.0.76'
implementation 'com.github.dengage-tech.dengage-android-sdk:sdk-geofence:6.0.76'
}
Geofence Initialization
After initializing the core SDK with Dengage.init
, you can enable geofence by calling the DengageGeofence.startGeofence
method in your application class.
DengageGeofence.startGeofence()
Request Location Permission
To request location permissions at runtime, use the DengageGeofence.requestLocationPermissions
method.
DengageGeofence.requestLocationPermissions(activity)
Huawei Messaging Service
HMS setup
-
Complete the HMS Android Setup to configure your Android application for Huawei integration.
-
Download the
agconnect-services.json
configuration file and place it in your app's directory. -
In your root-level (project-level) Gradle file
<project>/build.gradle
, add the following dependency::buildscript { repositories { maven {url 'http://developer.huawei.com/repo/'} } dependencies { classpath "com.huawei.agconnect:agcp:1.6.2.300" } }
-
In your module (app-level) Gradle file
<project>/app/build.gradle
, apply the Huawei Agconnect plugin as follows:plugins { id("com.huawei.agconnect") }
-
The Dengage Android HMS SDK is available via JitPack. To install the SDK, include the following dependencies in your
build.gradle
file. Ensure thesdk-hms
version matches the core SDK version.
dependencies {
implementation 'com.github.dengage-tech.dengage-android-sdk:sdk:6.0.76'
implementation 'com.github.dengage-tech.dengage-android-sdk:sdk-hms:6.0.76'
}
-
To handle push messages, you need to include the HmsMessagingService in your
AndroidManifest.xml
file. Place the following block inside the<application>
tag of yourAndroidManifest.xml
file to ensure proper integration:<!-- Add the Hms Messaging Service to handle push notifications from HMS --> <service android:name="com.dengage.hms.HmsMessagingService" android:exported="false" > <intent-filter> <action android:name="com.huawei.push.action.MESSAGING_EVENT" /> </intent-filter> </service>
Initialization for Huawei
init
method should be called once during the application's lifecycle to initialize the Dengage SDK. It is recommended to place it inside the onCreate
method of your Application
class.
val dengageHmsManager = DengageHmsManager()
Dengage.init(
context = applicationContext,
huaweiIntegrationKey = "your-huawei-integration-key",
dengageHmsManager = dengageHmsManager,
deviceConfigurationPreference = DeviceConfigurationPreference.Huawei,
disableOpenWebUrl = false
)
Just as like in Carousel Push section, you need to define a custom receiver in your AndroidManifest.xml
file and to prepare custom layouts for carousel functionality.