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

Create and update Collection Documents

Sync your models profiles and attributes into a Firestore collection document to enable real-time personalization and rapid data retrieval in your apps and websites.

Overview

This destination service allows DinMo to insert new documents or update existing ones in your Firestore collections based on your DinMo profiles or segments.

To use this service, follow these three steps:

  1. Create a Firestore destination. Follow our step-by-step guide to establish this connection.

  2. Create your DinMo user segment or data model representing the data you want to sync to Firestore.

  3. Activate your segment or model with the Firestore destination to start synchronization.

Every time the activation runs:

  • DinMo performs an upsert operation:

    • Insertion: If a Firestore document matching the provided Document ID does not exist, DinMo will create it using the mapped attributes and document id value.

    • Update: If a document exists, DinMo updates only the mapped attribute values.

  • Attributes that exist will have their values updated.

  • Attributes not present in the document will be created upon the first synchronization and regularly updated afterward.

  • DinMo will not delete existing documents even if the profile no longer exists in the model or segment. It will simply stop updating these documents.

Destination Setup

Before beginning data synchronization, set up your Firestore destination:

  • Go to destinations > Add a destination.

  • Choose your Firestore Platform.

  • Click on Create and update Collection Documents option.

  • Give it a name and save the destination.

Activation Configuration

Once the Firestore destination is configured, create an activation to begin syncing your data:

  • Specify the Firestore collection name to store your synchronized data.

  • Define the mapping between your data warehouse attributes and Firestore document fields.

Field Mapping

During activation setup, you need to specify:

  • Document ID Mapping: Choose the unique DinMo profile field used as the Firestore Document ID.

  • Collection Name: Enter the name of your Firestore collection.

  • Custom Attributes: Add custom attributes by mapping model fields and typing in custom names that will be used as document field names.

Scheduling

Define how frequently your data is updated in Firestore. With each scheduled update:

  • DinMo will perform an upsert operation, inserting new documents or updating existing ones.

  • Existing documents not found in the current DinMo data segment or model will remain in Firestore but will not be updated further.

PreviousFirestoreNextExport Audiences

Last updated 1 month ago