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. Integrations
  2. Destination Platforms
  3. Salesforce Marketing Cloud

Export audiences

PreviousSynchronize data extensionsNextSendGrid

Last updated 1 month ago

CtrlK
  • Overview
  • Destination setup
  • Activation configuration
  • Scheduling

Overview

In this destination service, DinMo DinMo will create lists of contacts and keep them up to date in SFMC.

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

  • Create a Salesforce Marketing Cloud destination. Refer to the corresponding section for more info.

  • Create a segment or a model composed of all the rows that will populate the Salesforce audience list.

  • Activate the segment or model to the Salesforce destination to start sending data. Refer to the corresponding section for more info.

Each time the activation is running:

  • Any new user entering your DinMo segment or model will be added to your SFMC list

  • Any user leaving your DinMo segment or model will be removed from your SFMC list

Destination setup

To start synchronising audiences, you are first required to create a Salesforce Marketing Cloud destination with the corresponding destination service.

In this process, you must specify how data will be transferred:

  • Either using an FTP user. In this case, you must indicate the file transfer location

  • Either through Amazon S3. In this case, you must again indicate the file transfer location.

Configuring Amazon S3 Access

Amazon S3 Access requires you to input an AWS role ARN to give DinMo write access to your S3 bucket at the file transfer location.

In order to do so, you must add this role arn to the role's trust policy : arn:aws:iam::724998534403:role/DinmoS3AccessorRole-dinmo-prod

Here is an example of a trust policy with that role :

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Principal": {
                "AWS": "arn:aws:iam::724998534403:role/DinmoS3AccessorRole-dinmo-prod"
            },
            "Action": "sts:AssumeRole"
        }
    ]
}

Here is a minimal policy granting s3 access to a role

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "s3:ListBucket"
            ],
            "Resource": "arn:aws:s3:::example-bucket"
        },
        {
            "Effect": "Allow",
            "Action": [
                "s3:GetObject",
                "s3:PutObject",
                "s3:DeleteObject"
            ],
            "Resource": "arn:aws:s3:::example-bucket/*"
        }
    ]
}

Learn how to create such a destination in our step-by-step tutorial

Activation configuration

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

Learn how to activate a segment in our step-by-step tutorial

Optional: Setup default activation settings

At the end of the destination creation, you will be proposed to setup Default Activation Settings. This step is optional, but is highly recommended to facilitate the activation process.

By configuring default settings, synchronizing all your audiences to Meta will just take one click. Without default settings, you will be required to go through this configuration each time you activate a new audience.

Note that even if you setup default settings, you will still be able to adjust activation settings for each of your audiences if you wish to.

In the Fields mapping section, you are asked to specify which field corresponds to the Contact Key of the users of the segment. This is the field that SFMC will use to recognise the contacts sent by DinMo.

Any non mapped fields in your segment will not be sent to Salesforce Marketing Cloud. SFMC will use these fields to enrich your customer list.

Scheduling

In this section, specify how often the list should be updated in SFMC. Every time the list is updated:

  • Any new user having entered your DinMo model or segment since the last update will be added to your list, if and only if this user is already an existing SFMC contact

  • Any user having left your DinMo model or segment since the last update will be removed from your list

Warnings

In this section, specify if you want to receive warning for your Salesforce Marketing Cloud activation.

Consult the specific section to learn more about sync warnings.