User Guide

Dengage Onboarding

Suggest Edits

Welcome to Dengage CXDP! This guide will walk you through the onboarding process, which consists of two main topics: Data Integration and Channel Integration.

Data Integration

Dengage CXDP enables you to store and manage both online and offline data. You can customize your database by adding new columns to existing tables or creating new tables. This way, you can build your own relational table structure in your CXDP account.

Before starting data integration, it's crucial to understand the table structures and data requirements within Dengage CXDP. Follow these steps:

  • Review the Intro to Data Space to understand different table types and data formats.
  • Explore Data Management to learn how to handle and organize your data effectively.
  • Check the Platform Limits section for any data-related restrictions you should be aware of.

Dengage CXDP allows you to store various types of data, including contact and device information, online events, and any other data you wish to use in your segments or campaigns.

1. Contact Data

Contact data is an essential part of your data integration. The master_contact table stores all contact-related data. You can:

Methods for Inserting/Updating Contact Data

  • API: In order to insert/update contact data, you can use the BulkUpsert method. To begin API integration, follow these steps:
  • FTP: In order to import data to your account via FTP, follow these steps:
  • Remote Source: Allows you to establish a direct connection between your database and Dengage CXDP. You can check the list of supported remote sources here.

Note: Please be informed that, based on your data size, initial bulk data import may not be done via API. So manual import, FTP or Remote Source would always remain as alternatives for your initial bulk contact import.

2. Device Data

Device data is collected via Web SDK and Mobile SDKs. The master_device table stores details such as:

  • Device ID
  • Token
  • Browser
  • SDK version
  • Operating system
  • etc.

3. Regular Tables

Regular tables can be created for specific use cases, allowing you to store additional data for table relations, segmentation, and content personalization.

You can insert/update data using API, FTP, or Remote Source methods.

Methods for Inserting/Updating Regular Tables

If you are using Dengage Standard Ecommerce Tables, review the table columns and data types here. For integrating Ecommerce Tables using the API method, refer to the links below for detailed guidance.

Note: If using Automated Flow for data import/export, refer to this page for all nodes and explanations.

4. Online Event Collection

Online events capture visitor actions on websites and mobile apps. These are collected through event JS code or Event API implementation.

Steps to Implement Event Collection

Dengage provides predefined Ecommerce Event tables within your account. These tables allow you to track key ecommerce activities effortlessly. To start using them, simply integrate the predefined codes for:

If your business requires event tracking beyond the predefined options, you can create your own custom events in Dengage. Follow these steps:

  • Create a Big Data Table – This table will store your custom event data. Follow the steps provided here to create one.
  • Implement custom events– Once your table is ready, configure your custom events.

Channel Integration

Dengage CXDP supports multiple communication channels. Each channel requires specific configurations before they can be used.

Email Channel

  • DNS configuration must be done for both the sender domain and the link domain (which should be different from each other).
  • For transactional emails, a separate sender domain must be created.
  • Once account configurations are completed, the warm-up process follows. You must share your active and blacklisted audience for this step.

SMS Channel

  • If Dengage has an existing integration with your vendor, only account details will be required.
  • If Dengage is not yet integrated with your vendor, you can share the vendor’s integration documentation with our team for review. Please note that the required details may vary for each vendor.

WhatsApp Channel

  • Configuration requires the WhatsApp number and Facebook Business Manager account.
  • After your WhatsApp account is created, you can follow the configuration steps provided here.

Web Push Channel

  • Configuration requirements are available here.
  • Please ensure you remove any former provider’s service worker file before implementing Dengage’s service worker.

On-Site Channel

  • Configuration requirements can be found here.

Mobile Push Channel

  • To enable mobile push notifications, you need to implement the relevant SDK based on your mobile app infrastructure. Dengage provides SDKs for various platforms, including the iOS SDK (Swift), Android SDK (Kotlin), React Native, Cordova, and Flutter. Refer to the appropriate SDK documentation to complete the integration:

In-App Channel

  • To use the in-app message channel, you need to integrate the correct SDK based on your mobile app. Dengage supports SDKs for iOS (Swift), Android (Kotlin), React Native, Cordova, and Flutter. Refer to the correct SDK for integration:

App Inbox Channel

  • To enable the App Inbox channel, SDK integration is required. Dengage provides SDKs for iOS (Swift), Android (Kotlin), React Native, Cordova, and Flutter. Refer to the appropriate SDK to complete the configuration:

Social Media Channels

  • You can connect your Google, META and Tiktok ads accounts via the steps provided here.

Updated about 4 hours ago