Introduction to Integrations

Bisko offers the possibility to send segments to third party services, so these segments can be used for targeting or other purposes specific to these services, via its out of the box integrations.

Each third party service has some required properties that should be filled in order for that integration to be activated, so an account with the specific third party service should be created if it doesn't already exist.

Name is a required property for every integration. The name should make an integration easy to find. It is possible to create multiple integrations with the same name and type.

AccountID is required to activate an integration with Gjirafa AdNetwork. This is the unique identifier for the Gjirafa AdNetwork account.

  1. Gjirafa AdNetwork Integration

AccountID is required to activate an integration with Integr8 AdNetwork. This is the unique identifier for the Integr8 AdNetwork account.

  1. Integr8 AdNetwork Integration

AccountID is required to activate an integration with MallTv AdNetwork. This is the unique identifier for the MallTv AdNetwork account.

  1. MallTv AdNetwork Integration

  1. Tonos Integration

  • OrganizationPublicId is a required property to activate an integration with GjirafaTech Tonos. This is the unique identifier for the GjirafaTech Tonos organization.

  • ApplicationPublicId is an optional field that can be provided when activating an integration with GjirafaTech Tonos, if the integration needs to be in application level. This is the unique identifier for an application within a GjirafaTech Tonos organization.

  1. Google AdManager Integration

  • NetworkCode is a required property to activate an integration with Google AdManager. This is the is a unique, numeric identifier for the Ad Manager network.

  • ApplicationName is an optional field that can be provided when activating an integration with GAM. This can help identify the application, in this case Bisko, connecting to the Ad manager network.