Skip to main content

Transfer ownership

Overview​

The Game Transfer feature allows Organizations to migrate ownership of one or more Games between themselves. This administrative tool ensures that player insights, historical data, and unique identifiers like the game_key and secret_key remain intact during transitions such as studio acquisitions or publishing shifts. The process is governed by a secure connection protocol to ensure data integrity and compliance with privacy standards.

Workspace Hierarchy​

The platform is structured into four levels to manage data and access:

  • Organization: The highest entity representing the company. It manages billing, Users, and PipelineIQ services .
  • Studio: A sub-division within an Organization used to group Games by development teams or brands.
  • Game: The container for actual analytics data, dashboards, and event streams.
  • User: Individuals with specific permissions (Viewer, Admin, Owner) at the Organization, Studio, or Game level .

Connection Types​

Before a Game can be moved, a secure handshake must occur between the source and destination Organizations. This is managed through the Connections tab.

info

There are two types of connection statuses during the handshake

  • Incoming Connection: Held by the Organization that will receive future ownership of the Game.
  • Outgoing Connection: Held by the Organization currently owning the Game that must share/transfer it.

Implementation​

Following these steps ensures a secure transfer of Game assets between two connected Organizations.

Establish the Organization Connection​

The recipient Organization must first initiate a connection request to the current owner.

  1. Navigate to Organization settings.
  2. Select the Connections tab.
  3. Click Generate connection link to create a unique URL.
  4. Share the generated link with the administrator of the Organization that currently owns the Game.
  5. Once the current owner visits the link, return to the Connections tab and select Accept request.

Initiate the Game Transfer​

Once the connection is established, the current owner can initiate the transfer protocol.

  1. Navigate to your Organization's game list.
  2. Locate the Game you wish to move and select the vertical ellipsis (⋮) on the right side of the entry.
  3. Select the Transfer button.
  4. Select the Destination Organization from the list of connected entities.

Finalize Acceptance and Studio Assignment​

The future owner must conclude the process by accepting the Game and placing it within their hierarchy.

  1. Navigate to the Games list in the destination Organization.
  2. Locate the pending transfer request.
  3. Select Accept request.
  4. Select the specific Studio where the Game should be placed.
warning

Permissions do not carry over automatically. You must manually invite Users to the transferred Game or its new Studio after the process is complete.

Examples​

Scenario: Studio Acquisition​

Two Organizations, "Alpha Studios" and "Beta Publishing," want to transfer "Game X" from Alpha to Beta.

  • Beta Publishing (Future Owner) navigates to Organization settings > Connections and generates a link.
  • Alpha Studios (Current Owner) uses the link to establish the connection.
  • Beta Publishing accepts the Incoming Connection request.
  • Alpha Studios uses the vertical ellipsis (⋮) in their Games list to initiate the transfer of "Game X."
  • Beta Publishing accepts "Game X" and assigns it to their "Premium Titles" Studio.

Best Practices​

  • Audit Event Schema: Before transferring, ensure your events don't break count and cardinality limits, to avoid issues for the new owner.
  • Verify PipelineIQ Tiers: Ensure the destination Organization has an active PipelineIQ subscription if you need to preserve historical event-level data beyond 30-90 days.
  • Rotate API Keys: Post-transfer, update any external BI tools or scripts that utilize the Metrics API or Organization API to use the new Organization’s keys.
  • Update Attribution: If using Adjust or similar partners, update the KEY in the partner dashboard to ensure automated callbacks continue to flow to the new entity.