Download clickworker - Revision history

Admin: Marked this version for translation

2024-04-19T16:39:34Z

Marked this version for translation

← Older revision		Revision as of 16:39, 19 April 2024
Line 4:		Line 4:
	By default, to verify click-through links for [[Meta redirect\|Meta Redirect-type integrations]], we use a ''clickworker'', a special page on the Kaminari Click domain, which checks the user and then redirects good users to the target link, and bots to [[Traffic back URL\|traffic-back URL]], if the corresponding option is enabled. This approach is as simple and convenient as possible, but has a number of disadvantages.		By default, to verify click-through links for [[Meta redirect\|Meta Redirect-type integrations]], we use a ''clickworker'', a special page on the Kaminari Click domain, which checks the user and then redirects good users to the target link, and bots to [[Traffic back URL\|traffic-back URL]], if the corresponding option is enabled. This approach is as simple and convenient as possible, but has a number of disadvantages.

			<!--T:15-->
	# If suddenly a technical problem occurs on our server, the redirect breaks down and your traffic will be lost.		# If suddenly a technical problem occurs on our server, the redirect breaks down and your traffic will be lost.
	# Redirects between different sites are slower than within one site, so a redirect through our clickworker can increase the percentage of non-revenue to the target link.		# Redirects between different sites are slower than within one site, so a redirect through our clickworker can increase the percentage of non-revenue to the target link.
Line 36:		Line 37:
	When delivering the clickworker to the user, you can dynamically replace the templates with current data.		When delivering the clickworker to the user, you can dynamically replace the templates with current data.

			<!--T:10-->
	== Templates description ==		== Templates description ==
	~~<!--T:10-->~~
	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-
