Parameters goal
With the Parameters goal, you can use transmitted events as a condition for conversion.
This goal can be used for:
- Event analytics. Track user actions on your site to understand how visitors interact with the resource.
- Analysis of events. Track specific user actions in greater detail. For example, check which page elements are clicked most often and at what stages users abandon the checkout process.
- Setup and optimization of ad campaigns. For example, this can help you understand which ads lead to the desired actions on your site.
To learn more about passing events using the params method, see Transmitting events.
The Parameters goal is only triggered for parameters up to 2 KB in size (approximately 2048 characters). If a parameter is larger than 2 KB, the goal isn't completed.
During a single user session, the service can register up to 400 online conversions for a tag. When creating a Parameters goal, check in advance that the new goal won't exceed this limit.
Creating a goal
To create a goal:
-
In Yandex Metrica, go to the Goals page in the left menu.
-
Click Add goal.
-
Select the Parameters goal type.
-
In the Name field, enter a name for the goal to create.
-
Using the Attributes button, you can select which level parameters will be used to set up the goal and in what order.
-
In the input field, specify the conditions.
Use the
"."character to separate levels. To describe conditions, you can use the following characters:-
@— contains a string; -
~— a regular expression.
Example
If you've kept the standard order of parameters in the attributes, the condition can look like this:
param_1.param_2.param_3.param_4 -
-
Click Add goal. The created goal will appear in the list of goals. Yandex Metrica will start collecting statistics on it within a few minutes.
Yandex Metrica will track parameter combinations that contain the specified condition. This will be counted as a conversion.
Revenue transfer
To transmit revenue data along with the parameters, use the order_price and currency (a three-letter ISO 4217 currency code) attributes.
Example:
// Example of object transmission. Maximum nesting depth: 10 levels.
ym(XXXXXX, "params", {
order_price: "15000",
currency: "RUB",
level1_1: {
level2_1: {
level3_1: "example1",
level3_2: "example2",
},
...
level2_2: "example3"
}
})
Restrictions
-
A maximum of 200 goals can be set for each tag.
-
The service registers a user reaching the same goal on the same counter no more than once per second.
-
During a single user session, the service can register up to 1000 offline conversions and 400 online conversions created for the tag.
-
The size of a transmitted event parameter mustn't exceed 2 KB (approximately 2048 characters).
-
If you edit a tag or goal, the previously collected information won't change.
-
If you delete a goal, information collected for it will no longer be available in reports.
|
Useful links |
Online training |