Skip to main content
Census integration: user guide

Set up and use Census to send in data to Chameleon

Tiago Mota avatar
Written by Tiago Mota
Updated over a week ago

With our Census integration, you can send enriched data to Chameleon and leverage it when targeting, personalizing, and analyzing your Experiences. Ensure you have the right attributes to deliver contextual in-app Experiences to users.

You can set up Chameleon as a data destination in Census to create hyper-targeted Segments and deliver a better user experience.

Availability & Usage

๐Ÿ” Available for Growth, Enterprise

๐Ÿ“ Data ready to use in Tours, Tooltips, Embeddables, Microsurveys, Launchers

How does this integration work?

Census is a Reverse ETL platform that helps sync your warehouse data back to your tool stack so teams can easily use it to make better decisions and improve efforts.

Through Reverse ETL you can easily copy the data you have in your central warehouse to your tools (e.g. Twilio Segment, Salesforce, Zendesk, Mixpanel) and leverage it across other tools. Get enriched data that is combined from all your other tools, and leverage it in Chameleon.

Setting up the integration

You can leverage Census HTTP requests to send data to Chameleon and use it to create better product guidance. To configure this, you'll need to add an HTTP destination using an API key generated in Chameleon.

๐Ÿ‘‰ View your API tokens in your Dashboard or Learn more about the Chameleon API.

Create a destination

โถ In your Census dashboard navigate to "Destinations" and find the HTTP request option.

โท Next, fill in the details of your HTTP request. Name your destination and enter the Base URL for the Chameleon API (

โธ Generate a new API token in Chameleon and copy it to your clipboard.

โน Click to add a header, name the header X-Account-Secret , and paste in your token. You can also check the box indicating it's a secret --hiding it in our UI if you or anyone else attempts to edit this connection later on.

โบ Finally, click Connect.

Create your sync

Next, head over to the Sync section of your Census dashboard to add a sync between your warehouse data and Chameleon.

  • Pick your data warehouse or the source that contains the data you want to sync

  • Select the 'Chameleon HTTP Request destination' you created earlier

  • Add one of the following values for Specify a request endpoint

    • For Users, the endpoint is /v3/observe/hooks/profiles/batch

    • For Companies the endpoint is /v3/observe/hooks/companies/batch

  • Choose a trigger that you want Census to monitor in your source data (usually Records added or changed).

  • Select Multiple records per request and add 10,000 as the number of rows per batch.

  • Choose the User ID (ideal) or Email as the sync key in the next step

  • Pick the POST request method and pick the JSON payload type

  • Next, define your JSON payload with the Template editor and add one of the following "Templates".

    • Fill in the keys and values you want to sync to Chameleon

    • Include uid to match the User ID / Company ID passed to chmln.identify.

    Users (using the profiles key)

    "profiles": [
    {% for record in records %}
    "uid": "{{ record['ID']}}",
    "example_property_name_1": "{{ record['Example']}}"
    {% endfor %}

    Companies (using the companies key)

    "companies": [
    {% for record in records %}
    "uid": "{{ record['ID']}}",
    "example_property_name_1": "{{ record['Example']}}"
    {% endfor %}
  • Next, set the rate limit to 20 per minute.

  • Finally, test your sync and save it. You can check to see if your data was sent as expected, from the "API Inspector tab" in your sync configuration.

How to use it?

You'll find data sent through Census as filters when creating your audience in Chameleon. You can also leverage user properties to personalize the Experiences you create for a unique user experience.

This way you can connect valuable data across your tool stack and put it to work when guiding users in your product.

โ„น Ensure you are sending the same uid to both Census and Chameleon for your users to be identified correctly.

Did this answer your question?