Line 82:		Line 83:
	</pre>		</pre>

	<!--T:14-->		= Example implementation = <!--T:14-->
	~~= Example implementation =~~

			<!--T:16-->
	Below is an example of the simplest implementation of a clickworker on your side using PHP.		Below is an example of the simplest implementation of a clickworker on your side using PHP.

			<!--T:17-->
	Let's say that you own a website '''my-site.com''' and people come to you through links like this:		Let's say that you own a website '''my-site.com''' and people come to you through links like this:
	<pre>https://my-site.com/click.php?utm_source=1&utm_campaign=123&utm_click_id=93652664834&target=https%3A%2F%2Fgoogle.com</pre>		<pre>https://my-site.com/click.php?utm_source=1&utm_campaign=123&utm_click_id=93652664834&target=https%3A%2F%2Fgoogle.com</pre>
	And you want Kaminari Click to check the user for fraud and redirect to the target link (in this case, google).		And you want Kaminari Click to check the user for fraud and redirect to the target link (in this case, google).

			<!--T:18-->
	== Making a link ==		== Making a link ==
	You decided that you will take the data directly from the GET parameters and that ''utm_source'' will be written in '''sub1''', ''utm_campaign'' in '''sub2''' and ''utm_click_id'' in '''sub3'''.		You decided that you will take the data directly from the GET parameters and that ''utm_source'' will be written in '''sub1''', ''utm_campaign'' in '''sub2''' and ''utm_click_id'' in '''sub3'''.

			<!--T:19-->
	Next, in your integration settings you need to copy the link for clickworker downloading and replace the templates you need, that is, {sub1}, {sub2}, {sub3}, {clickUrl}, the rest can be deleted.		Next, in your integration settings you need to copy the link for clickworker downloading and replace the templates you need, that is, {sub1}, {sub2}, {sub3}, {clickUrl}, the rest can be deleted.

			<!--T:20-->
	[[File:Clickworker-link.png]]		[[File:Clickworker-link.png]]

			<!--T:21-->
	As a result, you will get a link like this:		As a result, you will get a link like this:
	<pre>https://kaminari.space/v1/click?kmnrKey=XXXXXXXXX&sub1=<?=$_GET['utm_source']?>&sub2=<?=$_GET['utm_campaign']?>&sub3=<?=$_GET['utm_source_id']?>&u=<?=$_GET['target']?>&download</pre>		<pre>https://kaminari.space/v1/click?kmnrKey=XXXXXXXXX&sub1=<?=$_GET['utm_source']?>&sub2=<?=$_GET['utm_campaign']?>&sub3=<?=$_GET['utm_source_id']?>&u=<?=$_GET['target']?>&download</pre>

			<!--T:22-->
	== Downloading a clickworker ==		== Downloading a clickworker ==
	Using the resulting link, download the clickworker and save it to the file '''clickworker.php'''		Using the resulting link, download the clickworker and save it to the file '''clickworker.php'''

			<!--T:23-->
	[[File:Clickworker-page2.png]]		[[File:Clickworker-page2.png]]

			<!--T:24-->
	Then you need to create a '''click.php''' file, put the headers in it and include '''clickworker.php'''		Then you need to create a '''click.php''' file, put the headers in it and include '''clickworker.php'''

			<!--T:25-->
	<pre>		<pre>
	<?php		<?php

	header('Access-Control-Allow-Origin: *');		<!--T:26-->
			header('Access-Control-Allow-Origin: *');
	header('access-control-allow-methods: GET, POST, OPTIONS');		header('access-control-allow-methods: GET, POST, OPTIONS');
	header('access-control-allow-headers: X-Requested-With, Cache-Control, Content-Type');		header('access-control-allow-headers: X-Requested-With, Cache-Control, Content-Type');
Line 119:		Line 130:
	</pre>		</pre>

			<!--T:27-->
	The both files must be uploaded on the website.		The both files must be uploaded on the website.

	== Testing ==		== Testing == <!--T:28-->

			<!--T:29-->
	To check, go to the link in your browser:		To check, go to the link in your browser:
	<pre>https://my-site.com/click.php?utm_source=1&utm_campaign=123&utm_click_id=93652664834&target=https%3A%2F%2Fgoogle.com</pre>		<pre>https://my-site.com/click.php?utm_source=1&utm_campaign=123&utm_click_id=93652664834&target=https%3A%2F%2Fgoogle.com</pre>
	Great job! The redirect worked and you ended up on Google’s website.		Great job! The redirect worked and you ended up on Google’s website.

			<!--T:30-->
	[[File:Clickworker-redirect2.png]]		[[File:Clickworker-redirect2.png]]
	<br />		<br />
Line 133:		Line 147:
	Excellent result. The click was counted, the tags were placed correctly.		Excellent result. The click was counted, the tags were placed correctly.

			<!--T:31-->
	[[File:Clickworker-stat.png]]		[[File:Clickworker-stat.png]]

			<!--T:32-->
	[[Category:Features]]		[[Category:Features]]
	</translate>		</translate>

Admin at 16:37, 19 April 2024

2024-04-19T16:37:23Z

← Older revision		Revision as of 16:37, 19 April 2024
Line 30:		Line 30:
	<!--T:8-->		<!--T:8-->
	[[File:Download clickworker2.png]]		[[File:Download clickworker2.png]]
			<br />
	<br />		<br />

Admin at 16:36, 19 April 2024

2024-04-19T16:36:53Z

← Older revision		Revision as of 16:36, 19 April 2024
Line 2:		Line 2:
	<translate>		<translate>
	<!--T:1-->		<!--T:1-->
	By default, to verify click-through links for [[Meta Redirect-type integrations~~\|Meta redirect~~]], we use a ''clickworker'', a special page on the Kaminari Click domain, which checks the user and then redirects good users to the target link, and bots to [[Traffic back URL\|traffic-back URL]], if the corresponding option is enabled. This approach is as simple and convenient as possible, but has a number of disadvantages.		By default, to verify click-through links for [[Meta redirect\|Meta Redirect-type integrations]], we use a ''clickworker'', a special page on the Kaminari Click domain, which checks the user and then redirects good users to the target link, and bots to [[Traffic back URL\|traffic-back URL]], if the corresponding option is enabled. This approach is as simple and convenient as possible, but has a number of disadvantages.

	# If suddenly a technical problem occurs on our server, the redirect breaks down and your traffic will be lost.		# If suddenly a technical problem occurs on our server, the redirect breaks down and your traffic will be lost.

Admin at 16:36, 19 April 2024

2024-04-19T16:36:24Z

← Older revision		Revision as of 16:36, 19 April 2024
Line 30:		Line 30:
	<!--T:8-->		<!--T:8-->
	[[File:Download clickworker2.png]]		[[File:Download clickworker2.png]]
			<br />

	<!--T:9-->		<!--T:9-->
Line 85:		Line 86:
	Below is an example of the simplest implementation of a clickworker on your side using PHP.		Below is an example of the simplest implementation of a clickworker on your side using PHP.

	Let's say that you own a website ~~<code>https://~~my-site.com~~/</code>~~ and people come to you through links like this:		Let's say that you own a website '''my-site.com''' and people come to you through links like this:
	<pre>https://my-site.com/click.php?utm_source=1&utm_campaign=123&utm_click_id=93652664834&target=https%3A%2F%2Fgoogle.com</pre>		<pre>https://my-site.com/click.php?utm_source=1&utm_campaign=123&utm_click_id=93652664834&target=https%3A%2F%2Fgoogle.com</pre>
	And you want Kaminari Click to check the user for fraud and redirect to the target link (in this case, google).		And you want Kaminari Click to check the user for fraud and redirect to the target link (in this case, google).

Admin at 16:35, 19 April 2024

2024-04-19T16:35:05Z

← Older revision		Revision as of 16:35, 19 April 2024
Line 85:		Line 85:
	Below is an example of the simplest implementation of a clickworker on your side using PHP.		Below is an example of the simplest implementation of a clickworker on your side using PHP.

	Let's say that you own a website ~~'''~~https://my-site.com/~~'''~~ and people come to you through links like this:		Let's say that you own a website <code>https://my-site.com/</code> and people come to you through links like this:
	<pre>https://my-site.com/click.php?utm_source=1&utm_campaign=123&utm_click_id=93652664834&target=https%3A%2F%2Fgoogle.com</pre>		<pre>https://my-site.com/click.php?utm_source=1&utm_campaign=123&utm_click_id=93652664834&target=https%3A%2F%2Fgoogle.com</pre>
	And you want Kaminari Click to check the user for fraud and redirect to the target link (in this case, google).		And you want Kaminari Click to check the user for fraud and redirect to the target link (in this case, google).
