Integration Developer Guide
Integrate with Related Marketing Cloud Platform Easily and Quickly!
Here, you can find the integration details and documents of the features you can use on a single platform.
Member Integration | Product Integration | Web Event Integration | Web Push Integration | SDK | API Integration | Offline Data Integration | Sms Integration | |
---|---|---|---|---|---|---|---|---|
Bulk Email | ||||||||
Email Reco | ||||||||
Transactional Email | ||||||||
Web Push | ||||||||
Segment | ||||||||
Target | ||||||||
Web Reco | ||||||||
Mobil App | ||||||||
Offline Data | ||||||||
SMS |
MEMBER INTEGRATION
WHY IT IS NECESSARY
Member Integration with Web Service
Member Integration with Data Warehouse
WEB EVENT INTEGRATION
WHY IT IS NECESSARY
Event integration on your website can be completed in 2 different ways (Integration with GTM and Direct Integration). If you are using GTM, we can check the data layer for your site, and if your site’s Data Layer is suitable for integration, our team can complete the integration on your behalf if you authorize visilabs.analytics@euromsg.com to edit in GTM. You can complete the integration yourself, as described in the documents, by any method you wish.
Please find the documents below
PRODUCT INTEGRATION
WHY IT IS NECESSARY
For Brands using RMC Recommend, RMC Segment and RMC Target modules; It is necessary in order to display recommended products in these environments or in marketing communications according to the behavior of visitors in web and mobile environments, to segment using product data or to take actions such as displaying banners, pop-ups, in-app messages.
It is mandatory for the RMC Recommend module and optional for RMC Segment and RMC Target module. Can be decided according to the scenarios.
If you have a ready XML file for integration (it can also be Google Feed XML), you can send it first. Together with its control, we can define it to the system if there are no deficiencies.
In addition, you can send xml in single or multi-language (currency, etc.) format according to the following documents.
WEB PUSH INTEGRATION
WHY IT IS NECESSARY
For Web Push integration, you must first define a Push Application for your website on the RMC panel. If the necessary adjustments are made and the update is attempted, you need to place the worker file (relatedpush_sw.js) in the root folder of your site and the script on all the pages you want to collect permissions from..
Please find the documents below
MOBIL INTEGRATION
WHY IT IS NECESSARY
OFFLINE DATA INTEGRATION
WHY IT IS NECESSARY
TRANSACTIONAL EMAIL INTEGRATION
WHY IT IS NECESSARY
With Transactional email web services, you can send informational messages such as password reminder, membership activation, your order is in the cargo, and get the results of these for analysis.
Integration to each service is required for e-mail, SMS and push sending.
To start the transactional email integration of your account, we need to create an API user for you. Please share which e-mail address you want us to forward the API user information.
Please find the documents below
SMS INTEGRATION
WHY IT IS NECESSARY
For Sms integration, you must first provide us with the brand you are working with as an SMS Provider and the “username, password, originator, opt-out keyword” information that will be required within the processes.
SMS permission management processes are required to be managed with your SMS Provider. Your SMS Provider will require İYS Code and İYS Brand Code within our integration. Please share your IYS code and IYS Brand Code with the required information above.