ads
POST /v1/public/ads-wordpress/clicks
The plugin's click-fraud tag sends paid-click visits for scoring.
Authentication
This endpoint does not take an API key. It takes its own credential, issued to the plugin or service that calls it, as a bearer token; see the description above.
This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.
Try it
Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.
curl -X POST https://api.zinndigital.com/v1/public/ads-wordpress/clicks \
-H "Authorization: Bearer zdk_live_…" \
-H "Content-Type: application/json" \
-d '{ "hits": <object[]> }'Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console
Details
Site token only. Up to 500 visits a batch, the facts an access log holds. Visits that carry a paid-click id (gclid, msclkid, fbclid, ttclid, li_fat_id, twclid, epik) and are older than the 10-minute dwell window are scored by the same click-fraud shield as sites hosted by Zinn® (docs/1006 §15), on the connected host whatever host a visit names. Each click is stored once, so a re-sent batch stores nothing new. Nothing is scored when the organisation switched the shield off.
Request body
| Name | Type | Required | What it is |
|---|---|---|---|
hits | object[] | Yes | — |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
received | integer | Yes | — |
clicks | integer | Yes | — |
stored | integer | Yes | — |
suspected | integer | Yes | — |
Errors this endpoint can return
401 · 422 · 429