Line 104:		Line 104:
	[[File:Clickworker-page2.png]]		[[File:Clickworker-page2.png]]

	Then you need to create a '''click.php''' file, put the headers in it and ~~call~~ '''clickworker.php'''		Then you need to create a '''click.php''' file, put the headers in it and include '''clickworker.php'''

	<pre>		<pre>
Line 117:		Line 117:
	</pre>		</pre>

	The files must be uploaded on the website.		The both files must be uploaded on the website.

	== Testing ==		== Testing ==
Line 126:		Line 126:

	[[File:Clickworker-redirect2.png]]		[[File:Clickworker-redirect2.png]]
			<br />
			<br />
	Time to check the statistics.		Time to check the statistics.
	Excellent result. The click was counted, the tags were placed correctly.		Excellent result. The click was counted, the tags were placed correctly.

Admin at 16:31, 19 April 2024

2024-04-19T16:31:57Z

@@ Line 2: / Line 2: @@
 <translate>
 <!--T:1-->
-By default, to verify click-through links for Meta Redirect-type integrations, we use a ''clickworker'', a special page on the Kaminari Click domain, which checks the user and then redirects good users to the target link, and bots to [[Traffic back URL|traffic-back URL]], if the corresponding option is enabled. This approach is as simple and convenient as possible, but has a number of disadvantages.
+By default, to verify click-through links for [[Meta Redirect-type integrations|Meta redirect]], we use a ''clickworker'', a special page on the Kaminari Click domain, which checks the user and then redirects good users to the target link, and bots to [[Traffic back URL|traffic-back URL]], if the corresponding option is enabled. This approach is as simple and convenient as possible, but has a number of disadvantages.
 # If suddenly a technical problem occurs on our server, the redirect breaks down and your traffic will be lost.
@@ Line 40: / Line 40: @@
 ! Name !! Description !! Note
 |-
