PushizoDocs
Analytics & data

Best channel

Calculates, from past deliveries, the channel each user responds to most. You use the result in two places: in audiences and in the Channel selection step of journeys.

Calculates, from past deliveries, the channel each user responds to most. You use the result in two places: in audiences and in the Channel selection step of journeys.

Enabling

Enable it from the Best Channel page in the dashboard or through the API. Scores are recalculated after saving and every night.

PUT /v1/apps/{appId}/channel-scores/config
Authorization: Bearer <admin-scoped key>

{ "enabled": true, "window_days": 90, "min_sends": 3, "count_email_opens": false }
FieldDefaultDescription
window_days90Delivery period taken into account (7–365 days)
min_sends3Minimum number of sends a channel needs before it gets a score (1–100)
count_email_opensfalseWhether email opens count as engagement

Disabling it deletes the scores.

How the score is calculated

  • Send: a delivery sent to the user.
  • Engagement: a delivery that was clicked or opened. Email opens are not counted by default, because Apple Mail Privacy Protection can generate opens without the user ever seeing the message.
  • Score: (engagement + 5 × channel rate) / (sends + 5). The channel rate is your app's overall rate on that channel. This keeps a channel with only a few sends from jumping ahead on its own.

Channels: Push (all push providers count as one channel), Email, WhatsApp, RCS, SMS. A delivery that falls back from RCS to SMS counts as SMS.

SMS has no open data: engagement only happens when a tracked link is clicked. That is why SMS scores may look low.

Using it in audiences

{ "all": [{ "field": "best_channel", "op": "in", "value": ["email", "sms"] }] }
FieldOperatorsValue
best_channeleq, neq, in, not_inpush, email, whatsapp, rcs, sms

The best channel is chosen from the channels through which the user is reachable at calculation time. A user without a score only matches neq and not_in.

Using it in journeys

The Channel selection step routes the user to a branch; it does not send a message itself. Add a send step with its own content to each branch. Preference and suppression rules are applied at the send step.

The selection is made when the step runs:

  1. Only the channels you selected in the step and that the user is subscribed to at that moment are candidates.
  2. The highest-scoring channel among those with a score is selected.
  3. If none of them has a score, the first channel in the step's order is selected.
  4. If there are no candidates, the user goes to the Unreachable branch.

The selected channel and its source (score or order) appear in the user's journey timeline.

Reports

EndpointScopeDescription
GET /v1/apps/{appId}/channel-scores/configanalytics:readSettings and calculation status
POST /v1/apps/{appId}/channel-scores/computeadminQueues a calculation
GET /v1/apps/{appId}/channel-scores/overviewanalytics:readDistribution per channel
GET /v1/apps/{appId}/channel-scores/usersusers:readUsers with a known best channel (channel, limit, cursor)
GET /v1/apps/{appId}/channel-scores/users/{userId}users:readA user's channel scores

On this page