Conversion Data

Once the integration with firebase is complete, the following steps can be followed to enable conversion data to be fed into Fast Track to provide you insight on such notifications.

ℹ️ Firebase Webhook Handler

The Firebase Webhook Handler accepts payload information from external users regarding Firebase push notifications.

The Firebase webhook handler provides an API endpoint that allows external users to send metadata headers and an action related to push notifications sent through Firebase. The endpoint supports Basic Authentication for secure communication.

The following implementation will be done within your app, which will send such data to FT notifying of the current status of the Push Notification sent to that device. As part of the firebase push notifications, Fast Track adds the properties to the Data property. Then for the conversion data, Fast Track expects to receive the following kind of payload on the POST endpoint in order to match to the original notification sent out.

The Firebase webhook handler expects payloads in the following structure:

{
  "action": "clicked",
  "metadata": {
    "conversion_fasttrack_triggerhash": "your_triggerhash_value",
    "conversion_fasttrack_id": "your_id_value",
    "conversion_fasttrack_activityid": 1,
    "conversion_fasttrack_actionid": 2,
    "conversion_fasttrack_actiongroupid": 3,
    "conversion_fasttrack_actioncommunicationprofileid": 4,
    "conversion_fasttrack_userid": 5,
    "conversion_fasttrack_playeroriginid": 6,
    "conversion_fasttrack_firebase_notification_type": "firebasepushandroid",
    "conversion_fasttrack_firebase_provider": "firebase"
  }
}

The allowed action values are:

• delivered

• read

• clicked

---

Endpoint

REST API

⬆️ POST https://brand.ft-crm.com/webhook/callback/firebase/

Important: Trailing / is required.

---

Authentication

Username: fasttrack

Password: provided during configuration

Only authorised users with valid Basic Authentication credentials can access the webhook endpoint securely.

---

✅ Success Response

HTTP/1.1 200 OK
Content-Type: application/json

{
  "message": "success"
}

❌ Error Response

HTTP/1.1 400 Bad Request
Content-Type: application/json

{
  "error": "invalid action value: invalid. Allowed actions: clicked, delivered, read"
}