This Metadata tracer tool traces metadata for a URL configured in Property Manager. You can use it for the current property version active either on staging or production.

With this tool you can trace metadata tags applied to a request and visually confirm if the appropriate metadata tags got applied in the right moment.

Submit a request

Learn how to submit a request in the Metadata tracer tool.

Go to ☰ > SUPPORT > Edge Diagnostics.
In the side menu, select > Metadata tracer.
Select the Request method: GET, POST, or HEAD. The default method is GET.
Configure the request based on the selected request method.

POST GET, HEAD

a. Select up to 10 Locations you want to run the request from.

b. Add the Content-Type Request header.

c. Optional: Add other Request header to simulate user traffic and for debugging purpose. It needs to follow the format: Header: value. For example, User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.169 Safari/537.36. Check this list of user agents for possible values.

d. Optional: Click Add another header to add more request headers. To add Akamai Pragma headers, click Add Pragma headers. To learn more, check Pragma headers.

e. Optional: Enter the POST request body. For safety, ensure the request and response don’t contain sensitive information and test on non-production data only. a. Select whether you want to run the request from a Location or Edge server IP. Enter up to 10 values.

b. Optional: Add a Request header to simulate user traffic and for debugging purpose. It needs to follow the format: Header: value. For example, User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.169 Safari/537.36. Check this list of user agents for possible values.

c. Optional: Click Add another header to add more request headers. To add Akamai Pragma headers, click Add Pragma headers. To learn more, check Pragma headers.

POST	GET, HEAD
a. Select up to 10 Locations you want to run the request from. b. Add the `Content-Type` Request header. c. Optional: Add other Request header to simulate user traffic and for debugging purpose. It needs to follow the format: Header: value. For example, User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.169 Safari/537.36. Check this list of user agents for possible values. d. Optional: Click Add another header to add more request headers. To add Akamai Pragma headers, click Add Pragma headers. To learn more, check Pragma headers. e. Optional: Enter the POST request body. For safety, ensure the request and response don’t contain sensitive information and test on non-production data only.	a. Select whether you want to run the request from a Location or Edge server IP. Enter up to 10 values. b. Optional: Add a Request header to simulate user traffic and for debugging purpose. It needs to follow the format: Header: value. For example, User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.169 Safari/537.36. Check this list of user agents for possible values. c. Optional: Click Add another header to add more request headers. To add Akamai Pragma headers, click Add Pragma headers. To learn more, check Pragma headers.

Select whether the property you want to trace metadata is active on Production or Staging.
Click Submit.

What you should see
If you entered more than one location or edge server IP, Edge Diagnostics divides your input; one request per one location or edge server IP. All requests appear in the Recent requests table. Click in the table's corner to see only your requests.

Next steps
Click your request’s row to check the results. If you see in the Actions column, it means, that your request could not be processed and you need to retry.

Results

To learn about results, check How to read the results.