EN RU
Pricing Blog

# Release 11.1 alpha

Release 11.1 introduces navigation improvements, flexible click uniqueness configuration, and simplified integration workflows.

# New menu structure

We’ve moved the settings from the top right corner to the sidebar and split them into two sections:

  • Settings — a section for configuring the system and interface. This includes everything that changes the tracker’s behavior but does not relate to maintenance or debugging.
  • Maintenance — a section for technical and service operations. Here you’ll find tools to help maintain the system, analyze issues, and manage data.

We’ve also placed commonly used items at the top level of the menu:

  • Users — user management.
  • Integrations — integrations with external services.

Now everything important is visible and just one click away.

# Uniqueness by parameter in campaigns

Campaign settings now include a new way to determine uniqueness — by parameter. You can now specify a GET parameter (for example, external_id) that the system will use to treat clicks as belonging to the same user, even if:

  • IP addresses are different;
  • Cookies are missing or have been cleared.

How it works:

  1. In the Uniqueness settings, select the new option — Parameter.
  2. Enter the name of the GET parameter.
  3. The user session will be restored based on the value of this parameter within the specified Uniqueness TTL.

In traffic logs, you’ll see entries like:

  1. First click: no sessionId by parameter external_id: "xxxxx".
  2. Repeat click: found session by parameter external_id: "xxxxx" → Found sessionId "xxxxxxxxxxxxx".

This method is useful when a single user may land on different flows or offers within one campaign, and uniqueness is determined not by IP, or cookies, but by a specific identifier in the request.

# Facebook integration: separate connections for sending conversions and receiving costs

The Facebook integration is now available in two separate modes:

  • Costs — transfers cost data.
  • Conversions — transfers conversion data.

Previously, using the conversions integration required having an active costs integration. This dependency has now been removed — you can create and use the conversions integration independently.

This simplifies setup and provides more flexibility: you can connect only what’s needed for your specific workflow.

← Glossary →