Custom conversions new alpha

The custom conversions function enhances tracking capabilities of advertising campaigns, enabling you to track not only standard statuses (lead, sale, rejected, rebill), but also any other statuses necessary for a more accurate statistical analysis.

Features

1. Creating unique custom events, such as viewing specific pages, interacting with content, scrolling through pages, or using certain functions, opens up the possibility to tailor tracking to the unique goals and needs of each campaign, providing more accurate data for analysis, and optimization.

2. The ability to assign any names to conversions that match the action (for example, "Pricing page view," "Add to cart").

3. Specify one, two, or more parameters, upon which the event will be recorded in the metric when they are matched. Different parameters can be used to track a single conversion.

Functionality

1. Name

Field for entering the conversion name.

• When entering the name of a custom conversion in Latin characters, the name is automatically duplicated in the parameter values (spaces are taken into account and replaced with an underscore "_").

• To display the created custom conversion, use the metric settings, for example, in the "Campaigns" section.

The created custom conversion has two metrics: "conversion" and "conversion (revenue)." In "conversion (revenue)," similar to the "Revenue" metric, the revenue from incoming payouts is recorded in the payout= parameter in the postback. The 'conversion (revenue)' metric tracks only the revenue from the custom conversion. Metrics output in the report columns:

2. Parameter values

Field for entering the status value that must come in the status= parameter in the postback. It is allowed to specify one, two, or more values.

• When entering one or more values, they must be separated by a comma, for example: scroll, trash, second_deposit.

• All the values specified in the field will be used for recording in the custom conversion being created.

• You can track which value recorded the conversion in the "Original Status" metric in Reports > Conversions.

WARNING

Only Latin letters, underscores, and numbers are allowed for the value (for example, "scroll", "second_deposit", "deposit_1").

3. Checkboxes

• Include in conversions column (columns(metrics)) — Conversion events obtained through the created custom conversion can be included or excluded from the overall conversion statistics in the "Conversions" metric.

• Include in revenue column — Include or exclude the display of revenue from custom conversions in the "Revenue" metric.

• Send postback to traffic source — The ability to turn on or turn off sending a postback, specified in the traffic source (S2S Postback of the traffic source).

WARNING

Disabling metrics does not affect data collection; it only hides the display. Enabling metrics makes the data available for viewing again.

4. Tracking

Examples of use in tracker functionality that uses custom conversions.

• As with the field "2. Parameter Values", when entering the name of a custom conversion in Latin characters, this name is automatically duplicated in the value of the status parameter in the tracking methods.