In relation to the question I referred, one of the replies referred to file uploads to cloud destinations (Locations) and file locations. This, I think, is the issue: I consider file uploads to be actual uploads, but in reality they are likely ways to tell Classifications API in which cloud location...

To answer at least a part of your question: The filters listed refer to the "metricFilters" array and the item ids you've defined in the request. Since you have a dimension with breakdowns, it looks like the first two (0 and 1, brand and product) index of columns are used by those and the rest liste...

Premise: I am creating a process where a maintained classifications file can be fully or partially manually be uploaded to Analytics' Classifications API and data is updated. This can be done with relative ease using FTP file transfer to send items in, but since the API has more options, we decided ...

Even through possible and there might be good reasons to do so, there is no need to run the AA Extension with Web SDK, as Web SDK is capable of sending data to Analytics by itself without using any other Extensions (such as Visitor ID Service). This also removes the questions regarding hostnames for...

I can't say off the bat why would the second, identical call not include the actual query for Target, but that is very much why the second call in debugger is not working the same, as the parts of request defining the action to Target is missing and will not have Target capability working as intende...

Hello!For question 1), you need to separately send the display event information, as mentioned on the second checkbox. This would be done in the same call as your Analytics data is being sent and should avoid the issue of having two calls per page load registered to Analytics as well. For number 2),...

I have tested different scenarios for the POST upload method by using Postman, curl in Windows Powershell, curl in Unix server. I've placed the file locally on the Windows machine I'm using, remote Unix server and open location available through HTTPS without authentication. The issue is that these ...

I see, my mistake in taking "parameters" as universally instead of literally Target-parameters. These parameters, as you said, are part of the XDM data structure and Target gets them automatically. As shown in the migration document, it does not cover profile, user and some other parts of Target dat...

This link could help you find out the missing details in data mapping for Target's parameters: Send parameters - Migrate Target from at.js 2.x to Web SDK | Adobe Target While it is true that all XDM is passed to each destination (with the exception of items under data-object), it does not mean they ...

Hey. In this case I think you have the right idea and by populating data that is used by Analytics to identify page calls, the data is counted towards page views, regardless of its type. This seems a bit backward, but it is what it is. The best method is to use a different data object for Target and...