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
All existing members on your platform must be transferred to your RMC account in bulk, and the update of newly added/updated members must continue. The purpose of database transfer is to create a member database on your RMC account. This member database will be used in marketing channels and automations such as email/mobile push/web push.
You can transfer your customer data to us via web service or data warehouse. Below are the documents with the necessary steps for both ways:

Member Integration with Web Service

While sending a member, you can first buy a service ticket with the Auth method (Login) and then send the members collectively with the Add Bulk method or one by one using the insert member demographic method.

Member Integration with Data Warehouse

If you have a customer table and you want to upload this table to RMC and feed it periodically, you can follow the steps in the document below. After you upload the customer table you have to RMC, you must inform us so that we can mark this table as the main table in the system.
(In addition to the incremental file upload method specified in the document to update your customer table, you can also use a web service. InsertUpdateRowInDwTable method allows you to add/update new records.)

WEB EVENT INTEGRATION

WHY IT IS NECESSARY
For Brands using RMC Recommend, RMC Segment and RMC Target modules; It is necessary to display recommended products in these environments or in marketing communications, to segment using visitor data, or to take actions such as displaying banners, pop-ups, in-app messages according to the behavior of visitors in web and mobile environments.

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
Required to transfer user information that allows web push notifications and to be able to send Web Push Notifications to these users.

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
We offer the most comprehensive integrated mobile marketing solutions compatible with iOS, Android and Huawei operating systems in the largest SDK network. You can transfer new users and member information changes in your mobile application, collect all your user’s behavioral data within the application, integrate many features such as push notifications, pop-up messages, surveys and gamification schemes into your mobile application in the most appropriate way to your brand identity, and create personalized customer experiences.
For mobile integration processes, you must first inform us of the SDK type you use in your application. We will also share the appropriate SDK documents with you.

OFFLINE DATA INTEGRATION

WHY IT IS NECESSARY
Required if historical or offline (eg. store) purchase or behavior data is to be transferred to RMC systems. It enables behavioral data such as past or offline purchases of your customers to be used when segmenting or creating product recommendations.
For offline data integration, we can upload purchasing or different behavior data to the system in the form of a csv file with the requirements specified in the document below.

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
With SMS integration, you can easily create, edit and send your SMS via the RMC Platform. You can use demographic information for personalization and offer different deals to all your customers with interesting personalized offers. Your SMS, Email and Push channels are integrated. You can send your SMS campaigns to your members in the database, and keep customer satisfaction at the highest level with the right communication frequency by sending fewer SMS to your users who make the necessary conversion via e-mail.

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.