LogoLogo
  • 🦩Overview
  • 💾Datasets
    • Overview
    • Core Concepts
      • Columns & Annotations
      • Type & Property Mappings
      • Relationships
    • Basic Datasets
      • dbt Integration
      • Sigma Integration
      • Looker Integration
    • SaaS Datasets
    • CSV Datasets
    • Streaming Datasets
    • Entity Resolution
    • AI Columns
      • AI Prompts Recipe Book
    • Enrichment Columns
      • Quick Start
      • HTTP Request Enrichments
    • Computed Columns
    • Version Control
  • 📫Syncs
    • Overview
    • Triggering & Scheduling
    • Retry Handling
    • Live Syncs
    • Audience Syncs
    • Observability
      • Current Sync Run Overview
      • Sync History
      • Sync Tracking
      • API Inspector
      • Sync Alerts
      • Observability Lake
      • Datadog Integration
      • Warehouse Writeback
      • Sync Lifecycle Webhooks
      • Sync Dry Runs
    • Structuring Data
      • Liquid Templates
      • Event Syncs
      • Arrays and Nested Objects
  • 👥Audience Hub
    • Overview
    • Creating Segments
      • Segment Priorities
      • Warehouse-Managed Audiences
    • Experiments and Analysis
      • Audience Match Rates
    • Activating Segments
    • Calculated Columns
    • Data Preparation
      • Profile Explorer
      • Exclusion Lists
  • 🧮Data Sources
    • Overview
    • Available Sources
      • Amazon Athena
      • Amazon Redshift
      • Amazon S3
      • Azure Synapse
      • ClickHouse
      • Confluent Cloud
      • Databricks
      • Elasticsearch
      • Kafka
      • Google AlloyDB
      • Google BigQuery
      • Google Cloud SQL for PostgreSQL
      • Google Pub/Sub
      • Google Sheets
      • Greenplum
      • HTTP Request
      • HubSpot
      • Materialize
      • Microsoft Fabric
      • MotherDuck
      • MySQL
      • PostgreSQL
      • Rockset
      • Salesforce
      • SingleStore
      • Snowflake
      • SQL Server
      • Trino
  • 🛫Destinations
    • Overview
    • Available Destinations
      • Accredible
      • ActiveCampaign
      • Adobe Target
      • Aha
      • Airship
      • Airtable
      • Algolia
      • Amazon Ads DSP (AMC)
      • Amazon DynamoDB
      • Amazon EventBridge
      • Amazon Pinpoint
      • Amazon Redshift
      • Amazon S3
      • Amplitude
      • Anaplan
      • Antavo
      • Appcues
      • Apollo
      • Asana
      • AskNicely
      • Attentive
      • Attio
      • Autopilot Journeys
      • Azure Blob Storage
      • Box
      • Bloomreach
      • Blackhawk
      • Braze
      • Brevo (formerly Sendinblue)
      • Campaign Monitor
      • Canny
      • Channable
      • Chargebee
      • Chargify
      • ChartMogul
      • ChatGPT Retrieval Plugin
      • Chattermill
      • ChurnZero
      • CJ Affiliate
      • CleverTap
      • ClickUp
      • Constant Contact
      • Courier
      • Criteo
      • Crowd.dev
      • Customer.io
      • Databricks
      • Delighted
      • Discord
      • Drift
      • Drip
      • Eagle Eye
      • Emarsys
      • Enterpret
      • Elasticsearch
      • Facebook Ads
      • Facebook Product Catalog
      • Freshdesk
      • Freshsales
      • Front
      • FullStory
      • Gainsight
      • GitHub
      • GitLab
      • Gladly
      • Google Ads
        • Customer Match Lists (Audiences)
        • Offline Conversions
      • Google AlloyDB
      • Google Analytics 4
      • Google BigQuery
      • Google Campaign Manager 360
      • Google Cloud Storage
      • Google Datastore
      • Google Display & Video 360
      • Google Drive
      • Google Search Ads 360
      • Google Sheets
      • Heap.io
      • Help Scout
      • HTTP Request
      • HubSpot
      • Impact
      • Insider
      • Insightly
      • Intercom
      • Iterable
      • Jira
      • Kafka
      • Kevel
      • Klaviyo
      • Kustomer
      • Labelbox
      • LaunchDarkly
      • LinkedIn
      • LiveIntent
      • Loops
      • Mailchimp
      • Mailchimp Transactional (Mandrill)
      • Mailgun
      • Marketo
      • Meilisearch
      • Microsoft Advertising
      • Microsoft Dynamics
      • Microsoft SQL Server
      • Microsoft Teams
      • Mixpanel
      • MoEngage
      • Mongo DB
      • mParticle
      • MySQL
      • NetSuite
      • Notion
      • OneSignal
      • Optimizely
      • Oracle Database
      • Oracle Eloqua
      • Oracle Fusion
      • Oracle Responsys
      • Orbit
      • Ortto
      • Outreach
      • Pardot
      • Partnerstack
      • Pendo
      • Pinterest
      • Pipedrive
      • Planhat
      • PostgreSQL
      • PostHog
      • Postscript
      • Productboard
      • Qualtrics
      • Radar
      • Reddit Ads
      • Rokt
      • RollWorks
      • Sailthru
      • Salesforce
      • Salesforce Commerce Cloud
      • Salesforce Marketing Cloud
      • Salesloft
      • Segment
      • SendGrid
      • Sense
      • SFTP
      • Shopify
      • Singular
      • Slack
      • Snapchat
      • Snowflake
      • Split
      • Sprig
      • Statsig
      • Stripe
      • The Trade Desk
      • TikTok
      • Totango
      • Unify
      • Userflow
      • Userpilot
      • Vero Cloud
      • Vitally
      • Webhooks
      • Webflow
      • X Ads (formerly Twitter Ads)
      • Yahoo Ads (DSP)
      • Zendesk
      • Zoho CRM
      • Zuora
    • Custom & Partner Destinations
  • 📎Misc
    • Credits
    • Census Embedded
    • Data Storage
      • Census Store
        • Query Census Store from Snowflake
        • Query Census Store locally using DuckDB
      • General Object Storage
      • Bring Your Own Bucket
        • Bring your own S3 Bucket
        • Bring your own GCS Bucket
        • Bring your own Azure Bucket
    • Developers
      • GitLink
      • Dataset API
      • Custom Destination API
      • Management API
    • Security & Privacy
      • Login & SSO Settings
      • Workspaces
      • Role-based Access Controls
      • Network Access Controls
      • SIEM Log Forwarding
      • Secure Storage of Customer Credentials
      • Digital Markets Act (DMA) Consent for Ad Platforms
    • Health and Usage Reporting
      • Workspace Homepage
      • Product Usage Dashboard
      • Observability Toolkit
      • Alerts
    • FAQs
