GeoComply

Before Integration

Before integrating GeoComply into HUB2, it is important to receive answers from the licensee on the following questions:

1. Will players be able to play games on mobile and / or desktop?
2. If players will be able to play on desktop, whether the GeoComply solution used will be PLC or Solus?
3. If players will be able to play on mobile/tablet, whether the GeoComply solution used will be Oobee or Solus?
4. Regardless of the solution, when geofencing check should happen: right after login everywhere, on a certain page, or in a game wrapper?

Required Data for GeoComply solution

See below required fields for each GeoComply solution that HUB2 supports. These values need to be requested from GeoComply directly.

PLC

Ooobee

Solus

Integrate

In case it is required to perform Geofencing everywhere on the website, create a Tag in Tag Manager with the type GeoComply and Enable only requested integrations. Fill in the details of the integration as received from GeoComply team directly.

The tag should have the condition "On Application Initialisation". Save the tag, activate it and mark as "Ready for Production". After publishing the website, it should be ready to do geofencing.

In case it is required to perform Geofencing only on a certain page, then instead of "On Application Initialisation", use "On After Page Rendered" condition with a specific Page Condition that will mark only necessary pages.

It is important to know that for the wrapper (where Casino / POP games are launched), configuration for GeoComply requires it to be in another Tag. In case Casino / POP games are used on the project, create a copy of the previously created Tag and use "On Wrapper Initialisation" condition. Save the tag, activate it and mark as "Ready for Production". After publishing the website, it should be ready to do geofencing.