Link markup for click verification

In order for clickable links prepared by verifiers to work correctly and for the VK Ads account statistics for campaigns under audit to take into account conversions on the targets of the VK Ads pixel associated with the account, you need to make additional adjustments.

For Adriver links to work correctly, it is necessary to pass the value of the {{clickid}} macro to the rb_clickid markup parameter of the landing page address, which must be properly wrapped in the AdRiver link. There are a number of configuration steps to do this.

Step 1
It is necessary to substitute a special macro into the markup parameter rb_clickid of the target url, which will get the value from the custom parameter of AdRiver. Such parameter is the ordinal custom, macro ![sdtN*]. Where N is the ordinal number, start with number 11.

In the source link we replace VK Advertising macros with verifier macros as a result the link that will be passed to the verifier will look like this.

The original markup of the target url:

A link that is installed in AdRiver:

Step 2

Next, you need to add the &custom=11= parameter to the AdRiver clickable link, and in this parameter, use ; to write macros from the original link (step 1), which should be passed to third-party analytics systems. Note the correspondence between the macro sequence number ![sdtN] and the sequence of macros in the custom parameter.

The reference that is issued by the verifier:

Final view of the verifier link:

AdRiver clickable links may use ev.adriver.ru and vr.adriver.ru in addition to using ad.adriver.ru.

Result

When clicking on the link, the parameters and macros of VK Ads will be passed to the custom=11= parameter, for example:

If a conversion is made, it will be associated with a specific click from VK Ads and will be logged in the Conversions metrics group in the statistics interface.

If you need to pass additional labels in the click link, you should use a unique macro for each of them. For example: std: ![sdt1], ![sdt2] and so on. All macros should be separated with semicolon.

For Weborama links to work correctly, it is necessary to pass the value of the {{clickid}} macro to the rb_clickid markup parameter of the landing page address, which must be properly wrapped in the Weborama link. This requires a number of configuration steps.

Initial markup of the target url:

We add the rb_clickid parameter with the {{clickid}} macro to the original markup of the target url and pass the link to the verifier.

The link that is set in Weborama:

It is necessary to inform the verifier to set up parameter and macro forwarding from the source link of the target url via the technical parameter a.ycp. When preparing the link, the verifier encodes characters such as "&" and "=" as a result, the final view of the verifier link will look like this.

Final view of the link produced by the verifier:

Result

When you click on the link via the a.ycp parameter, VK Ads parameters and macros will be passed, for example:

If a conversion is made, it will be associated with a specific click from VK Ads and will be logged in the Conversions metrics group in the statistics interface.

For Adserving links to work correctly, it is necessary to pass the value of the technical macro [LineID] to the markup parameters of the landing page address, which must be properly wrapped in the Adserving link. To do this, you need to perform a number of configuration steps.

Initial markup of the target url:

In the original markup of the target url, we add the rb_clickid parameter with the {{clickid}} macro.

The link that is set in Adserving:

It is necessary to inform the verifier to set up the parameters and macros from the source link of the target url via the technical parameter [LineID]. When preparing the link, the verifier encodes characters such as "&" and "=" as a result, the final view of the verifier link will look like this.

Final view of the link produced by the verifier:

Result

When click on the link, the parameters and macros of VK Ads will be passed to the technical macro [LineID], for example:

If a conversion is made, it will be associated with a specific click from VK Ads and will be logged in the Conversions metrics group in the statistics interface.