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
  • Event Type
  • Fields mapping
  • Scheduling
  1. Integrations
  2. Destination Platforms
  3. Pinterest Ads

Send conversions

PreviousExport audiencesNextReddit Ads

Last updated 11 months ago

Overview

With this destination service, DinMo will send conversion events (online or offline) to optimize targeting (for instance: clicks, add to carts, purchase, etc.).

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

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

  • Creating an event segment composed of all the events you wish to send to Pinterest. All records of the segment correspond to a unique event type (for instance, purchase) and a unique action source (for instance, physical store), that was previously created in Pinterest. Refer to this to learn how to build segments without SQL in DinMo.

  • Activating the segment to the Pinterest destination to start sending data. Refer to the for more info.

DinMo will be sending all the new conversion events each time the activation is running.

Destination setup

Learn how to create such a destination in our

To start sending conversion events, you are first required to create a Pinterest destination with the corresponding destination service.

You will need to specify the ad account to which your events will be sent.

Note: If the dataset id you seek is not listed, it means that the user who connected DinMo to Pinterest does not have the permissions for this account.

Activation configuration

Once the destination has been setup, and your DinMo segment containing all your conversion events created, you can create an activation to start sending data to Pinterest right away.

Event Type

When setting up a activation, you need to specify the related event type. All records of the segment will be considered as events of the selected type (for instance, 'Add to cart').

Make sure your segment only contains conversions of the selected type.

Fields mapping

In the Fields mapping section, you are asked to specify the meaning of the fields of your segment that you wish to send to Pinterest. Any non mapped fields in your segment will not be sent to Pinterest.

Pinterest will use the fields you send to identify the conversions and their values, and recognize each user behind the conversions.

You must map the following fields:

  • Event time (Required): The timestamp when the conversion took place

  • Action source: Can be either app_android, app_ios, web, or offline

  • Event id: The identifier of the event

  • Email: The email addresses of the users. It can be in clear text, or hashed (SHA-256)

If the conversion is transactional (i.e referring to a purchase), you must also map the two following fields:

  • Value: The price spent by the customer during the transaction

  • Currency: The currency of the transaction

It is highly recommended to map the Event Id or Order Id field, but it is not compulsory.

To increase the chance of identifying the user behind the conversion, or, to send more details about the event, you can also map other non-required fields.

The higher the number of fields you send, the most likely Pinterest will be able to identify the users.

Scheduling

In this section, specify how often the conversions should be sent to Pinterest.

All new conversions will be sent in batch to Pinterest at the specified time interval.

Note that Pinterest will reject all conversions that are more than 7 days old.

Learn how to activate a segment in our

Refer to the to access the exhaustive list.

step-by-step tutorial
Pinterest documentation
step-by-step tutorial
step-by-step tutorial
corresponding section
corresponding section