Articles on: Integrations

General guide to integrations with Icomm

At Icomm, integration is a fundamental part of enhancing and expanding the capabilities of the platform. Whether Natively, through API or SFTP, you can connect Icomm with a wide range of external systems, from CRM to e-commerce platforms. In this guide, we'll provide you with an overview of the options available to integrate with Icomm and how to make the most of these capabilities.

Integrations via SFTP



Integration via SFTP is a secure and reliable way to exchange data with Icomm. It is ideal for integrations that involve file transfer, such as database synchronization or information exchange with management systems.

With this option, you can make integrations compatible with various platforms, including CRM, content management systems, e-commerce platforms, and more.

Through SFTP files, it is possible to:

Omnichannel Integration
Data import

Native integrations



Icomm's platform offers a number of native integrations for e-commerce platforms. These integrations are designed to facilitate connection and data exchange between Icomm and the following platforms:

- Magento
- Shopify
- Fenicio
- Vtex
- Prestashop
-[Tokko](/en-us/article/how-to-integrate-with-tokko-in-icomm-18x8s1y/)
- Porta

These native integrations simplify the integration process and allow you to take full advantage of the capabilities of both platforms quickly and efficiently.

Omnichannel integration



Omnichannel integration is a service that allows Icomm to receive, import and process daily transactions and customers generated at physical and online points of sale, obtaining more than 75 indicators that can be used in dynamic segmentation and automation processes. This integration allows you to interconnect Icomm with any physical point of sale, e-commerce or platform intended to manage transactions and customers.

For more information about this integration, consult our guide: Omnichannel Integration Guide

Integration with Meta



The integration with Meta allows you to save records generated from "Lead Ads" type campaigns in a platform profile and generate a "Custom Audience" on Facebook based on a segment of users from the results section of the Icomm tool. This integration gives you the ability to take advantage of the data generated in your campaigns and use it effectively in your marketing strategies.

To know all the details about the integration, consult our guide: How to Integrate with Meta

##API

Icomm APIs provide a powerful way to integrate your platform with other systems and applications. Through APIs, you can perform different types of integrations to automate processes, exchange data and improve the efficiency of your operations. Some of the main APIs available are:

Main API: Allows you to work with contacts, profiles and results through an HTTP application programming interface.
Omnichannel API: Processes purchase orders generated at physical and online points of sale daily, obtaining more than 75 indicators for segmentation and automation.
Transactional API: Facilitates sending emails through Icomm, with operations, schemas and template syntax defined.
Survey API: Allows you to create and send professional forms, and analyze the results in real time.
Main Webhooks: They keep the status of your contact lists synchronized with your CRM, avoiding the need to constantly invoke the API to check for updates.

For more information on how to use these APIs, visit our: Icomm | Developers portal

Is it possible to have multiple integrations on the Icomm platform?



The platform allows you to have two or more integrations activated at the same time. However, depending on the case, the data can be merged or kept separate.

Therefore, it is important to keep in mind that the following integrations work with the same databases:

- Omnichannel
- API
- Magento
- Shopify
- Porta
- Fenicio

Integrations with Vtex and Prestashop are handled with independent databases.

This means that if a customer already has an integration from this group activated and wants to add another from the same set, but does not want the data to be mixed in the same profile, they must be integrated independently. That is, the data travels to separate profiles.

This is possible by assigning a unique customer identifier ("fake ID") for each integration.

For example, if the customer has Magento with ID 2350 and wants to add Omnichannel in another profile, they will be assigned a fake ID like -2350 for Omnichannel. In this way, the data from both integrations will be kept separate in different profiles linked to unique IDs.

Updated on: 04/30/2024

Was this article helpful?

Share your feedback

Cancel

Thank you!