Optimove’s integration with GiG offers flexible options for ingesting batch and real-time data, managing promotions, and coordinating email delivery. This article outlines the supported integration points and provides setup instructions for each capability.

Features Supported by GiG Integration

GiG supports a variety of integration points that allow Optimove to ingest and act on customer data in real-time or through scheduled processes:

Batch Data Integration:
- SQL connectivity (DB replica) – Casino, Sweepstakes, and Sports verticals.
- GiG broker (Kafka) - for clients that don’t have SQL connectivity.
  - In this option, historical data and customer data will be shared with CSV files through Optimove’s SFTP.
  - Currently, only Casino integration has been done end-to-end for the GiG broker. That will affect data QA timelines for other verticals.
- Please note: sports data does not include bet details data, which will affect the product history.
Promotional Integration:
Note:
Email Consent Management: Sync opt-in/out preferences*.
Email Transactional Emails: Trigger transactional messages*.
Streaming Data Integration: Real-time data ingestion*.
Web Channel Integration: Web Push and Web Page Pop Up.

Features marked with * are supported only for LogicX clients.

Important Note:
The Optimove Customer ID (CID) will follow this format: tenantID_playerID. GiG will use this as the CID across all the integrations listed above. Please note that for batch data, stitching will be handled by Optimove.

Batch Data Integration (DB Replica)

GiG provides two batch data integration methods: direct SQL access via ClickHouse (recommended) or event-based batch ingestion via Kafka (for clients that don’t have SQL connectivity). Both options enable scalable data ingestion into Optimove for segmentation and campaign use.

Option 1: SQL Connectivity (ClickHouse DB)

This is the most recommended method for clients who have direct SQL connectivity to their data.

Integration Steps:

Database Access: GiG shares database credentials and whitelists Optimove’s IP addresses.
- Required: Endpoint, Username, Password
Data QA: Optimove pulls the data and performs QA checks.
ETL Finalization: GiG’s DB is updated in real-time. Once data is finalized, Optimove builds the ETL, maps the data, and creates the pipeline to ingest the data.

For full process details and timelines, please contact your project manager.

Option 2: GiG Broker (Kafka-Based Batch)

Clients without SQL access can use Kafka to deliver data events, which Optimove transforms into batch data.

Supported Topics:

customer_detail_{tenant_id}_v1
enriched_game_{tenant_id}_v1
enriched_game_detail_{tenant_id}_v1
enriched_sport_{tenant_id}_v1
enriched_payment_{tenant_id}_v1
enriched_bonus_{tenant_id}_v1
enriched_customer_{tenant_id}_v1
enriched_sweepstake_transaction_{tenant_id}_v1

Note: Customer Detail and Enriched Customer topics data is already sent to Optimove via SFTP - So these can be ignored.

The enriched_bonus topic contains data for both sports and casino bonuses. Use the product_id field to determine the type: 1 for casino and 2 for sports.

Topics per vertical:

Sweepstakes

customer_detail_{tenant_id}_v1

enriched_customer_{tenant_id}_v1

enriched_game_detail_{tenant_id}_v1

enriched_payment_{tenant_id}_v1

enriched_sweepstake_transaction_{tenant_id}_v1

Sport & Casino

customer_detail_{tenant_id}_v1

enriched_customer_{tenant_id}_v1

enriched_game_{tenant_id}_v1

enriched_game_detail_{tenant_id}_v1

enriched_sport_{tenant_id}_v1

enriched_payment_{tenant_id}_v1

enriched_bonus_{tenant_id}_v1

Casino

customer_detail_{tenant_id}_v1

enriched_customer_{tenant_id}_v1

enriched_game_{tenant_id}_v1

enriched_game_detail_{tenant_id}_v1

enriched_payment_{tenant_id}_v1

enriched_bonus_{tenant_id}_v1

Sport

customer_detail_{tenant_id}_v1

enriched_customer_{tenant_id}_v1

enriched_sport_{tenant_id}_v1

