ChurnZero

Datafly Signal delivers events to ChurnZero server-to-server using ChurnZero’s analytics tracking API. Product-usage and lifecycle events captured by Datafly.js are forwarded to ChurnZero from your own infrastructure and attached to the right account and contact, feeding ChurnScores, Plays, journeys, and health scoring — with no client-side ChurnZero script on your pages.

Prerequisites

Before configuring ChurnZero in Signal, you need:

• A ChurnZero account with admin access.
• Your ChurnZero AppKey (found in Admin > AppKey).
• Knowledge of which ChurnZero region your instance runs in (US or Europe/Asia).
• A stable account external ID for each customer account, matching the identifier you use in your CRM. ChurnZero attaches every event to an account using this value.

Configuration

Configuration Fields

Configure in Signal

API Endpoint

ChurnZero’s tracking API accepts every write as an HTTP GET with all fields in the URL query string. Signal sends one request per event:

GET https://analytics.churnzero.net/i?appKey={app_key}&action=trackEvent
    &accountExternalId={account}&contactExternalId={contact}
    &eventName={event}&eventDate={iso8601}

For Europe/Asia accounts the host is eu1analytics.churnzero.net. The path is always /i and the action is always trackEvent.

Identity Signals

ChurnZero keys every event on the (accountExternalId, contactExternalId) composite. There is no hashing, fingerprinting, or device identity — matching depends entirely on the external IDs you supply.

Call datafly.identify() when a user logs in or is otherwise known, passing the account identifier and the contact’s email:

datafly.identify("user-123", {
  email: "jane.doe@acme.example",
  account_external_id: "ACME-CRM-0042"
});

Event Mapping

The SaaS / Customer Success preset maps Signal events to ChurnZero events:

All other events are dropped. To track additional events, add them to the integration’s Field Mappings in the Management UI.

Example: Feature Used event

Datafly.js call:

datafly.identify("user-123", {
  email: "jane.doe@acme.example",
  account_external_id: "ACME-CRM-0042"
});
 
datafly.track("Feature Used", {
  feature_name: "Export to CSV",
  count: 1
});

Request sent by Signal:

GET https://analytics.churnzero.net/i
    ?appKey=YOUR_APP_KEY
    &action=trackEvent
    &accountExternalId=ACME-CRM-0042
    &contactExternalId=jane.doe%40acme.example
    &eventName=Feature%20Used
    &eventDate=2026-06-06T10:32:00Z
    &description=Export%20to%20CSV
    &quantity=1

Testing

1. Trigger an identified event on your site (for example, log in then use a tracked feature).
2. In Signal’s Event Debugger, confirm the event was delivered to ChurnZero with a 200 response and that accountExternalId, contactExternalId, and eventName are populated.
3. In ChurnZero, open the matching Account and check the contact’s activity timeline — the event should appear within a minute, with the eventName you mapped.

Troubleshooting