-| kmnrId || kmnrId, generated during the ping at {{KamiLink|v2/ping}}. Needed for linking clicks if the '''[[S2S ping]]''' option is enabled. || -
+| kmnrId || kmnrId, generated during the ping at {{KamiLink|v2/ping}}. Needed for linking clicks if the '''[[S2S ping]]''' option is enabled. || Required if the option [[S2S ping]] is enabled
 |-
 | kmnrKey || Integration identifier under which the impression is analyzed. || Required parameter
@@ Line 58: / Line 58: @@
 | sub7 || ... || -
 |-
-| sub8 || Available if the option [[Additional subs|Additional subs]] is enabled || -
+| sub8 || ... || Available if the option [[Additional subs]] is enabled
 |-
-| sub9 || Available if the option [[Additional subs|Additional subs]] is enabled || -
+| sub9 || ... || Available if the option [[Additional subs]] is enabled
 |-
-| sub10 || Available if the option [[Additional subs|Additional subs]] is enabled || -
+| sub10 || ... || Available if the option [[Additional subs]] is enabled
 |-
 | u || The target link to which the user will be directed after verification. It should be in a URL-safe format (for example, processed with the JavaScript method [https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/encodeURIComponent encodeURIComponent]). || Required parameter if the option [[Target URL|Target URL]] is not enabled
@@ Line 74: / Line 74: @@
 For the clickworker to function correctly, it must send the following headers to the user's browser:
 <pre>
 accept-ch: Width, Viewport-Width, DPR, Device-Memory, Downlink, RTT, ECT, Save-Data, Sec-CH-UA-Arch, Sec-CH-UA-Bitness, Sec-CH-UA-Mobile, Sec-CH-UA-Model, Sec-CH-UA-Platform, Sec-CH-UA-Platform-Version, Sec-CH-UA, Sec-CH-UA-Full-Version
 </pre>
 <!--T:14-->
 [[Category:Features]]
 </translate>

Admin at 15:39, 19 April 2024

2024-04-19T15:39:45Z

← Older revision		Revision as of 15:39, 19 April 2024
Line 2:		Line 2:
	<translate>		<translate>
	<!--T:1-->		<!--T:1-->
	To verify click-through links, we use a ''clickworker'', a special page on our ~~domain~~.		By default, to verify click-through links for Meta Redirect-type integrations, we use a ''clickworker'', a special page on the Kaminari Click domain, which checks the user and then redirects good users to the target link, and bots to [[Traffic back URL\|traffic-back URL]], if the corresponding option is enabled. This approach is as simple and convenient as possible, but has a number of disadvantages.

			# If suddenly a technical problem occurs on our server, the redirect breaks down and your traffic will be lost.
			# Redirects between different sites are slower than within one site, so a redirect through our clickworker can increase the percentage of non-revenue to the target link.
			# You may feel uncomfortable that a third party is included in the redirect chain.

	<!--T:2-->		<!--T:2-->
	~~If you want to avoid losses and delays in cross-domain redirects~~, ~~you can download~~ the clickworker and ~~host~~ it on your server. It needs to be updated once a day because we regularly make changes to the scripts.		To solve these problems, we suggest downloading the ''clickworker'' and hosting it on your server. It needs to be updated '''once a day''' because we regularly make changes to the scripts.

	<!--T:3-->		<!--T:3-->
	'''Please note that this option is only available for ''Redirect''-type integrations.'''		'''Please note that this option is only available for ''Meta Redirect''-type integrations.'''

	<!--T:4-->		<!--T:4-->
