ComRaidComRaid Docs

Notification attribution

Attribute opens and delivery outcomes.

ComRaid injects stable IDs into push data payloads so your product can join acknowledgements and conversions to the original Notification.

Not the same as contact attributes

Contact attributes describe Contact state for targeting (plan, region, stage). Notification attribution identifies a specific send touchpoint after delivery. Keep targeting keys on the Contact; store cr_* IDs on your own conversion or analytics rows.

Injected payload keys

Before send, ComRaid adds attribution identifiers to the FCM/APNs data payload. All ComRaid keys use the cr_ prefix so they never collide with your product data keys.

{
  "cr_message_id": "9bc6a840-1f5d-49a7-bd1b-3f0d3a5cf2e7",
  "cr_message_recipient_id": "2c83e5a4-3974-45e7-a87d-9f3686a3db05",
  "cr_delivery_id": "6dc94971-a413-44db-b79d-87fd1ce2f8cf",
  "cr_attribution_token": "opaque_signed_or_random_token"
}
  • cr_message_id — logical Message (push Notification).
  • cr_message_recipient_id — per-Contact recipient on Broadcasts; omitted for simple Single sends that only set the Message contact_id.
  • cr_delivery_id — per-Endpoint Delivery attempt.
  • cr_attribution_token — opaque token for Delivery acknowledgements and product joins.

Android FCM payloads never include a system notification block. Every Android Notification is a data message; the Android SDK presents non–Data-only alerts and injects display helpers:

  • cr_title, cr_body, optional cr_image_url / cr_android_channel_id
  • cr_actions — JSON string of [{ "id", "text", "icon?" }]
  • optional cr_sound, cr_subtitle, cr_badge (integer as a string), cr_thread_id, and cr_priority (normal only; absent means high)
  • cr_data_only — "true" for a Data-only Notification (never auto-shown)

APNs alert Notifications keep presentation in aps (sound, subtitle, badge, thread-id). APNs Data-only payloads carry the same cr_* presentation hints except cr_priority / cr_android_channel_id. Alert APNs always sets mutable-content so a Notification Service Extension can ack delivered.

First-class content.push.deep_link is delivered as cr_deep_link in the same FCM/APNs data payload (alongside attribution keys). Apps read it on open to navigate; ComRaid does not auto-route.

See React Native SDK for displaying those buttons and Acknowledgements for recording which button was tapped.

Product-owned conversions

ComRaid does not store purchases, subscriptions, or revenue events. Your product backend should persist attribution references on its own conversion rows:

push delivered
  -> app preserves cr_* attribution IDs
  -> user converts (purchase, signup, …)
  -> product backend stores conversion + ComRaid IDs
  -> product reports conversions against the original touchpoint

Use attribution IDs for analytics you own. Use delivery acknowledgements (POST /deliveries/{id}/delivered and /opened) for delivered/opened communication metrics and optional per-button click counts inside ComRaid — see Acknowledgements.

On this page