Xtremepush

Datafly Signal delivers events to Xtremepush server-to-server using the External Event API (event hits). Each event can trigger a real-time Xtremepush campaign or workflow (email, push, SMS, web, in-app) and updates the matching user profile — with no client-side Xtremepush SDK in the page.

Why route Xtremepush through Datafly Signal

• Profiles are updated from the server, not the browser. Events reach Xtremepush even when a tracker blocker or a failed page unload would have dropped a client-side call, so the profile reflects what actually happened.
• Token lifecycle is handled for you. Signal obtains and refreshes the OAuth credentials Xtremepush requires, so nothing expires quietly in the middle of a campaign.
• One consent decision governs every destination. Xtremepush is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.

Prerequisites

Before configuring Xtremepush in Signal you need an active Xtremepush project and its App Token.

Configuration

Configure in Signal

datafly.identify("crm-12345", {
  email: "jane.doe@example.com",
  first_name: "Jane",
  last_name: "Doe",
  phone: "+44 7700 900123"
});

API Endpoint

POST https://api.eu.xtremepush.com/api/external/hit/event

(or https://api.us.xtremepush.com/... for US projects)

Authentication is carried in the request body as the apptoken field. Each event is sent as a single JSON object. Xtremepush returns {"success": true, "code": 200} on acceptance.

A higher-throughput batch endpoint (/api/external/hit/events, up to 1,000 events per request) is also available; contact Datafly support if you need batching enabled.

Identity Signals

Xtremepush matches events to user profiles using the external user_id. Additional profile traits ride along in user_attributes and update the profile before any triggered campaign fires.

Consent

consent_preferences is not set. It records communications permissions (email, SMS, WhatsApp opt-ins), and cookie consent must never set them; an unknown consent state would also have written 0, opting users out. Send it from your own preference centre if you need it.

Event Mapping

Signal uses GA4-style event names. The Default preset maps them to Xtremepush event names; everything else is dropped (defaults.action: drop).

The Retail preset adds remove_from_cart, order_shipped and refund. Currency is upper-cased; timestamp is Xtremepush’s 2024-12-13 11:36:00 +00:00 form. Every other event is dropped.

Example: Purchase event

Datafly.js call:

datafly.identify("crm-12345", { email: "jane.doe@example.com" });
 
datafly.track("purchase", {
  transaction_id: "ORD-001",
  value: 129.99,
  currency: "usd"
});

Xtremepush event hit sent by Signal:

{
  "apptoken": "YOUR_APP_TOKEN",
  "user_id": "crm-12345",
  "event": "purchase",
  "timestamp": "2026-06-06 11:36:00 +00:00",
  "user_attributes": {
    "email": "jane.doe@example.com"
  },
  "value": {
    "order_id": "ORD-001",
    "revenue": 129.99,
    "currency": "USD"
  }
}

Testing

1. In Signal, open the Event Debugger for your Xtremepush integration.
2. Trigger an event on your site (e.g. a purchase).
3. Confirm Signal received {"success": true, "code": 200} from Xtremepush.
4. In Xtremepush, open the user profile for the user_id you sent and confirm the event appears in the profile’s event/activity history.
5. If you have a campaign triggered by the event, confirm it fires.

Troubleshooting