enriched_payment_{tenant_id}_v1

enriched_bonus_{tenant_id}_v1

Integration Steps:

Kafka Setup
- GiG shares tenant ID and confirms the Kafka topics are active.
- Optimove sets up the connection and consumes data from those topics.
Historical Data & Customers Files Delivery
- SFTP Set Up: Optimove provides SFTP credentials.
- GiG shares the historical data as CSV files following the same structure as the streaming events. (Payment data will be shared at the transactional level.)
- GiG shares customers via the SFTP environment daily.
Data QA
- Optimove will transform the data and start the data QA phase.
- Once the data finalization milestone has been reached, the data will be ingested into Optimove for campaigns and segmentation.

For full process details and timelines, please contact your project manager.

Multi-brand supported: each brand uses separate Kafka topics and a unique brand/tenant ID on GiG's end.

Promo Integration

Optimove's integration with GiG now supports two distinct platform options. Please select the integration relevant to you below:

CoreX Platform Integration (Promotions)

Optimove’s integration with CoreX (Promotions (formerly OptiPromo)) supports Tags, Bonuses, Free Spins, and Free Bets for both scheduled and real-time campaigns.

Key Points

Works for scheduled and real-time (conditional execution) campaigns.
Supports four promotion types: Tags, Bonuses, Free Spins, and Free Bets.
Ensures campaigns are sent only to players who were successfully assigned a promotion in GiG’s system.
Real-time execution is handled through GiG’s OptiPromo APIs.
Automatically filters out failed assignments, so no players receive campaigns without a valid promotion.
In a single campaign, it’s possible to select multiple bonuses. However, if one or more bonuses fail to be successfully assigned, Optimove will not send the campaign to that player.

You can view all promotions created in GiG directly in the Optimove UI under OptiPromo. Promotions are synced on a scheduled basis.

Promotions 1.png

Assigning Promotions

Promotion Type	Required Attributes	Notes
Tag	`tag_id`, `tag_id_duration`	`tag_id_duration` defines when to untag users. If it’s empty, Optimove will automatically untag users based on the campaign duration.
Bonus	`bonus_template_id`, `bonus_amount`	Amount can currently only be fixed (defined by the user).
Free Spin / Free Bet	`freespin_template_id`, `freebet_template_id`	All templates can be viewed directly in the OptiPromo UI within Optimove.

To update or review a promotion’s metadata, click Edit next to the promotion. The relevant fields (like tag_id and tag_id_duration) will appear under Meta Data:

Promotions 2.png

How It Works

Open Your Promotions: Go to Plan → OptiPromo → Promotions to view all promotions synced from GiG.
Edit Metadata (If Needed): Click Edit on the relevant promotion and update fields such as tag_id, tag_id_duration, or template IDs.
Activate Promotion: After making your updates, activate the promotion. Promotions will only appear in the Optimove campaign builder once they are activated.
Create a Campaign: In the campaign setup, select the activated promotion and enable Conditional Execution to ensure only players with a successfully assigned promotion receive the campaign.
Execution: Optimove sends the promotion request to GiG, waits for confirmation, and then sends the campaign only to successful players.

Important Notes:

The integration automatically handles untagging based on the tag_id_duration attribute.
If no duration is provided, untagging will occur after the campaign duration ends.
Failed promotion assignments are excluded from campaign delivery.
Promotions and templates are auto-synced from GiG to Optimove.
OBJECT_TAG_ALREADY_EXISTS --> If you try to assign the same tag to the same user Optimove will receive this error and therefore it will be ignored.
Retry Mechanism --> Optimove's retry mechanism is disabled for this step of the GIG integration. If Optimove is unable to assign promotions we will skip this user and won't retry

Core Platform Integration

One of the most valuable integrations available between GiG and Optimove is the ability to synchronize Tags from GiG directly into Optimove. This allows you to utilize Optimove’s advanced segmentation and campaign orchestration to tag players within GiG's Bonus Engine.

Key Benefits:

