Working with Optimove and Amelco enables you to seamlessly implement Optimove integrations to get you up and running seamlessly.

This article provides an overview of features that can be supported by your Amelco integration and how to implement the integration.

Features Supported by Amelco Integration:

Our integration capabilities, supported by Amelco, include:

• Batch Data Processing: for casino and sports verticals
• Real-time Event Streaming: available via web SDK, mobile SDK, and server-side integration
• Mobile Channel Integration (formerly OptiMobile): including mobile push notifications and in-app channels/functionalities
• Web Channel (formerly OptiWeb): including the Web Push channel
• Promotional Integration: seamlessly incorporate promotional activities into your campaigns for Scheduled and Triggered Campaigns
• Optimove Personalize (formerly Opti-X)
• Transactional API: using Optimove transactional APIs to send transactional emails
• Preference Center API: using Optimove preference APIs to manage and maintain user permissions in real time
• Email consent (formerly OptiMail): via batch data and API

Batch Data Implementation

Data Delivery Method: Files, utilizing Optimove's SFTP

Integration Steps:

1. SFTP Setup: Optimove to create a dedicated SFTP environment. Please reach out to the project manager for the credentials.
2. Data Delivery & QA: Amelco to upload the data to the SFTP location. Optimove to pull the data and start the data QA phase.
3. ETL Setup: Amelco to automate the batch data process.

Once the data & ETL finalization milestone has been reached, the data will be ingested into Optimove for campaigns and segmentation.

For complete details of the process and timelines, please reach out to your dedicated project manager.

You can see the Data Schema here for detailed information on the data schema used in Batch Data Integration. This document provides a comprehensive overview of the data's structure and relationships to support your integration efforts.

Real-Time Implementation

Provide the following details for real-time event streaming:

• Tenant ID
• Tenant Token
• Server-side endpoint

These details will be provided by Optimove after submitting the Real-time prerequisite form.

Events Implemented in the First Phase:

As part of the initial implementation, the following events will be incorporated:

SDK Events:

• Page visit
• Login Success
• Casino Game Open
• Application Backgrounded
• Application Installed

Server-side Events:

• User Registration Complete
• User KYC Passed
• User KYC Started
• User Deposit Success
• Casino Bet Placed
• Casino Bet Settled
• Balance Update
• User Promo Opt In
• User Bonus Awarded
• User Bonus Clawback
• User Email Opt In Status Changed
• User Push Opt In Status Changed
• User Deposit Initiated
• User Withdrawal Started
• User Withdrawal Approved
• User Withdrawal Funds Released
• User Account Status Changed
• User RG Limits Set
• User Time Out Set
• Sports Bet Added to Betslip
• Sports Bet Placed
• Sports Bet Settled
• Sports Bet Voided
• Sports Bet Cashout
• Casino Game Session Complete
• User Account Closed
• User segment membership tier changed

Recommended use cases for the events above:

• Welcome journey
• Player balance drop
• Player deposit abandonment

Mobile Implementation

To configure the relevant mobile channels, provide the following details to Amelco:

• Mobile credentials
• Optimove credentials
• Specify which channels to set up

You can find these details on your site under Settings -> Mobile Push Configuration.

Amelco will also be able to access this information using their user account on your site.

Amelco will add the SDK initializer to the client apps on Android and iOS, plus plug in the Optimove keys. See the React Native docs: Optimove OptiMobile SDK Reference.

Web Channels

Amelco will follow these steps:

1. Integrate the Web SDK following this article: Web SDK Integration. The tenant ID and token will be provided by Optimove's CSE.
2. In order to integrate the Web Push channel, Amelco will have to add a script to the website's service worker, following this article: Service Worker.

Promo System Implementation

There are two parts to the bonus integration: bonus syncing and bonus awarding.

Bonus Syncing

To sync promotions, Amelco will generate an API key with ADMIN permission on your site.

Then, once a promo is generated in the WL engine, the promos will be synced to Optimove and will be visible in the campaign builder.

Bonus Awarding

Using the API key, Amelco will register a URL listener to scheduled campaigns (ET13) and triggered campaigns (ET11).

With any campaign execution, WL will receive the campaign details and customer list and award the promotions.

Optimove Personalize

Amelco will be responsible for data input and data output, meaning Amelco will be sharing the inventory and real-time data for Optimove Personalize.

Integration steps:

• Amelco will share their connection details for the inventory data.
• Amelco will share real-time events as per the requested Optimove Personalize modules.
• *Events required: please see the Real-Time Implementation section above.

Transactional API

If you are using an Email transactional account, you can leverage Amelco Logic to send automated transactional emails. The email templates will be created and managed directly in Optimove under the "Manage Templates" section. This setup ensures a seamless process for sending transactional emails, fully integrated with Optimove's capabilities and managed efficiently through Amelco Logic.

Integration Steps:

1. Configure your Transactional Account in Optimove.
2. Email Request: The client submits the Email request form to the Customer Success Engineer. Please provide the following info in the request:
   • Domain
   • Sender Email
   • Sender Name
   • Reply-To email
   • Spam email
3. Optimove Setup: The CSE allocates a new IP address within SendGrid and creates the necessary DNS records.
4. Client Implementation: Amelco implements the DNS records in their domain hosting provider.
5. Email Configuration by Optimove: the Email channel is added to the Optimove UI, and the DNS records are verified.
6. Build templates using the Visual or HTML Editor in the "Transactional" account type.
7. Use the TRANS: prefix for personalization tags.
8. Create an API key with Transactional permissions and share it with Amelco. Amelco will trigger emails via direct API calls from their backend.
9. Share with your CSM the personalization tags you intend to use in the templates, for example, FIRST_NAME, BALANCE, FORGOT_PASSWORD_URL, etc.

Preference Center API

Setting up the Multi-Channel Preference Center lets you provide customers with a seamless and personalized experience. Follow these steps to implement and configure the feature.

Integration steps:

1. Contact your Customer Success Engineer (CSE), who will handle the activation process for you. Once enabled, you'll be able to access all settings in the Preferences section of the platform.
2. Once your Brand Groups are established, you can begin configuring topics. Topics allow your customers to opt into the content they care about.

How to Add Topics (will be done by Amelco):

1. Navigate to Settings > General > Preference Center.
2. Add topics by defining their name, description, and associated Brand Group. Example topic: Formula 1 Updates.
3. Assign topics to communication templates (Email, SMS, Push, etc.).

In order to update a topic for a specific customer ID using the Preference Center API, you can use the following endpoint:

PATCH https://preference-center-{region}.optimove.net/api/v1/preferences

With the following details:

• Region: eu/us
• Tenant ID: should be provided by CSE/CSM

To load a single customer's preferences, use the following endpoint:

GET https://preference-center-{region}.optimove.net/api/v1/preferences

With the following details:

• Region: eu/us
• Tenant ID: should be provided by CSE/CSM

Consent Data Management

Amelco updates the Email consent field using these two methods:

• Batch data (for Email)
• API updates (for Email and SMS — formerly OptiText)

Batch Data

Amelco will include the most updated subscription status for every user by sending it through the batch data update. By doing that, Optimove's system will update the Email Unsubscribe attribute with the latest information once a day.

Amelco will adjust the batch data file to include the following attributes:

• Email address
• Timestamp — dd/mm/yy - hh:mm (time and date)
• Subscription status — Opt-in = true/false

API Updates

Amelco/WL use Optimove's API to update users with their subscription status for the Email and SMS channels once the consent changes appear on their side.

On a daily basis, Amelco scheduled jobs pull unsubscribe lists from Optimove (Email and SMS) and apply the change diff to the ATS DB.