Powered by GitBook
On this page
  • Getting started
  • Prerequisites
  • Step 1: Connect Ortto
  • Step 2: Connect your data warehouse
  • Step 3: Create your model
  • Step 4: Create your first sync
  • Step 5: Confirm the synced data in Ortto
  • Sync Speed
  • Supported objects
  • Supported Sync Behaviors
  • Need help connecting to Ortto?

Was this helpful?

  1. Destinations
  2. Available Destinations

Ortto

This page describes how to use Census with Ortto.

PreviousOrbitNextOutreach

Last updated 2 months ago

Was this helpful?

Getting started

This guide shows you how to use Census to connect your Ortto account to your data warehouse and create your first sync.

Prerequisites

Before you begin, you'll need the following:

  • Census account: If you don't have this already, .

  • Ortto account

  • Have the proper credentials to access to your data source. See our docs for each supported data source for further information:

Step 1: Connect Ortto

  1. Click New Destination.

  2. Select Ortto from the dropdown list.

  3. Ortto uses API keys to authorize access to the API, so you will need to provide an API Key to Census.

    1. You can create an API key in Ortto specifically for Census. On the left-hand menu click More > Data Sources. On the Data Sources page click the New Data Source button then select Custom API (advanced). Give the source a name of your choosing and click Create. The API Key will be shown on the following page. Make sure to save it somewhere secure.

    2. Copy the API key and paste it into the API Key field in the Ortto setup in Census.

Step 2: Connect your data warehouse

The steps for connecting your data warehouse will depend on your technology. See the following guides:

Step 3: Create your model

When defining models, you'll write SQL queries to select the data you want to see in Ortto. This can be as simple as selecting everything in a specific database table or as complex as creating new calculated values.

  1. Enter a name for your model. You'll use this to select the model later.

  2. Enter your SQL query. If you want to test the query, use the Preview button.

  3. Click Save Model.

Step 4: Create your first sync

The sync will move data from your warehouse to Ortto. In this step, you'll define how that will work.

  1. Under What data do you want to sync?, choose your data warehouse as the Connection and your model as the Source.

  2. Under Which properties should be updated?, select the fields you want to update by mapping a field in Ortto to a column in your model.

  3. Click Next. This will open the Confirm Details page where you can see a recap of your setup.

  4. If you want to start a sync immediately, set the Run a sync now? checkbox.

  5. Click Create Sync.

When configuring your sync, the page should look something like this: 👇

Step 5: Confirm the synced data in Ortto

Once your sync is complete, it's time to check your data. Open Ortto and check that the records updated correctly.

If everything went well, that's it! You've started syncing data from your warehouse to Ortto! 🎉

Sync Speed

In most cases, you won't run into any issue with sync speed based on rate limiting unless:

  • You're running an initial sync action that will update many records in Ortto.

  • You have another integration or service that's making API calls to Ortto and using the same API key.

Supported objects

Object Name

Supported?

Sync Keys

Organization

✅

Name, Website

Person

✅

Email, External ID

Supported Sync Behaviors

Behaviors

Supported?

Objects

Update or Create

✅

Organization, Person

Update Only

✅

Person

Need help connecting to Ortto?

Log into Census and navigate to .

Ortto has custom rate limiting based on what plan you're on. You can check out the limits for your specific plan . Enter the limit for the 60s interval of your plan in the Rate limit per 60s field. If no limit is specified we will default to the Pro plan (600 requests/min).

From inside your Census account, navigate to the page.

From inside your Census account, navigate to the page.

Under Where do you want to sync data to?, choose Ortto as the Connection and an Object in Ortto. (See .)

Under How should changes to the source be synced?, choose Update or Create. (See .)

Under How are source and destination records matched?, select a mapping key. (See for details.)

And if anything went wrong, to get some help.

Sync speeds can be affected by API rate limiting from the destination app. Ortto has a number of different rate limiting criteria for their API depending on IP, Ortto tier, responses, and payloads. (See for details.)

if you want Census to support additional objects for Ortto.

Learn more about all of our sync behaviors in our documentation.

if you want Census to support more Sync Behaviors for Ortto.

via support@getcensus.com or start a conversation with us via the chat.

🛫
start with a free trial
Azure Synapse
Databricks
Elasticsearch
Google BigQuery
Google Sheets
MySQL
Postgres
Redshift
Snowflake
SQL Server
Destinations
here
Databricks
Google BigQuery
Google Sheets
Postgres
Redshift
Snowflake
Models
Syncs
contact the Census support team
Ortto API Documentation
Let us know
Syncs
Contact us
Contact us
in-app
Supported Objects
Supported Sync Behavior
Supported Objects
Basic SQL query for a new model
Sync setup for Ortto