DinMo integrations

Attentive (contact lists). Sets a true or false Attentive attribute for existing users, matched by email or phone, as they enter or leave a DinMo segment, so the list can be built by filtering in Attentive.

Attentive (subscriber attributes). Updates standard and custom attributes of existing Attentive subscribers, matched by email or phone, from a DinMo model, with a first full load that can take hours and only changes after that.

Emarsys (contact lists). Creates Emarsys contact lists from DinMo models or segments and keeps membership current for existing contacts matched by email, without creating or deleting any contact.

Emarsys (contacts). Updates Emarsys contact fields from a DinMo model by clear-text email and can insert new contacts into a list chosen at setup, since Emarsys needs every contact in a list.

Emarsys (RDS custom tables). Updates rows of a predefined Emarsys Relational Data Service table from a DinMo model, matched on its id column and optionally inserting rows, for accounts with RDS enabled.

ActiveCampaign (audiences). Subscribes contacts entering a DinMo segment to an ActiveCampaign list and unsubscribes those who leave, creating the list if needed and optionally managing a contact tag too.

ActiveCampaign (contact attributes). Creates and updates ActiveCampaign contacts matched by email from a DinMo model or segment, filling standard and custom fields and adding missing custom fields, without deleting anyone.

ActiveCampaign (contact tags). Adds a chosen ActiveCampaign contact tag, such as VIP, to people entering a DinMo segment and removes it when they leave, keeping both the contacts and the tag itself.

ActiveCampaign (events). Sends named events with one optional text value from DinMo to existing ActiveCampaign contacts, matched by email, through ActiveCampaign Event Tracking and its event key.

Dotdigital (contact lists). Maintains a Dotdigital contact list for each DinMo segment, public or private, adding and removing members by contact ID, email or phone.

Dotdigital (contacts). Upserts Dotdigital contacts from DinMo segments by contact ID, email or phone, creating missing custom fields, with newly created contacts subscribed to email automatically.

Dotdigital (Insight data). Writes purchase, browsing or review records from DinMo into Dotdigital Insight data collections, new or existing, each linked to an existing contact or account by contact ID, email or phone.

Dotdigital (program enrollment). Enrolls contacts who enter a DinMo audience into an existing Dotdigital program through its API, starting the journey at once, without removing them when they later leave the audience.

Brevo (contact lists). Creates a Brevo list per DinMo segment in a folder you choose and adds or removes existing contacts by email as the segment changes, without creating new contacts.

Brevo (contacts). Updates Brevo contact attributes from DinMo segments by clear-text email and can insert new contacts, which land in a DinMo list inside a DinMo folder, with custom attributes added.

Batch (catalogs). Syncs products, offers or other items from DinMo into a Batch catalog through the Batch Catalog API, creating the catalog if needed and upserting, mirroring or deleting items.

Batch (CEP audiences). Creates Batch CEP audiences from DinMo segments and keeps members current by Batch external ID, using an API name plus a display name, without creating contacts.

Batch (CEP events). Sends new rows of a DinMo event model to Batch CEP profiles as events, linked by custom profile ID, with a lowercase event name, timestamp, label and custom event attributes.

Batch (CEP profiles). Creates and updates Batch CEP profiles from DinMo by custom profile ID, including email, phone, language, time zone and subscription fields, with an optional mirror mode that deletes profiles.

Batch (MEP contacts). Updates custom attributes on existing Batch MEP contacts from DinMo segments, matched by email or external ID, since the Batch API can't create contacts.

Batch (profile deletion). Deletes Batch CEP or MEP profiles permanently when they are in a DinMo segment, either for the whole segment on every run or only for people new to it since the last run.

Selligent (contact lists). Keeps Selligent lists of existing users in step with DinMo audiences, each named after its audience, adding and removing users by a matching key without creating new ones.

Selligent (record attributes). Updates changed attribute values in the Selligent users table from DinMo models, optionally inserting new users, matched on a key field and mapped to Selligent field names.

Splio. Updates Splio contact attributes from DinMo segments by email and can import new contacts and custom attributes, as far as your Splio SFTP configuration permits.

Actito. Updates Actito profile attributes from a DinMo model or segment, optionally creating profiles, in insert, update, upsert or mirror mode, where mirror deletes profiles missing from the source.

Actito (contact lists). Keeps Actito external target lists in step with DinMo segments, adding entrants and removing leavers matched by email, phone or external ID, without creating new contacts.

Actito (custom tables). Writes rows from a DinMo model or segment into an Actito custom table of your choice, inserting, updating or mirroring records and creating missing attributes as needed.

June Email Marketing. Adds users from DinMo segments to a dedicated June email list, matched by email, and tags them with each segment's name for June segmentations, without removing anyone who leaves.

June Email Marketing (customer attributes). Keeps June contact attributes in step with a DinMo model, matched by email, in upsert mode or in a mirror mode that also deletes contacts missing from the source.

Voyado Engage. Enriches Voyado Engage contacts with profile attributes and predictive scores from DinMo models, matched by email or contactId, updating existing contacts or also inserting new ones.

Voyado Engage (segments as labels). Mirrors DinMo audience membership onto existing Voyado Engage contacts as labels, or as selected email or SMS consent statuses, adding and removing contacts as audiences change.