Works for scheduled conditional execution campaigns.
Automatically sync tags across both platforms, ensuring consistency and accuracy.

Integration Steps:

To set up Promo Integration between GiG and Optimove, follow these steps:

Initial Configuration with Your Customer Solution Engineer

Provide the following details to your assigned Customer Solution Engineer:
- List of Brands: Specify the brands you want to integrate with.
- API URLs to Retrieve Tags: For each brand, provide the specific API endpoint used to fetch available tags from GiG’s Bonus Engine.
- API URLs to Tag Players: For each brand, provide the specific API endpoint used to apply tags to players in GiG’s platform.

How it works: Tag Synchronization

Tags are synchronized between GiG and Optimove on an hourly basis. During this process, Optimove's Tag Synchronization Module retrieves the latest tags from GiG and updates them in Optimove. The module checks for any new, modified, or deleted tags and then calls the Optimove API to add, update, or remove corresponding promotions as needed. This ensures that the most current set of tags is always available for your campaign targeting.

Naming Convention

To ensure seamless mapping between GiG's tags and Optimove’s promotions, the following naming convention is used:

Optimove Promo Name: BrandName_TagName
Optimove Promo Code: BrandName_TagID

Scheduled Campaign Execution

To tag players in scheduled campaigns using the GiG-Optimove integration, follow these steps:

Create a Campaign: Set up your campaign in Optimove as you normally would, defining your target audience.
Configure Tagging in Execution Details: In the Execution Details section of the campaign setup, select the desired tag from the drop-down menu. Enable the Conditional Execution toggle to ensure that only players successfully tagged in GiG’s Bonus Engine will be eligible to receive the campaign.

Limitations / Important Notes

Core Platform: This integration is only valid for clients on Core Platform and not CoreX.
Tagging Success Requirement: Only customers who are successfully tagged in GiG’s Bonus Engine will receive the campaign. The final list of targeted customers can be found under the "Targeted Customers" tab in Optimove mission control.
Single Tag Recommendation: If multiple tags are selected in the campaign's action, Optimove will attempt to tag the player with each selected tag. However, it will randomly decide whether to send the campaign based on the tagging result. To ensure predictable campaign execution, it is advised to use only one tag per action.

Email Consent Management

If you are using Email and have a platform where users can opt in or opt out of communications, GiG can seamlessly update Email's consent management system using the Optimove API. This integration ensures that user consent preferences are always accurately updated.

Integration Steps:

Create an API key with Admin access and share it with GiG.
Ask your CSM to provide a list of Brand IDs to be used for the integration.

Email Transactional Emails

If you are using an Email transactional account, you can leverage GiG Logic to send automated transactional emails. 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 GiG Logic.

Integration Steps:

Configure your Transactional Account in Optimove.
Create an API key with Transactional permissions and share it with GiG.

Streaming Data Integration

GiG has developed the streaming data integration via LogicX. This integration captures immediate customer actions (e.g., purchases, logins) to enable instant updates, trigger campaigns, and enhance dynamic, timely responses. The full guide can be found at this link.

Web Channel Integration: Web Push and Web Page Pop-Up

For clients using Web and a GiG-managed front-end, there is an additional integration option to enable Web Push and Web Page Pop-Up.

Integration Steps:

The client must submit a request form to enable the integration. This will trigger the onboarding process from the Optimove side.
After the onboarding process, provide the Tenant Token and Tenant ID to your GiG point of contact.

Features Supported by GiG Integration

Batch Data Integration (DB Replica)

Option 1: SQL Connectivity (ClickHouse DB)

Option 2: GiG Broker (Kafka-Based Batch)

Supported Topics:

Topics per vertical:

Sweepstakes

Sport & Casino

Casino

Sport

Integration Steps:

Promo Integration

CoreX Platform Integration (Promotions)

Core Platform Integration

Email Consent Management

Email Transactional Emails

Streaming Data Integration

Web Channel Integration: Web Push and Web Page Pop-Up

Related articles