DinMo Documentation
  • 📙Core Concepts
  • Guides
    • ⚡Get started with DinMo
      • Initial Configuration of DinMo
        • Connect a Source
        • Create your Models
        • Create a Destination
      • Create and Activate Segments on DinMo
        • Create your first Segment
        • Activate your first Segment
    • 🌐Workspaces & Organizations
    • 💭Need Help?
  • Integrations
    • Data Sources
      • AWS Redshift
      • Databricks
      • Google BigQuery
      • PostgreSQL
      • Snowflake
    • Destination Platforms
      • Actito
        • Synchronize users attributes
        • Export contact lists
      • All My SMS
      • Attentive
        • Synchronize Users
      • AWS S3
        • Export your data models and segments to AWS S3
      • Azure Storage
        • Export data to Azure Blob Storage
      • Batch
        • Synchronize contacts (MEP)
        • Synchronize profiles (CEP)
        • Send events (CEP)
      • Braze
        • Synchronize users attributes
        • Send track events
        • Synchronize subscription statuses
        • Export user lists
      • Brevo
        • Synchronize contacts
        • Export contact lists
      • Criteo
        • Export contact lists
      • Dialog Insight
        • Synchronise Contacts
      • Dotdigital
        • Synchronize contacts
        • Synchronize Insight Data collections
        • Export contact lists
      • Emarsys
        • Export contact lists
        • Synchronize contacts data
        • Synchronize custom table's data (RDS)
      • Firestore
        • Create and update Collection Documents
        • Export Audiences
      • Google Ads
        • Export audiences
        • Enhanced Conversions for Web
        • Upload click or offline conversions
          • Prerequisites and walkthrough
        • Adjust conversion events
        • Retract conversion events
        • Sync offline store conversions
      • Google Display & Video 360
        • Export audiences
      • Google Drive
        • Export data to Google Sheet
      • Google Search Ads 360
      • Hubspot
        • Synchronize objects
        • Synchronize custom CRM objects
      • Intercom
        • Export segments
        • Synchronize contacts
        • Synchronize companies
      • Iterable
        • Synchronize user attributes
        • Export contact lists
      • June Email Marketing
        • Export Contact Lists
      • Klaviyo
        • Export contact lists
        • Synchronise contacts
        • Create subscription list
      • LinkedIn Ads
        • Export user audiences
        • Export company audiences
      • Mailchimp
        • Export segments
      • Meta Ads
        • Export audiences
        • Send conversion events
      • Microsoft Ads (Bing)
        • Export audiences
      • Pinterest Ads
        • Export audiences
        • Send conversions
      • Reddit Ads
        • Export Audiences
      • Salesforce
        • Synchronize object attributes
        • Synchronize custom object attributes
      • Salesforce Marketing Cloud
        • Synchronize data extensions
        • Export audiences
      • SendGrid
        • Synchronize contacts
        • Export contact lists
      • Selligent
      • SFTP
        • Export your data models and segments
      • Snapchat Ads
        • Export Audiences
      • Splio
        • Synchronize contacts
      • TikTok Ads
        • Export Audiences
        • Send Offline Conversions
        • Send Web Conversions
      • X (Twitter)
        • Export audiences
      • Zendesk
        • Synchronize users
        • Synchronize custom objects' data
      • Zuora
        • Synchronize Accounts
        • Synchronize Subscriptions
        • Send Usage Data
  • Models
    • Overview
    • Primary Keys
      • Detect duplicate primary keys
    • Calculated Fields
  • Identity resolution
    • Overview
  • Segments
    • Visual Builder
    • Breakdowns
    • Overlap Analysis
  • Activations
    • Overview
    • Sync Scheduling
    • Troubleshooting Syncs
      • Automatic pause or resume Activations
      • Sync warnings
  • AI PREDICTIONS
    • Overview
    • LTV and Churn
    • Product Recommendations
  • Customer Hub
    • Overview
    • ⚡Getting Started
      • Schema configuration
      • Metrics configuration
      • Audience Creation
      • Audience Performance
    • Profiles API
  • Data hosting
  • DinMo Storage
  • Workspace management
  • Set Up
  • Managing Users & Roles
  • Audit Logs
  • Enterprise Single Sign-On (SSO)
  • Security & Privacy
  • Overview
  • Networking
  • Privacy
    • Data Processing
