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
  1. Integrations
  2. Destination Platforms
  3. Klaviyo

Create subscription list

Use this destination to subscribe or unsubscribe profiles to email marketing, SMS marketing, or both.

PreviousSynchronise contactsNextLinkedIn Ads

Last updated 1 month ago

Overview

In this destination service, DinMo will subscribe or unsubscribe profiles to email marketing, SMS marketing, or both.

Previously, user consent could be added with any profile update/create request, like in Events. Now, user consent is configured at the Subscription List level. More info in the .

To do so, you will need to go through these steps:

  • Creating a Klaviyo destination. Refer to the for more info.

  • Create a user segment made up of users who need to opt in to specific communication channels (e-mail, SMS, or both). Refer to this to learn how to build segments without SQL in DinMo

  • Activating the segment to the Klaviyo destination to start sending data.

Each time the activation will be running:

  • Any new user entering your DinMo segment will be added to your Klaviyo list, and will be opt-in to the specific channel (e-mail, SMS, or both)

  • Any user leaving your DinMo segment will be removed from your Klaviyo list, and so will be opt-out to the specific channel (e-mail, SMS, or both)

Note that only users who have an email linked to a Klaviyo contact will be present in your Klaviyo list. In this service, DinMo will not create new contacts in Klaviyo. If you need to create a new contact, please refer to this destination service.

Destination setup

To start subscribing or unsubscribing profiles, you are first required to create a Klaviyo destination with the corresponding destination service.

Learn how to create such a destination in our

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.

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

To configure your default activation settings:

  • Select the underlying Users Model

  • Decide whether to subscribe/unsubscribe people to email, SMS or both.

  • Choose whether or not to import consent history. In that case, you'll need to map the "Consent At" field.

  • Map your different model fields to link your columns to standard fields to facilitate activating your data on Klaviyo. Be sure to map the phone number if you've selected SMS and email if you've selected email.

Double opt-in vs. single opt-in

Double opt-in can trigger confirmation messages to the end user when subscribing them via the Klaviyo API. This may be an unwanted behavior.

By default, DinMo will create a list set to double opt-in. `

If this is not the behavior you want, you must:

  • Create a new list in Klaviyo which is called "DinMo Subscription List", before creating the activation in DinMo

  • Set the opt-in process at "Single opt-in" in the settings of that list (see screenshot below)

Activation configuration

Once the destination has been setup, and your DinMo segment created, you can create an activation to start sending data to Klaviyo right away. The segment will be exported as a contact list in Klaviyo.

Activation Name and Description

In this section, the name you enter will be the name given to the list created in Klaviyo.

By default, and if you activate your segment using the default activation settings, the name of the list will be DinMo Subscription List.

Scheduling

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

  • Any new user having entered your DinMo segment since the last update will be added to your list, if and only if this user is already an existing Klaviyo contact. They will be opt-in to the specific channel (e-mail, SMS, or both)

  • Any user having left your DinMo segment since the last update will be removed from your list. They will be opt-out to the specific channel (e-mail, SMS, or both)

By configuring default settings, subscribing and unsubscribing profiles will just take one click. Without default settings, you will be required to go through the each time you activate a new segment.

To subscribe users to SMS, it is required to first setup SMS in Klaviyo.

If you select it, Klaviyo will not send a confirmation email to the users (skips the ). It should be used when importing profiles that have given consent in the past (for example if you are migrating data). In that case, you will need to map the "Consent At" field, that represents the moment the profile consented to be subscribed to marketing communication

Learn how to activate a segment in our

configuration
Learn more in the Klaviyo documentation
step-by-step tutorial
official Klaviyo documentation
step-by-step tutorial
step-by-step tutorial
corresponding section
double opt-in
Klavio - at the list level: select single or double opt-in