12

Packages and Configuration Options

The SDK consists of a few packages. You’ll get the most value out of Customer.io when you use all our packages together, but this lets you omit packages for features you don’t intend to use.

SDK packages

To minimize our SDK’s impact on your app’s size, we’ve split the SDK into packages. You can limit your install to the packages that you need for your project. But, in most cases, you’ll want to install all the packages to get the most value out of Customer.io.

You must install the datapipelines package. It lets you identify people, which you must do before you can send them messages, etc. You’ll want to add the messaging-push-fcm and the messaging-in-app packages to send push notifications and in-app messages respectively.

Configuration options

You’ll call configuration options before you initialize the SDK. In most cases, you’ll want to stick with the defaults, but you might do things like change the logLevel when testing updates to your app—as shown in the example below.

If you’re in our EU region, you must set Region.EU.

CustomerIOBuilder(
    applicationContext = this,
    cdpApiKey = "your_cdp_api_key"
).apply {
    // If you're in the EU, set Region.EU
    Region.US
    autoTrackDeviceAttributes(true)
    autoTrackActivityScreens(false)
    logLevel(CiologLevel.DEBUG)
    addCustomerIOModule(
        ModuleMessagingInApp(
            config = MessagingInAppModuleConfig.Builder(
                siteId = "your_site_id",
                region = Region.US
            ).setEventListener(InAppMessageEventListener()).build()
        )
    )
    addCustomerIOModule(ModuleMessagingPushFCM())
    build()
}