Expiration Period in User Invitations: 7 days

To add more users to your accounts, you must invite them to the platform using their email addresses. The invitation expires in 7 days. In other words, the new user has a maximum of 7 days to accept the invitation and log in to the system.

Dataspace Limits

This section will explain some important import and export parameters and limits.

Concurrent Segment Execution Count: 6

This is the number of segments that can be calculated concurrently and in parallel within an account. In other words, the platform can process the audience calculation for up to 6 segments at the same time. If you try to run another segment while these 6 segments are being calculated, the system will notify you and make you wait until a slot becomes available. We may increase this limit under very rare and temporary circumstances.

Maximum Number of Realtime Segments: 10

For real-time rules (utilized in Realtime in-app and onsite modules for displaying popups or personalizing the site), the platform is required to keep the audience of a segment prepared. This entails swiftly calculating the audience in these segments and maintaining them in a live cache to promptly respond to real-time queries. This denotes the maximum number of segments for which the platform will maintain the audience readily available for interrogation by the real-time rules engines to cater to those rules.

Maximum Number of Realtime Tags: 10

For real-time rules (utilized in Realtime in-app and onsite modules for displaying popups or personalizing the site), the platform is required to keep the audience of a tag prepared. This entails swiftly calculating the audience in these tags and maintaining them in a live cache to promptly respond to real-time queries. This denotes the maximum number of tags for which the platform will maintain the audience readily available for interrogation by the real-time rules engines to cater to those rules.

Maximum file size imported through the Admin Panel: 100MB

For importing data, you can upload files through the Dengage Platform's Admin Panel. The maximum file size is 100 MB, and it is currently not possible to increase this limit.

Maximum Export Limit: 7168 MB

You can place export orders on our platform. The platform will select the data and export it to your desired location. However, the maximum size per export is 7168 MB (~7GB). Exceeding this size will result in an error, and the export will not be completed.

Expire time for downloads: 24 Hours

When you use the Download button to export data from our platform, the system will prepare the data and keep it available for 24 hours. If you don't download the data within this 24-hour period, you will need to initiate the download process again to obtain the data on your computer.

Maximum File Size through Dengage FTP Import: 1 GB

You can import data to your account by uploading files through our FTP site. The maximum file size you can send to our FTP site is 1 GB. To upload data larger than 1 GB, you can compress your files into a ZIP format. Approximately 6-7 GB of raw data can be compressed into a ZIP file of around 1 GB.

Concurrent Data Imports: 3

The platform can process up to 3 data imports simultaneously, depending on the overall system load. For example, if you import 9 files at once, the system will handle a maximum of 3 files at a time.

Maximum Number of Nodes in Automated Flow: 50

The maximum number of nodes that can be used in Automated Flow is limited. If you require more nodes, please contact your account manager to request an increase in this limit.

Maximum Segment Filter Count: 50

You can create a segment with maximum 50 data filters in a segment. If you require more nodes, please contact your account manager to request an increase in this limit.

Maximum Tracked Table Count: 10

The Dengage Platform can monitor the number of rows in up to 10 tables over time. You can request the platform to track the daily row count in these tables to observe increases or decreases. This feature is primarily used for reporting purposes.

Maximum Tracked Segment Count: 10

The Dengage Platform can monitor the size of audience in up to 10 segments over time. You can request the platform to track the daily audience count in these segments to observe increases or decreases. This feature is primarily used for reporting purposes.

 Remote Source Maximum Size: 8192 MB

The Dengage Platform can connect to Remote Data Sources to fetch data for your account. The maximum data size that the platform can fetch is 8192 MB. If the data exceeds this size, the platform will generate an error signal.

Rest API Limits

This section will explain some important REST API parameters and limits.

Maximum Rows/Contacts per Request through REST API: 1000

You can upload your data or contacts to your account through REST API. Import functions (Like Bulk Contact Import or Upsert Data to Regular Tables) supports bulk uploads. You can send up to 1000 rows of data or contacts at one request to our REST API functions.

Maximum Number of Attachments in Transactional Emails

You can include up to 5 attachments in the body of a transactional email. If needed, this limit can be increased by contacting your account manager.

Maximum Size of Each Attachment in Transactional Emails

Each of the 5 attachments can be up to 40 KB in size by default. If needed, these limits can be increased by contacting your account manager.

Content Limits

This section explains the limits on Content that can be uploaded to Dengage Platform.

Maximum File Size for CDN Uploads: 500 KB

The maximum file size (images on emails, push messages etc) that can be uploaded to the CDN is 500 KB. This limit can be increased by contacting your account manager for larger file management needs.

Email Maximum Content Size: 102 KB

The maximum size for your HTML used in building an email content is 102 KB. If you need a larger limit, you can contact your account manager to request an increase.

 SMS Maximum Content Size: 1 KB

The maximum size for your text used in building an sms content is 1 KB. If you need a larger limit, you can contact your account manager to request an increase.

Mobile/Web Push Maximum Character Limit: 500 chars

The maximum number of characters to build your mobile/web push messages text content. You can add image to this content but this parameter limits the number of characters to build text part of your mobile/web push message. If you need a larger limit, you can contact your account manager to request an increase.

 Mobile/Web Push Maximum Content Size: 1 KB

The maximum size for web/mobile push content is 1 KB. This includes the entire content of push message.

In-app Maximum Content Size: 5 KB

The maximum size for in-app content is 5 KB. This includes content created with the Visual Editor or HTML Editor. If your in-app message exceeds this limit, consider reducing its size or simplifying the content or please ask your account manager to increase this limit with Dengage Technical support team.

 Onsite Maximum Content Size: 5 KB

The maximum size for onsite content is 5 KB. This includes content created with the Visual Editor or HTML Editor. If your onsite message exceeds this limit, consider reducing its size or simplifying the content or please ask your account manager to increase this limit with Dengage Technical support team.

Campaign Limits

This section explains the limits while creating Campaign flows.

Maximum Number of Nodes in a Flow: 100

By default, you can add up to 100 nodes in a campaign flow. If the number of nodes in a flow exceeds this limit, consider reducing its size or simplifying the flow or please ask your account manager to increase this limit with Dengage Technical support team.

Recurring Minimum Schedule Period: 15 minutes

Campaign flows on the Dengage platform come in two types: One-time and Recurring. This parameter establishes the minimum recurring schedule period for flows, set at 15 minutes by default. In simpler terms, recurring campaign flows can be scheduled with intervals as short as 15 minutes.

 SDK Limits

This section covers certain parameters related to Mobile and Web SDKs.

Minimum Interval for Fetching In-app Messages: 15 minutes

When setting up an in-app campaign on the platform, the campaign needs to be fetched by the Mobile SDK before it can be displayed to the device user. This time interval refers to the frequency at which the SDK retrieves these messages from our servers. While you can request a reduction in this wait time, it's important to note that doing so may impact the performance of your in-app messaging. This is because the SDK will need to check for updates more frequently. The default interval for this is set to 15 minutes, but it can be reduced to as low as 1 minute. For adjustments to this setting, please reach out to your account manager.

Minimum Interval for Fetching Onsite Messages: 15 minutes

When setting up an onsite campaign on the platform, the campaign needs to be fetched by the Web SDK before it can be displayed to the user. This time interval represents how often the SDK retrieves these messages from our servers. While you can request a reduction in this wait time, it's essential to consider the impact on your website's performance. Increasing the frequency of fetching messages may strain the SDK and potentially affect the overall performance. The default interval for this is set to 15 minutes, but it can be reduced to as low as 1 minute. For any adjustments to this setting, please contact your account manager.