Line 30:		Line 34:
	When delivering the clickworker to the user, you can dynamically replace the templates with current data.		When delivering the clickworker to the user, you can dynamically replace the templates with current data.

			== Templates description ==
	<!--T:10-->		<!--T:10-->
	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-
	! Name !! Description		! Name !! Description !! Note
	\|-		\|-
	\| kmnrId \|\| kmnrId, generated during the ping at {{KamiLink\|v2/ping}}. Needed for linking clicks if the '''[[S2S ping]]''' option is enabled.		\| kmnrId \|\| kmnrId, generated during the ping at {{KamiLink\|v2/ping}}. Needed for linking clicks if the '''[[S2S ping]]''' option is enabled. \|\| -
	\|-		\|-
	\| kmnrKey \|\| Integration identifier under which the impression is analyzed.		\| kmnrKey \|\| Integration identifier under which the impression is analyzed. \|\| Required parameter
	\|-		\|-
	\| sub1 \|\| Filled sub-tags. If you are not using certain tags, it is not mandatory to send them.		\| sub1 \|\| Filled sub-tags. If you are not using certain tags, it is not mandatory to send them. \|\| -
	\|-		\|-
	\| sub2 \|\| ...		\| sub2 \|\| ... \|\| -
	\|-		\|-
	\| sub3 \|\| ...		\| sub3 \|\| ... \|\| -
	\|-		\|-
	\| sub4 \|\| ...		\| sub4 \|\| ... \|\| -
	\|-		\|-
	\| sub5 \|\| ...		\| sub5 \|\| ... \|\| -
	\|-		\|-
	\| sub6 \|\| ...		\| sub6 \|\| ... \|\| -
	\|-		\|-
	\| sub7 \|\| ...		\| sub7 \|\| ... \|\| -
	\|-		\|-
	\| sub8 \|\| ~~...~~		\| sub8 \|\| Available if the option [[Additional subs\|Additional subs]] is enabled \|\| -
	\|-		\|-
	\| sub9 \|\| ~~...~~		\| sub9 \|\| Available if the option [[Additional subs\|Additional subs]] is enabled \|\| -
	\|-		\|-
	\| sub10 \|\| ~~...~~		\| sub10 \|\| Available if the option [[Additional subs\|Additional subs]] is enabled \|\| -
	\|-		\|-
	\| u \|\| The target link to which the user will be directed after verification. It should be in a URL-safe format (for example, processed with the JavaScript method [https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/encodeURIComponent encodeURIComponent]).		\| u \|\| The target link to which the user will be directed after verification. It should be in a URL-safe format (for example, processed with the JavaScript method [https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/encodeURIComponent encodeURIComponent]). \|\| Required parameter if the option [[Target URL\|Target URL]] is not enabled
	\|}		\|}

	~~<!--T:11-->~~
	~~If you are not using kmnrId, or you do not need all sub-tags, or if you have [[Traffic back URL\|Traffic-back URL]] instead of clickUrl, simply remove unnecessary templates from the link.~~

	<!--T:12-->		<!--T:12-->

Admin at 13:54, 30 November 2023

2023-11-30T13:54:10Z

← Older revision		Revision as of 13:54, 30 November 2023
Line 2:		Line 2:
	<translate>		<translate>
	<!--T:1-->		<!--T:1-->
	~~Для проверки кликовых ссылок мы используем~~ ''~~кликворкер~~'', ~~специальную страницу на своём домене~~.		To verify click-through links, we use a ''clickworker'', a special page on our domain.

	<!--T:2-->		<!--T:2-->
	~~Если вы хотите избежать потерь и задержек на кроссдоменных редиректах~~, ~~вы может скачать кликворкер себе и разместить на своём сервере~~. ~~Необходимо обновлять его раз в сутки, потому что мы постоянно вносим изменения в скрипты~~.		If you want to avoid losses and delays in cross-domain redirects, you can download the clickworker and host it on your server. It needs to be updated once a day because we regularly make changes to the scripts.

	<!--T:3-->		<!--T:3-->
	'''~~Обратите внимание, опция доступна только в интеграциях типа~~ ''Redirect''.'''		'''Please note that this option is only available for ''Redirect''-type integrations.'''

	<!--T:4-->		<!--T:4-->
	= ~~Подключение опции~~ =		= Option Activation =
	~~Закажите у менеджера включение опции~~ '''Download ~~clickworker~~''' ~~на своей интеграции~~. ~~После того как её включат~~, ~~в интеграции появится ссылка для скачивания~~.		Request the activation of the '''Download Clickworker''' option from your manager for your integration. Once enabled, a download link will appear in the integration for you to retrieve the clickworker.

	<!--T:5-->		<!--T:5-->
Line 18:		Line 18:

	<!--T:6-->		<!--T:6-->
	= ~~Шаблоны~~ =		= Templates =
	~~В фигурных скобках в ссылке находятся шаблоны~~, ~~они будут как есть прокинуты в код~~.		The curly brackets in the link contain templates, and they will be passed into the code as they are.

	<!--T:7-->		<!--T:7-->
