Cordial's powerful real-time segmentation and personalization relies on the data you make available in the platform. As a developer, it's your job to get relevant data flowing into the platform to enable your marketing team to build dynamic, personalized messages for your customers.
API first and developer friendly
About the data
Cordial uses a document-based and search-based database to store all data in the following set of collections.
|Contact Collection||Stores data specific to a contact including channels, attributes, list membership and cart items.|
|Events (Contact Activities) Collection||Stores event data specific to messages (opens, clicks, etc.) or any custom named event.|
|Product Collection||Stores data from a product catalog. Typically developers will update this collection on a nightly or weekly basis. This data can be used to embellish an email, but is not used for audience search.|
|Orders Collection||Stores order data. This can hold specific order details and can be used for building an audience.|
|Supplements Collection||Stores additional data (store locations, coupon codes, message content, etc.) that doesn’t fit into one of the above collections.|
Watch the data overview video to learn more:
Cordial's API gives you access to virtually all of the platform's functionality, such as importing and exporting contacts, event, order, product, and message data—as well as sending batch and triggered messages and other job-related activities.
Here some recommended articles to get you started with our API:
In our documentation, API calls are grouped according to the following categories:
- Contact Management
- Orders, Products, and Supplements
- Message Creation and Delivery
- Operations Related
For testing and documentation needs, we built a custom implementation of Swagger to test all available API calls. Learn about using Swagger to access and test Cordial APIs here.
Cordial has two distinct API addresses, so it's important to check which one is associated with your account:
- For accounts located at HTTPS://admin.cordial.io/, the associated API URL is https://api.cordial.io/docs/v2/
- For accounts located at HTTPS://usw2.admin.cordial.io/, the associated API URL is https://api.usw2.cordial.io/docs/v2/
Recommended data integrations
Your industry and marketing strategy will determine how you collect and store data. We have some suggestions to help you get started.
- Contact attribute data: Contact data is paramount to any marketing strategy and can be passed to Cordial using the following methods:
- Contact activity events: Events (also referred to as contact activities) such as cart abandon and browse abandon are essential to triggered messaging strategies. They can be sent to Cordial using these methods:
- Cart items: Cordial stores cart items in the Contact Collection, and they can be used for populating message content in cart abandonment messages. Cart items can be passed two ways:
- Order data: You can use order data in the content of a message as well as to build an audience. Order data is used in replenishment campaigns, order surveys, and order confirmation messages—and can be sent two ways.
Note: When using order data to send confirmation messages, we recommend using the API method.
- Product data: Product data is used in message content and should be updated on a recurring basis to maintain a current catalog. You can do so:
Note: Product data is also updated in the Product Collection when passed along with order data.
- JSON validator: JSONLint is an awesome tool for checking your JSON for errors when making API calls. Sometimes it's just a misplaced comma that is causing the problem!
- HTML, JS, and JSON beautifier: jsbeautifier.org will beautify your code and make it easier to read.
- DNS lookup: whatsmydns.net/#NS checks the current IP address of your domain name and DNS record information against multiple name servers located in different parts of the world.
- Postman: An alternative to Swagger for testing API calls is Postman.