Ping back URL - Revision history

Admin at 09:30, 5 May 2026

2026-05-05T09:30:18Z

← Older revision		Revision as of 09:30, 5 May 2026
Line 62:		Line 62:
	\| kmnrKey \|\| Integration identifier		\| kmnrKey \|\| Integration identifier
	\|-		\|-
	\| fraud \|\| 1 if the hit is fraudulent, 0 if the hit is non-fraudulent, ~~-1 if the hit could not be verified~~		\| fraud \|\| 1 if the hit is fraudulent, 0 if the hit is non-fraudulent,
	\|-		\|-
	\| block \|\| 1 if the hit was blocked according to the integration settings, 0 if the hit wasn't blocked		\| block \|\| 1 if the hit was blocked according to the integration settings, 0 if the hit wasn't blocked

Admin at 09:05, 21 November 2025

2025-11-21T09:05:14Z

← Older revision		Revision as of 09:05, 21 November 2025
Line 82:		Line 82:

	<!--T:15-->		<!--T:15-->
	If the ping-back still cannot be delivered, you can always retrieve the status for any click via our API, which serves as the reliable source of truth regardless of delivery success.		If you receive a ping-back, your server should respond with a status 200. Otherwise, we make three more attempts to send the request. If the ping-back still cannot be delivered, you can always retrieve the status for any click via our API, which serves as the reliable source of truth regardless of delivery success.

	<!--T:6-->		<!--T:6-->

Admin: t15 Убрал упоминание логов заменив API

2025-11-19T11:24:12Z

t15 Убрал упоминание логов заменив API

← Older revision		Revision as of 11:24, 19 November 2025
Line 82:		Line 82:

	<!--T:15-->		<!--T:15-->
	If ~~you receive a~~ ping-back, ~~your server should respond with a~~ status ~~200. Otherwise~~, ~~we make three more attempts to send~~ the ~~request. If it was not possible to send a ping-back, we save it in an internal log and can provide it to you upon request~~.		If the ping-back still cannot be delivered, you can always retrieve the status for any click via our API, which serves as the reliable source of truth regardless of delivery success.

	<!--T:6-->		<!--T:6-->

Admin: Marked this version for translation

2024-01-26T12:23:30Z

Marked this version for translation

← Older revision		Revision as of 12:23, 26 January 2024
Line 18:		Line 18:
	To understand which impression we've checked, you need to mark it.		To understand which impression we've checked, you need to mark it.

			<!--T:14-->
	If you have an '''JS check'''-type integration, add the <code>kmnrId</code> key to <code>window.kmnr</code> with any unique identifier convenient for you. By this identifier you can later recognize the impression.		If you have an '''JS check'''-type integration, add the <code>kmnrId</code> key to <code>window.kmnr</code> with any unique identifier convenient for you. By this identifier you can later recognize the impression.

Line 80:		Line 81:
	\|}		\|}

			<!--T:15-->
	If you receive a ping-back, your server should respond with a status 200. Otherwise, we make three more attempts to send the request. If it was not possible to send a ping-back, we save it in an internal log and can provide it to you upon request.		If you receive a ping-back, your server should respond with a status 200. Otherwise, we make three more attempts to send the request. If it was not possible to send a ping-back, we save it in an internal log and can provide it to you upon request.

Admin at 12:22, 26 January 2024

2024-01-26T12:22:59Z

← Older revision		Revision as of 12:22, 26 January 2024
Line 36:		Line 36:
	After receiving, processing the data, and making a decision about the bot status of the click, we send the decision to you in JSON POST format.		After receiving, processing the data, and making a decision about the bot status of the click, we send the decision to you in JSON POST format.
	<pre>{		<pre>{
	"kmnrId":"50d9ecc6-402b-4a74-9397-fc20f2980567",		"kmnrId": "50d9ecc6-402b-4a74-9397-fc20f2980567",
	"kmnrKey":111111111,		"kmnrKey": 111111111,
	"fraud":1,		"fraud": 1,
	"block":1,		"block": 1,
	"sub1":"sub1 value",		"sub1": "sub1 value",
	"sub2":"sub2 value",		"sub2": "sub2 value",
	"sub3":"sub3 value",		"sub3": "sub3 value",
	"sub4":444,		"sub4": 444,
	"sub5":555,		"sub5": 555,
	"sub6":"~~foo-bar~~",		"sub6": "",
	"sub7":"~~true~~"		"sub7": ""
	}</pre>		}</pre>

Admin at 12:21, 26 January 2024

2024-01-26T12:21:43Z