Line 28:		Line 28:

	<!--T:9-->		<!--T:9-->
	~~При отдаче кликворкера пользователю вы можете на лету заменять шаблоны актуальными данными~~.		When delivering the clickworker to the user, you can dynamically replace the templates with current data.

	<!--T:10-->		<!--T:10-->
	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-
	! ~~Название~~ !! ~~Описание~~		! Name !! Description
	\|-		\|-
	\| kmnrId \|\| kmnrId, ~~сгенерированный при отстуке на~~ {{KamiLink\|v2/ping}}. ~~Нужен для склеивания кликов если у вас подключена опция~~ '''[[S2S ping]]'''.		\| kmnrId \|\| kmnrId, generated during the ping at {{KamiLink\|v2/ping}}. Needed for linking clicks if the '''[[S2S ping]]''' option is enabled.
	\|-		\|-
	\| kmnrKey \|\| ~~Идентификатор интеграции, в рамках которой анализируется показ~~.		\| kmnrKey \|\| Integration identifier under which the impression is analyzed.
	\|-		\|-
	\| sub1 \|\| ~~Заполенные суб~~-~~метки~~. ~~Если какие-то метки вы не используете~~, ~~их слать не обязательно~~.		\| sub1 \|\| Filled sub-tags. If you are not using certain tags, it is not mandatory to send them.
	\|-		\|-
	\| sub2 \|\| ...		\| sub2 \|\| ...
Line 59:		Line 59:
	\| sub10 \|\| ...		\| sub10 \|\| ...
	\|-		\|-
	\| u \|\| ~~целевая ссылка, на которую пользователь будет отправлен после проверки~~. ~~Должна быть в~~ URL-~~безопасном виде~~ (~~например~~, ~~обработана JS-методом~~ [https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/encodeURIComponent encodeURIComponent]).		\| u \|\| The target link to which the user will be directed after verification. It should be in a URL-safe format (for example, processed with the JavaScript method [https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/encodeURIComponent encodeURIComponent]).
	\|}		\|}

	<!--T:11-->		<!--T:11-->
	~~Если вы не используете~~ kmnrId, ~~или вам не нужны все~~ sub-~~метки~~, ~~или вместо clickUrl у вас подключён~~ [[Traffic back URL\|Traffic-back URL]], ~~просто удалите ненужные шаблоны из ссылки~~.		If you are not using kmnrId, or you do not need all sub-tags, or if you have [[Traffic back URL\|Traffic-back URL]] instead of clickUrl, simply remove unnecessary templates from the link.

	<!--T:12-->		<!--T:12-->
Line 70:		Line 70:
	<!--T:13-->		<!--T:13-->
	= Headers =		= Headers =
	~~Для корректной работы кликворкер должен отдавать браузеру пользователя следующие заголовки~~:		For the clickworker to function correctly, it must send the following headers to the user's browser:
	<pre>		<pre>
	accept-ch: Width, Viewport-Width, DPR, Device-Memory, Downlink, RTT, ECT, Save-Data, Sec-CH-UA-Arch, Sec-CH-UA-Bitness, Sec-CH-UA-Mobile, Sec-CH-UA-Model, Sec-CH-UA-Platform, Sec-CH-UA-Platform-Version, Sec-CH-UA, Sec-CH-UA-Full-Version		accept-ch: Width, Viewport-Width, DPR, Device-Memory, Downlink, RTT, ECT, Save-Data, Sec-CH-UA-Arch, Sec-CH-UA-Bitness, Sec-CH-UA-Mobile, Sec-CH-UA-Model, Sec-CH-UA-Platform, Sec-CH-UA-Platform-Version, Sec-CH-UA, Sec-CH-UA-Full-Version

Admin: Marked this version for translation

2023-09-19T02:03:17Z

Marked this version for translation

