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
      • 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
      • 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
      • Google Display & Video 360
        • Export audiences
      • Google Search Ads 360
      • Hubspot
        • Synchronize 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 Marketing Cloud
        • Synchronize data extensions
      • SendGrid
        • Synchronize contacts
        • Export contact lists
      • Selligent
      • 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
  • 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
  • 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
  • Overview
  • Destination setup
  • Activation configuration
  • Fields mapping
  1. Integrations
  2. Destination Platforms
  3. Emarsys

Synchronize custom table's data (RDS)

PreviousSynchronize contacts dataNextFirestore

Last updated 4 months ago

Overview

This destination service is only relevant for Emarsys accounts with Relational Data Service (RDS) enabled.

In this destination service, DinMo will export and update rows of a pre-defined custom table located in Emarsys Relational Data Service (RDS), and optionally, insert new rows into this table.

The custom table should already exist in Emarsys RDS, with its schema configured, and, one of its column corresponding to the primary key should be exactly named 'id'.

To create such an activation, you will need to go through these three steps:

  • Creating an Emarsys destination. Refer to the for more info.

  • Creating a custom segment or custom model composed of all the records and their attributes that will be updated in Emarsys.

  • Activating the model to the Emarsys destination to start sending data. Refer to the for more info.

Each time the activation will be running:

  • If you ticked the insert mode option, all new records in the model will be inserted in the Emarsys custom table

  • All rows values that have changed since the last activation will be updated in the Emarsys custom table

If you chose not to insert new records, only records of the model which are already present in Emarsys will be updated.

Destination setup

To start synchronizing custom tables' data, you are first required to create an Emarsys destination with the corresponding destination service.

Learn how to create such a destination in our

In this process, you must enter the connection name in which your target table is contained. The connection name can be found under the Connections tab of the Relational Data add-on in Emarsys:

Next, enter the name of the target custom table that DinMo will update. The table must have been prievously created on Emarsys side. The table must already contain all relevant columns that DinMo will be updating, and, it must have a column exactly named id, that will be used to match records between DinMo and Emarsys.

Activation configuration

Once the destination has been setup, and your DinMo model created, you can create an activation to start sending data to Emarsys right away.

Fields mapping

In the Fields mapping section, you are asked to specify the field contained in your DinMo model corresponding to the identifier column of the target custom table. This field will be used to link the model's records to existing rows in Emarsys.

You can then map any other column existing in your Emarsys custom table. These attributes will then be updated by DinMo during each activation.

Learn how to activate a segment in our

step-by-step tutorial
step-by-step tutorial
corresponding section
corresponding section