Cordial Source

Ingest your event data from Cordial into RudderStack.

3 minute read

Cordial is a smart data platform for marketing teams. It lets you leverage AI to process real-time customer information and complex business data and deliver personalized content to users across various channels.

This guide will help you set up Cordial as a source in RudderStack.

Get started

Go to your RudderStack dashboard and click Add Source. From the list of Event Streams sources, select Cordial.
Assign a name to your source and click Continue.
Your Cordial source is now configured. Go to the Settings tab of the source and note the Webhook URL:

Log in to your Cordial dashboard and navigate to Integrations > Webhooks > New to create a webhook.
Click Edit in the Webhook Settings pane to configure the webhook.
In the Webhook Payload section, add the following schema:

{$payload = ['contact' => $contact, 'event' => $event]} 
{$utils->setPayload($payload)}

In the Request URL field, enter the webhook URL obtained in Step 3.

Further, you can choose to configure webhook triggers.

Event transformation

RudderStack ingests the events from Cordial as track events, after converting them into the appropriate event format. Cordial supports sending the single or batched request based on your webhook configuration.

Event mappings

RudderStack maps the following Cordial event types as is:

Email channel events
- open
- click
- optout
- bounce
SMS/MMS channel events
- message_sent
- click
REST channel events
- message_sent
Custom events
Mobile channel events
- crdl_notification_tap
- crdl_deep_link_open
- crdl_notification_delivered_in_foreground

It also maps some additional mobile channel events as shown:

Cordial event	RudderStack event
`crdl_app_install`	Application Installed
`crdl_app_open`	Application Opened

Property mappings

RudderStack maps the following Cordial properties from the event payload to the RudderStack fields:

Cordial property	RudderStack property
`event._id`	`properties.event_id`
`contact._id`	`context.traits.userId/userId`
`event.ts` `event.ats`	`timestamp` & `sentAt` & `originalTimestamp`
`event.d`	`context.device`
`contact.channels.email.address`	`context.traits.email`

How RudderStack creates the event payload

This section details how RudderStack receives the data from Cordial source and creates the resulting payload.

A sample payload sent by Cordial is shown below:

json

{
  "contact": {
    "_id": "6690fe3655e334d6270287b5",
    "channels": {
      "email": {
        "address": "alex@example.com",
        "subscribeStatus": "subscribed",
        "subscribedAt": "2024-07-12T09:58:14+0000"
      }
    },
    "createdAt": "2024-07-12T09:58:14+0000",
    "address": {
      "city": "San Diego"
    },
    "first_name": "Alex",
    "last_name": "Keener",
    "lastUpdateSource": "api",
    "lastModified": "2024-07-12T13:00:49+0000",
    "cID": "6690fe3655e334d6270287b5"
  },
  "event": {
    "_id": "669141857b8cc361ba0da2ef",
    "cID": "6690fe3655e334d6270287b5",
    "ts": "2024-07-12T14:45:25+00:00",
    "ats": "2024-07-12T14:45:25+0000",
    "d": {
      "type": "computer",
      "device": false,
      "platform": false,
      "browser": false,
      "robot": true
    },
    "a": "browse",
    "tzo": -7,
    "rl": "a",
    "UID": "4934ee07118197f93f74d5215b7b0076",
    "time": "2024-07-12T14:45:25+0000",
    "action": "browse",
    "bmID": "",
    "first": 0,
    "properties": {
      "category": "Games",
      "url": "http://example.com/games",
      "description": "A really cool game.",
      "price": 9.99,
      "title": "Monopoly",
      "test_key": "value"
    }
  }
}

RudderStack transforms the above payload into the following track payload: