Census changelog www.getcensus.com

Improvement

We now support the Opportunity object for our Planhat connector.

Improvement

We've expanded our support for our Freshsales connector and now you can sync to Deal objects.

Improvement

Our Reddit Ads destination now supports phone_number as a field for the Conversion Events object.

New

We've added support for Anthropic's latest model, Claude Sonnet 4.5, to Census AI Columns.

Claude Sonnet 4.5 offers improved reasoning capabilities and faster response times compared to Sonnet 4, making it ideal for complex data enrichment tasks like:

• Advanced sentiment analysis and classification
• Multi-step data transformations
• Nuanced text extraction and summarization

All existing AI Column workflows continue to work seamlessly. Simply select Claude Sonnet 4.5 from the model dropdown to try it out.

👉 AI Columns documentation

👉 Credit usage guide

Improvement

Good news! Our HTTP Request destination now supports OAuth.

What This Means for You

While we're continuously adding native destinations to Census, we know that sometimes you need to move faster than our product roadmap. The HTTP Request destination bridges that gap. It has always been our Swiss Army knife for data syncing, letting you send data to any service that accepts standard HTTP requests. Now, you can connect to APIs that require OAuth authentication flows, opening up even more integrations that aren't available on Census (yet).

How It Works

Setting up OAuth with the HTTP Request destination is straightforward:

1. Navigate to Destinations and create a new HTTP Request destination

2. Select OAuth as your Authentication Type

3. Configure your OAuth settings:

   • Redirect URL - Use the provided callback URL in your OAuth app settings
   • Authorization URL - Where users are sent to authorize access
   • Access Token URL - The endpoint for exchanging authorization codes for tokens
   • Client ID and Client Secret from your OAuth application
   • Scope - Define the permissions your integration needs
   • Authorization data location - Choose whether to send credentials in the request body or headers

4. Click through the authorization flow to connect

5. Census handles the token exchange and automatically includes the access token in your API requests

Get Started Today

Ready to sync to that OAuth-protected API you've been eyeing? Head to your Census workspace and create a new HTTP Request destination. The OAuth option is available immediately for all Census users.

While our implementation supports the most common OAuth patterns, there is a lot of variation between providers. If you have questions or need help setting up your first OAuth-enabled HTTP Request sync, our support team is ready to help at support@getcensus.com or via the in-app chat.

Happy syncing! 🚀

Improvement

You can now use user_alias as an identifier when syncing to Braze Cohorts.

Improvement

Our FullStory connector now supports Upsert behaviour. This uses FullStory's batch endpoints, so syncs should be significantly faster.

Improvement

We now support the Invoices object for our Planhat connector.

Improvement

Now you can use the Mailgun connector to send email directly, rather than having to add users to a mailing list and then trigger messages out-of-band. Email content can be included in the sync, or reference an existing Mailgun template to send more complex emails.

For more information on how to take advantage, see the Mailgun Connector documentation.

Improvement

We've made it easier to test your Google Ads syncs by now supporting validate_only mode for offline conversions. You can learn more about validate_only here.