Powered by GitBook
On this page
  1. Activations
  2. Troubleshooting Syncs

Sync warnings

PreviousAutomatic pause or resume ActivationsNextOverview

Last updated 4 months ago

CtrlK
  • Overview
  • Warning types
  • Configuration
  • Where to check warnings?

Overview

You can set warnings and alerts to monitor sync successes and failures. DinMo supports sending alerts via Slack and email. Warnings can be set as default for all syncs of a specific destination or at the individual sync level.

Warning types

DinMo offers different types of sync warnings.

  • Activation failure: This alert will be triggered when an activation is not correctly sent to the destination (failed status for the entire sync). You'll get more information on the reasons for sync failure at overview level (insufficient credentials, missing source data, etc.).

  • Percentage of rejected rows: This warning will be triggered when a certain percentage of data has been refused on the destination side. This feature is useful when you expect that a certain number of rows may fail, and you don't want to be notified unless the number of errors is significant.

  • Jobs with no operations: This warning will be triggered when several runs have been made, without loading any data at the destination. Occasionally, some jobs will send no data at all (i.e. there has been no data update between the two jobs). However, if this situation persists, the behavior may not be normal and the segment may be broken. This feature alerts you to such cases!

If you wish, notifications can all be sent by e-mail and/or slack. In all cases, warnings will be available in DinMo at several locations on the platform.

To receive Slack sync notifications, you must connect Slack upstream in DinMo's general settings. 👉 To find out more, consult this section.

Configuration

Sync-specific warnings can be configured at the destination level (and will therefore be applied by default to all activations using this destination) or at the level of a specific sync.

Alerts for complete sync failure must be configured in workspace settings. 👉 To find out more, consult this section.

  1. At the destination level

When a destination is created, DinMo suggests configuring default activation settings for all destinations that support it.

At the bottom of the configuration page, DinMo lets you create warnings for this destination.

How to — Set up sync warnings at the destination level
  1. At the sync level

When configuring an activation, you must:

  • Choose the segment that must be synchronised with your destination

  • Choose the destination that will receive the data

  • Configure your activation

At the bottom of the configuration page, DinMo lets you create warnings for this sync.

If you have created default activation settings, but do not wish to apply them to a specific activation of this destination, you can always click on “Advanced configuration”.

Advanced configuration allows you to modify the warnings for a specific sync, without modifying all the default activation settings.

No matter where you decide to set up your warnings, you'll be asked for the same information, which we detail below.

When creating Warnings, you will be encouraged to choose the type of alert you want, between Percentage of rejected rows or Jobs with no operations.

Percentage of rejected rows

If you choose Percentage of rejected rows, then you'll also have to choose the percentage above which you want to be alerted and the means of alert communication (email/slack).

👇 In the example below, you will be notified as soon as the number of rows rejected by the destination or DinMo exceeds 10% of the total number of rows.

Warning and email alert if the percentage of rejected rows is higher than 10%

Jobs with no operation

If you choose Jobs with no operation, then you'll also have to number of jobs without operation above which you want to be alerted and the means of alert communication (email/slack).

👇 In the example below, you will be notified as soon as the number of jobs with no operation is higher than 3.

Warning and email alert if the number of jobs without operation is higher than 3

Where to check warnings?

If you have selected the option to be alerted by e-mail or Slack, you will receive specific communications on these channels.

You will receive maximum 1 notification per alert configuration per 24h.

In all cases, warnings are also available directly on the platform:

  • In the Control Center

  • In the Activation List

  • In the Activation Overview

  • In the Activation run history

Of course, as soon as the problem is solved, the warning disappears from the application.