Dialog Insight. Upserts Dialog Insight contacts from DinMo segments by dropping a CSV on an SFTP server that a remotely launched Dialog Insight import automation loads into the contact list.

Criteo. Creates Criteo audience segments in a chosen ad account from DinMo segments and updates membership using emails, LiveRamp identity links, mobile ad IDs or retail media customer IDs.

Pinterest (audiences). Creates Pinterest Ads audiences in a chosen ad account from DinMo segments and keeps them current by email address, sent plain or SHA-256 hashed.

Pinterest (conversions). Sends web, app or offline conversion events from DinMo event segments to a Pinterest ad account with event time, action source, event ID and email, within Pinterest's 7-day limit.

The Trade Desk (CRM segments). Creates The Trade Desk CRM segments in a chosen region from DinMo segments and keeps them updated with emails or phone numbers, plain or SHA-256 hashed.

The Trade Desk (first-party segments). Builds The Trade Desk first-party segments from DinMo audiences using identifiers such as Trade Desk GUIDs, UID2, EUID, RampID or hashed emails and phones.

X Ads. Creates X (Twitter) Ads audiences from DinMo segments and updates them using emails, phone numbers, device IDs, X user IDs or handles, plain or SHA-256 hashed.

Reddit. Creates Reddit Ads audiences in a business account from DinMo segments, sending emails that DinMo hashes automatically or mobile advertising IDs, and updates membership on schedule.

Google Display & Video 360. Creates Google Display & Video 360 audiences from DinMo segments using contact info or mobile IDs, adding and removing members on schedule and applying list-level consent for ad data use.

Meta Conversions API. Sends online, offline or CRM lead conversion events from DinMo event segments to a Meta dataset through the Conversions API, one event type and action source per activation.

Google Ad Manager (audiences via batch upload). Fills publisher-managed Google Ad Manager audiences with PPIDs or mobile ad IDs from DinMo segments by writing batch upload files to the Google Cloud Storage bucket linked to your account.

Google Ad Manager (key-values via Firestore). Adds DinMo segments as values of a dinmo_segments key in Google Ad Manager and writes each profile's segments to Firestore, for your tag manager to pass to the Google Publisher Tag.

Taboola. Creates or reuses Taboola first-party audiences for DinMo segments and updates their members with SHA-256 hashed emails or unhashed mobile advertising IDs.

OpenAI Ads (audiences). Creates a ChatGPT Ads custom audience from a DinMo user segment and syncs its membership, sending normalized emails or phone numbers, existing SHA-256 hashes or Android advertising IDs.

OpenAI Ads (conversions). Delivers ChatGPT Ads conversions from DinMo event data to the OpenAI Conversions API, hashing user identifiers and converting amounts to minor units, with one Event Setting per activation.

OpenAI Ads (product feed). Sends ChatGPT Ads a full catalog snapshot built from a DinMo product model, written as one Google-compatible CSV file over SFTP and replaced each run, for up to 500,000 products.

Yahoo DSP (audiences). Adds people from DinMo segments to an advertiser's Yahoo DSP custom audience by email, IP address or mobile ad ID through the Traffic API, without ever removing those who leave.

Yahoo DSP (source). Brings Yahoo DSP Traffic API tables (general, audience and targeting) and prebuilt or custom reports in through DinMo Ingest, with rollback windows set by report interval.

Google Search Ads 360. Sends Floodlight conversions from DinMo event segments to Google Search Ads 360 as transactions or actions for a chosen device type, with Google click ID, conversion ID, timestamp and event name.

Azure Blob Storage. Writes DinMo models or segments to an Azure Blob Storage container as CSV, JSON, XML or Parquet files, including a difference mode that splits added, updated and removed records.

SFTP. Delivers DinMo segment or model extracts to an SFTP server in CSV, JSON, XML or Parquet, with timestamped names, chunked large exports and snapshot, upsert, insert or difference modes.

PostgreSQL. Connects a PostgreSQL database to DinMo through a dedicated user that reads the tables behind models and segments and writes to DinMo's own technical schemas.

MySQL. Writes profile attributes from DinMo segments or models into an existing MySQL table with upsert or mirror behavior, in beta, without creating tables or changing the schema.

Microsoft Fabric. Connects a Microsoft Fabric Warehouse, not a Lakehouse endpoint, to DinMo through an Entra service principal, so DinMo reads business schemas and keeps five technical schemas there.

ClickHouse. Connects ClickHouse to DinMo with a dedicated user and role that read the data for models and segments and write segment stats and snapshots to a technical database.

Redis. Maintains DinMo audience membership in Redis Sets stored at each profile key's .dinmo_segments, using SADD and SREM, so apps can check segments with low latency.

FTP. Uploads DinMo model or segment data to an FTP server as CSV, JSON, XML or Parquet files, choosing the folder, a timestamped file name and snapshot, upsert, insert or difference mode.

Firestore (audiences). Adds or removes DinMo segment names in a dinmo_segments field on Firestore documents as profiles enter or leave segments, creating missing documents, for web and app personalization.

Firestore (documents). Upserts Firestore documents in a chosen collection from DinMo profiles, keyed by a document ID, with merge or overwrite writes and optional last-updated or time-to-live fields.