← Older revision		Revision as of 02:03, 19 September 2023
Line 1:		Line 1:
	<languages/>		<languages/>
	<translate>		<translate>
			<!--T:1-->
	Для проверки кликовых ссылок мы используем ''кликворкер'', специальную страницу на своём домене.		Для проверки кликовых ссылок мы используем ''кликворкер'', специальную страницу на своём домене.

			<!--T:2-->
	Если вы хотите избежать потерь и задержек на кроссдоменных редиректах, вы может скачать кликворкер себе и разместить на своём сервере. Необходимо обновлять его раз в сутки, потому что мы постоянно вносим изменения в скрипты.		Если вы хотите избежать потерь и задержек на кроссдоменных редиректах, вы может скачать кликворкер себе и разместить на своём сервере. Необходимо обновлять его раз в сутки, потому что мы постоянно вносим изменения в скрипты.

			<!--T:3-->
	'''Обратите внимание, опция доступна только в интеграциях типа ''Redirect''.'''		'''Обратите внимание, опция доступна только в интеграциях типа ''Redirect''.'''

			<!--T:4-->
	= Подключение опции =		= Подключение опции =
	Закажите у менеджера включение опции '''Download clickworker''' на своей интеграции. После того как её включат, в интеграции появится ссылка для скачивания.		Закажите у менеджера включение опции '''Download clickworker''' на своей интеграции. После того как её включат, в интеграции появится ссылка для скачивания.

			<!--T:5-->
	[[File:Download clickworker.png]]		[[File:Download clickworker.png]]

			<!--T:6-->
	= Шаблоны =		= Шаблоны =
	В фигурных скобках в ссылке находятся шаблоны, они будут как есть прокинуты в код.		В фигурных скобках в ссылке находятся шаблоны, они будут как есть прокинуты в код.

			<!--T:7-->
	<pre>https://kaminari.space/v1/click?kmnrKey=XXXXXXXXX&kmnrId={kmnrId}&sub1={sub1}&sub2={sub2}&sub3={sub3}&sub4={sub4}&sub5={sub5}&sub6={sub6}&sub7={sub7}&u={clickUrl}&download</pre>		<pre>https://kaminari.space/v1/click?kmnrKey=XXXXXXXXX&kmnrId={kmnrId}&sub1={sub1}&sub2={sub2}&sub3={sub3}&sub4={sub4}&sub5={sub5}&sub6={sub6}&sub7={sub7}&u={clickUrl}&download</pre>

			<!--T:8-->
	[[File:Download clickworker2.png]]		[[File:Download clickworker2.png]]

			<!--T:9-->
	При отдаче кликворкера пользователю вы можете на лету заменять шаблоны актуальными данными.		При отдаче кликворкера пользователю вы можете на лету заменять шаблоны актуальными данными.

			<!--T:10-->
	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-
Line 52:		Line 62:
	\|}		\|}

			<!--T:11-->
	Если вы не используете kmnrId, или вам не нужны все sub-метки, или вместо clickUrl у вас подключён [[Traffic back URL\|Traffic-back URL]], просто удалите ненужные шаблоны из ссылки.		Если вы не используете kmnrId, или вам не нужны все sub-метки, или вместо clickUrl у вас подключён [[Traffic back URL\|Traffic-back URL]], просто удалите ненужные шаблоны из ссылки.

			<!--T:12-->
	<pre>https://kaminari.space/v1/click?kmnrKey=767073697&sub1={sub1}&sub2={sub2}&u={clickUrl}&download</pre>		<pre>https://kaminari.space/v1/click?kmnrKey=767073697&sub1={sub1}&sub2={sub2}&u={clickUrl}&download</pre>

			<!--T:13-->
	= Headers =		= Headers =
	Для корректной работы кликворкер должен отдавать браузеру пользователя следующие заголовки:		Для корректной работы кликворкер должен отдавать браузеру пользователя следующие заголовки:
Line 65:		Line 78:
	</pre>		</pre>

			<!--T:14-->
	[[Category:Features]]		[[Category:Features]]
	</translate>		</translate>

Admin at 02:03, 19 September 2023

2023-09-19T02:03:07Z

← Older revision		Revision as of 02:03, 19 September 2023
Line 1:		Line 1:
			<languages/>
			<translate>
	Для проверки кликовых ссылок мы используем ''кликворкер'', специальную страницу на своём домене.		Для проверки кликовых ссылок мы используем ''кликворкер'', специальную страницу на своём домене.

Line 64:		Line 66:

	[[Category:Features]]		[[Category:Features]]
			</translate>