IPv6 Support

Gamesight supports both IPv4 only and IPv4/IPv6 dual-stack depending on your game infrastructure. In this guide we will cover how you can get reliable attribution data in either networking stack configuration. Gamesight supports two different network architectures:

  • IPv4 Only (default) - In this configuration all trackers, events, and identifiers are recorded with IPv4 addresses. If your game's backend uses an IPv4 only architecture then you should use this configuration and provide IPv4 identifier values in your payloads.
  • IPv4/IPv6 Dual-stack - In this configuration the DNS server advertises both AAAA and A records to enable clients to select the IPv6 networking stack when it is available, falling back to IPv4 when it isn't. Under this configuration you will see a mixture of IPv6 and IPv4 values in the identifiers in your events.

It is critical that you have a consistent IP structure across your stack for fingerprint matching to attribute accurately. All of your events should either include dual-stack IPv4/IPv6 values or IPv4 only - but you shouldn't mix events reporting IPv4 only with dual-stack.

Dual-stack configuration

If you are on a dual-stack configuration please let your account manager know so we can configure your Game for IPv4/IPv6 dual-stack support.

If you are looking to migrate an existing Gamesight integration to dual-stack, there are a few steps to completing the rollout:

  1. Update game configuration - the first step is for your account manager to set your Game to dual-stack. This will update the domains that you use for click/impression tracking in addition to the Web SDK initialization snippet for your game. You can see these updated values under Management > In-Game Integration.
  2. Replace ad tags - update all integrated ad platforms with the updated click and impression tags for your Trackers. This will move the tags to dual-stack support.
  3. Update Web SDK integrations - if you have the Web SDK in place on your landing page, you will need to update the initialization code with the modified version available under Management > In-Game Integration.
  4. Update event payloads - update the network stack for your game backend so you have a mixture of IPv6 and IPv4 values passed to the /events endpoint.
  5. Complete E2E testing - finally, it is important that you complete end to end testing for your integration to ensure that all components are still function as intended. You can see the test steps in the Testing Your Game Integration guide.

That's it! You should now be ready to launch with your dual-stack networking.