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
      • Stripe
      • The Trade Desk
      • TikTok
      • Totango
      • 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
      • 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
  • 1. Get API key from Amplitude
  • 2. Create the Census Connection
  • 3. Create your first Model
  • 4. Create your first Sync
  • ️ Supported Objects and Sync Behaviors
  • Working with Amplitude's Data Model
  • Need help connecting to Amplitude?

Was this helpful?

  1. Destinations
  2. Available Destinations

Amplitude

This page describes how to use Census with Amplitude.

PreviousAmazon S3NextAnaplan

Last updated 2 months ago

Was this helpful?

Getting Started

‌In this guide, we will show you how to connect Amplitude to Census and create your first sync.

Prerequisites

  • Have your Census account ready. If you need one, now.

  • Have your Amplitude account ready.

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

1. Get API key from Amplitude

Census needs only one piece of information to connect to your Amplitude project

  • The API Key for an HTTP API data source for your Amplitude project

To find your Amplitude project's unique API key, follow these steps.

  1. Click Projects, then find your target project.

  2. On the General tab, copy your API key and secret key.

2. Create the Census Connection

Now that we have the API Key from Amplitude, we can now set up Amplitude as a Destination in Census.

  1. In the Destinations section of Census, create a new Amplitude connection by clicking the New Destination button and searching for "Amplitude" in the search bar.

  1. You can provide whatever name you like.

  2. Provide the copied API Key from Amplitude.

  3. Choose the appropriate region

  4. Click Connect

3. Create your first Model

Here you will have to write SQL queries to select the data you want to see in Amplitude. Here are some ideas of data you should select

  • The Lifetime Value of a customer

  • The end date of a user's trial

  • The date a user became active in your product

  • The number of key activities a user did in your app in the last 7/30 days

Once you have created your model, click save.

4. Create your first Sync

In the "What data do you want to sync?" section.

  • For the Connection, select the data warehouse you've already connected (See Prerequisites).

  • For the Source, select the model you created in step 4.

Next up is the "Where do you want to sync data to?" section.

  • Pick the Amplitude connection you created in step 3.

  • For Object, Select Device or User. If Devices can be associated with Users, then select Device. If no Device information is collected, select User.

For the "How should changes to the source be synced?" section.

  • Select Update Or Create

  • Pick the right mapping key; Amplitude only supports Distinct ID.

Finally, select the fields you want to update in the Mapper in the "Which Fields should be updated?" section. Here simply map the field from your Amplitude instance to the column from your model.

Click the Next button to see the final preview, which will have a recap of what will happen when you start the sync.

️ Supported Objects and Sync Behaviors

Object Name

Supported?

Sync Keys

Behaviors

Devices

✅

Device ID

Update or Create

Users

✅

User ID

Update or Create

Groups

✅

Group Value

Update or Create

Events

✅

Insert ID

Send

Both User and Device objects will resolve to a single User Profile in Amplitude. If Devices can be associated with Users, then select Device and map the User field to an appropriate value in your model. If no Device information is collected, select User.

Working with Amplitude's Data Model

Amplitude has very well optimized data model for analyzing time series event, but this model presents some quirks and challenges for historic data updating.

Each Event record in Amplitude has a snapshot of any user and group properties that applied to it at the moment that event was ingested into Amplitude. Amplitude's analyzes this event stream so this makes querying events really efficient.

But these events are immutable, meaning once they're written, they're never updated again, including that snapshot of user and group properties. This introduces some quirks:

  • If user properties are updated by Census, those user properties will only apply to any future ingested events at the time of their ingestion. So if User A's properties are updated by Census today, but they never again generate an event, the Amplitude UI will never show the updated user properties because none of the previous events' snapshots can be changed to reflect the updated properties.

  • This also means that historical event imports are limited. Historical events can be imported with updated user and group properties, but again, those properties will only be reflected on events ingested after the historical sync in real world time**,** not just in the future according to the timestamp of the events. This is because all events already ingested are immutable.

Working Around Missing User Properties

‌

Need help connecting to Amplitude?

In the Amplitude Analytics web app, click in the lower left navigation.

Now navigate to the

Now head to the and click the Add Sync button

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

if you want Census to support more Amplitude objects and/or behaviors.

This is Amplitude's intended design: fast, but with some inflexibility. You can read more about it in .

As a result of this behavior, we often get asked "Why can't I see my user properties?" and we explain that it's likely because the user hasn't had a subsequent event. Some users choose to work around this by creating a sort of Updated By Census synthetic Event instead of using the User Identify destination object. If you chose to go this route, you'll likely want to tell Amplitude to consider this an inactive event so that the user doesn't appear as active when this happens. See on the steps to define that and make sure you do this before running the sync to avoid accidentally marking your users as active.

‌ 🔋 if you want Census to support more Sync Behaviors for this destination.

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

🛫
create a Free Trial Census account
Azure Synapse
Databricks
Elasticsearch
Google BigQuery
Google Sheets
MySQL
Postgres
Redshift
Snowflake
SQL Server
Settings
Model section of our Dashboard
Sync page
Syncs
Contact us
Amplitude's documentation
Amplitude's documentation
Contact us
Contact us
in-app