CrowdPower Destination

CrowdPower is a growth marketing platform that enables businesses to track key customer actions and deliver automated tailored communications to drive sales and increase engagement.

This destination is maintained by CrowdPower. For any issues with the destination, please reach out to their team.


The CrowdPower Destination is currently in beta, which means that they are still actively developing the destination. If you are interested in joining their beta program or have any feedback to help improve the CrowdPower Destination and its documentation, please let their team know!

Getting Started

  1. From your Segment UI’s Destinations page click on “Add Destination”.
  2. Search for “CrowdPower” within the Destinations Catalog and confirm the Source you’d like to connect to.
  3. Drop in the API Key into your Segment Settings UI which you can find from your CrowdPower Project Settings.
  4. To find your CrowdPower API Key, go to the CrowdPower Console and click Settings in the sidebar menu. Use your CrowdPower project’s Public Key as the API key for Segment.


If you haven’t had a chance to review our spec, please take a look to understand what the Identify method does. An example call would look like:

analytics.identify('userId123', {
  name: 'John Doe',
  email: '',
  signed_up_at: 1583564043,

Identify calls in Segment create or update customers and their attributes in CrowdPower. Customer attributes may be used for creating segments. Your segments may be used as audiences for your marketing campaigns.

Date attributes should be sent as UNIX timestamps (UTC), and the keys should end in _at.


If you haven’t had a chance to review our spec, please take a look to understand what the Track method does. An example call would look like:

analytics.track('Purchased Item', {
    name: 'Cobb Salad',
    sku: 'ABC123',
    price: 1200,

Track calls in Segment create events for each customer in CrowdPower. Each event may have corresponding properties that may be used for creating customer segments and triggering marketing campaigns.

Date properties should be sent as UNIX timestamps (UTC), and the keys should end in _at.


To track customer revenue in CrowdPower, send the track event with the revenue key present.

analytics.track('New Charge', {
    revenue: 1200,

Track calls with the revenue key are treated as a charge in CrowdPower and do not appear in the customer’s event feed. The revenue is attributed to the customer, and the event name (and any other properties) are ignored.


You can send computed traits and audiences generated through Segment Personas to this destination as a user property. To learn more about Personas, reach out for a demo.

For user-property destinations, an identify call will be sent to the destination for each user being added and removed. The property name will be the snake_cased version of the audience name you provide with a true/false value. For example, when a user first completes an order in the last 30 days, we will send an identify call with the property order_completed_last_30days: true, and when this user no longer satisfies we will set that value to false.

When the audience is first created an identify call is sent for every user in the audience. Subsequent syncs will only send updates for those users which were added or removed since the last sync.


Segment lets you change these destination settings from your Segment dashboard without having to touch any code.


You can find your CrowdPower project’s public key on the settings page for your project.

This page was last modified: 12 Mar 2020

Get started with Segment

Segment is the easiest way to integrate your websites & mobile apps data to over 300 analytics and growth tools.
Create free account