Destination Platforms

A destination refers to any external tool or service to which you can send source data. This is where the data is usually accessed and utilized by the end users.
Examples of destinations include advertising platforms (such as Facebook Ads or Google Ads), customer relationship management software (such as Hubspot or Salesforce), or customer support tools (such as Zendesk). Other types of platforms, such as Facebook Catalog, are also supported on DinMo.
For guidance on connecting your designated destination, consult the corresponding section Connect a Destination

Destination platforms

These are typically where end-users consume data, including CRM systems, ad platforms, marketing automation tools, and support tools. DinMo seamlessly integrates with these destination platforms, providing a unified data solution. To add a destination platform, you establish a connection to the platform authorizing DinMo to create objects or/and update them with your source data.
You will find below the documentation related to all Destination platforms supported by DinMo:

Ad platforms

CRM platforms

Destination services

Destination services refer to what you are syncing/updating in a destination platform.
DinMo can update three types of objects within a destination platform:
  • Events: such as conversion events for Facebook Ads or conversion actions for Google Ads. This is the default destination type of event segments. DinMo syncs events to destination platforms in batch to optimize the data transfer process and ensure efficient handling of large volumes of event data. By grouping events together and sending them as batches, DinMo minimizes the number of individual requests made to the destination platforms, reducing network overhead and improving overall performance. The sync frequency is set when configuring the activation and can be up to real-time.
  • Lists: in some platforms, they can also be called segments or audiences, such as Customer List in Facebook Ads, static segments in Selligent Cloud, or cohorts in Braze. They are used to indicate membership of the platform contacts or users (ex., HubSpot contacts table) to a specific based on specific rules. This is the activation target of User Segment in DinMo.
  • Attribute objects: such as contacts tables within a CRM or catalog items in advertising platforms. They are dimensional entities that describe an identifiable contact. They contain attributes that change slowly, like (lifetime value, address, etc.).

Activation Targets

Activation Targets simplify the activation configuration process by allowing you to set it up just once, eliminating the need for repetitive configuration.
Before you can start sending data to destination platforms through DinMo, you need to choose an appropriate activation target, or create it if it does not exist yet. An activation target is a tailored configuration within DinMo that represents the core parameters of the destination platform where you intend to send your data. It is made of two parts:
  • Core parameters defining where your data should be sent. This information cannot be changed after the creation of the activation target. Core parameters typically include:
    • The Destination Platform (for example, Google Ads, or Meta Ads)
    • The Destination Service (for example, Google Enhanced Conversions)
    • The Destination Configuration (for example, the ad account, or the pixel ID)
  • Default activation settings defining how your data should be sent. This information can be changed when creating an activation, but is proposed by default in order to simplify the activation process. Default activation settings typically include:
    • The parent entity of all the segments typically sent to the activation target
    • The identifiers to match your entity segments with the target’s data (example: user id, email, phone, first name, last name, etc.)
    • The attributes within the target to be updated with segment attributes (if relevant)
    • The time frequency at which DinMo will update the target
Note that you can create as many activation targets as you want for a single destination platform. In this case, one activation target may correspond to a specific ad account, or to a specific type of sync: one activation target for syncing customer segments, one activation target for syncing web conversions, one activation target for syncing offline conversions, etc.
Last modified 2mo ago