You can check any tracking URL (ad impression, click, conversion, CAD) calling it in preview mode. A preview tracking request will be processed as closely as possible to the regular one. Some processing parts like the spider treatment are skipped. On the other hand, there are some additional checks such as the extended basket evaluation, especially in the preview mode.
No request processing results are stored or counted, so the same tracking URL can be called several times in preview mode. Processing results will be sent back as a JSON object containing all input parameters and calculated values like redirecting location URL or processing error information.
Working with Preview Mode
Preview mode is activated by adding of the query parameter preview_modeset to 1 or true to the regular URL (…&preview_mode=1)
Preview response always has the HTTP status 200 (OK), regardless of whether a processing error occurs.
Response content is a Json object containing
untracked_reason - object (in case of Untracked) containing code, alias and optional message
params - all request parameters like amc
validated parameter values like normalized basket
request specific calculated values like click channel or best matching voucher id on conversions
redirecting location URL
attribution information on conversions
explanation of why a click is filtered out due to custom click filters
The untracked_reason object is always present if processing was unsuccessful
You can let onpage clicks and conversions be called in Preview Mode using an internal preview cookie, which can be set manually before testing and should be removed afterwards. All tracking requests with this cookie set are called as in Preview Mode, so you can just load the landing page to check onpage clicks, or make a test purchase to see the attribution results immediately.
Preview response with cookie looks different because the preview Json object cannot be sent directly in response body, which is always the one pixel image both on clicks and conversions. The preview Json object is transmitted in the custom http header x-preview-response, which can be found in http log of the browser.