← Older revision		Revision as of 12:21, 26 January 2024
Line 16:		Line 16:
	<!--T:8-->		<!--T:8-->
	== kmnrId ==		== kmnrId ==
	To understand which impression we've checked, you need to mark it. If you have an '''JS check'''-type integration, add the <code>kmnrId</code> key to <code>window.kmnr</code> with any unique identifier convenient for you. By this identifier you can later recognize the impression.		To understand which impression we've checked, you need to mark it.

			If you have an '''JS check'''-type integration, add the <code>kmnrId</code> key to <code>window.kmnr</code> with any unique identifier convenient for you. By this identifier you can later recognize the impression.

	<!--T:9-->		<!--T:9-->
Line 32:		Line 34:
	<!--T:4-->		<!--T:4-->
	= Response format =		= Response format =
	After receiving, processing the data, and making a decision about the bot status of the click, we send the decision to you in JSON POST format. <~~code~~>{ kmnrId: '50d9ecc6-402b-4a74-9397-fc20f2980567', kmnrKey: 111111111, fraud: 1, block: 1, sub1: 'sub1 value', sub2: 'sub2 value', sub3: 'sub3 value', sub4: 444, sub5: 555, sub6: 'foo-bar', sub7: 'true' }</~~code~~>		After receiving, processing the data, and making a decision about the bot status of the click, we send the decision to you in JSON POST format.
			<pre>{
			"kmnrId":"50d9ecc6-402b-4a74-9397-fc20f2980567",
			"kmnrKey":111111111,
			"fraud":1,
			"block":1,
			"sub1":"sub1 value",
			"sub2":"sub2 value",
			"sub3":"sub3 value",
			"sub4":444,
			"sub5":555,
			"sub6":"foo-bar",
			"sub7":"true"
			}</pre>

	<!--T:13-->		<!--T:13-->

Admin at 12:19, 26 January 2024

2024-01-26T12:19:43Z

← Older revision		Revision as of 12:19, 26 January 2024
Line 32:		Line 32:
	<!--T:4-->		<!--T:4-->
	= Response format =		= Response format =
	After receiving, processing the data, and making a decision about the bot status of the click, we send the decision to you in JSON POST format. <code>{ kmnrId: 111111111, fraud: 1, block: 1 }</code>		After receiving, processing the data, and making a decision about the bot status of the click, we send the decision to you in JSON POST format. <code>{ kmnrId: '50d9ecc6-402b-4a74-9397-fc20f2980567', kmnrKey: 111111111, fraud: 1, block: 1, sub1: 'sub1 value', sub2: 'sub2 value', sub3: 'sub3 value', sub4: 444, sub5: 555, sub6: 'foo-bar', sub7: 'true' }</code>

	<!--T:13-->		<!--T:13-->

Admin at 12:16, 26 January 2024

2024-01-26T12:16:09Z

← Older revision		Revision as of 12:16, 26 January 2024
Line 15:		Line 15:

	<!--T:8-->		<!--T:8-->
			== kmnrId ==
	To understand which impression we've checked, you need to mark it. If you have an '''JS check'''-type integration, add the <code>kmnrId</code> key to <code>window.kmnr</code> with any unique identifier convenient for you. By this identifier you can later recognize the impression.		To understand which impression we've checked, you need to mark it. If you have an '''JS check'''-type integration, add the <code>kmnrId</code> key to <code>window.kmnr</code> with any unique identifier convenient for you. By this identifier you can later recognize the impression.

Admin at 12:10, 26 January 2024

2024-01-26T12:10:10Z

← Older revision		Revision as of 12:10, 26 January 2024
Line 2:		Line 2:
	<translate>		<translate>
	<!--T:1-->		<!--T:1-->
	If you want to receive the verification results for each click on your URL, you can do so using the '''Ping-back URL''' option.		If you want to receive the verification results for each click on your own URL, you can do so using the '''Ping-back URL''' option.

	<!--T:2-->		<!--T:2-->
	= Option activation =		= Option activation =
	~~Request the activation of~~ the '''Ping-back URL''' option ~~from your manager for~~ your integration.		Ask your manager to activate the '''Ping-back URL''' option on your integration.

	<!--T:7-->		<!--T:7-->

Admin at 12:07, 26 January 2024

2024-01-26T12:07:32Z

← Older revision		Revision as of 12:07, 26 January 2024
Line 34:		Line 34:

	<!--T:13-->		<!--T:13-->
	By kmnrId you can find the impression in your stat.		By kmnrId and sub-tags you can find the impression in your stat.

	<!--T:5-->		<!--T:5-->
Line 41:		Line 41:
	! Name !! Value		! Name !! Value
	\|-		\|-
	\| kmnrId \|\| ~~kmnrId, unique~~ identifier convenient for you		\| kmnrId \|\| Unique identifier convenient for you
	\|-		\|-
	\| ~~fraud~~ \|\| ~~1 if the click is fraudulent, 0 if the click is non-fraudulent, -1 if the click could not be verified~~		\| kmnrKey \|\| Integration identifier
	\|-		\|-
	\| block \|\| 1 if the ~~click~~ was blocked according to the integration settings, 0 if the ~~click~~ wasn't blocked		\| fraud \|\| 1 if the hit is fraudulent, 0 if the hit is non-fraudulent, -1 if the hit could not be verified
			\|-
			\| block \|\| 1 if the hit was blocked according to the integration settings, 0 if the hit wasn't blocked
			\|-
			\| sub1 \|\| Sub-tags that were sent with the hit
			\|-
			\| sub2 \|\| ...
			\|-
			\| sub3 \|\| ...
			\|-
			\| sub4 \|\| ...
			\|-
			\| sub5 \|\| ...
			\|-
			\| sub6 \|\| ...
			\|-
			\| sub7 \|\| ...
	\|}		\|}

			If you receive a ping-back, your server should respond with a status 200. Otherwise, we make three more attempts to send the request. If it was not possible to send a ping-back, we save it in an internal log and can provide it to you upon request.

	<!--T:6-->		<!--T:6-->