Hey Nick,A good portion of the Experience Cloud documentation uses DITA (for example, https://marketing.adobe.com/resources/help/en_US/reference/), and I was involved heavily with the tooling on the DITA side as well as with the Analytics implementation.Even though we use DITA to create and assemble the site pages, we track everything at the web page level, so there isn't too much that is DITA-specific about our Analytics implementation. There are many many ways to use content chunks to assemble...

My general rule:- Data that you want to use to use for audience building and targeting should go in Audience Manager- Data that you want to use to supplement Analytics reports and existing Target audiences should (also) go in Customer Attributes (it is fine to upload the data to both systems)Customer Attributes:- In Adobe Analytics, you can use uploaded dimensions directly in Analytics reports and segments. For example, if you upload a customer status (bronze, silver, gold), you can use that dim...

Take a look at the Marketing Cloud ID service, specifically using the setCustomerID function: https://marketing.adobe.com/resources/help/en_US/mcvid/mcvid-get-set.html

Put each context data value in the same HashMap, and then pass one HashMap to the track call: // Adobe - track when this state loads HashMap exampleContextData1 = new HashMap(); exampleContextData1.put("myapp.login.LoginStatus", "logged in"); exampleContextData1.put("myapp.login.Template", "templateB"); Analytics.trackState("Home Screen", exampleContextData1);

The REST API documentation is at Home | Adobe Developer Connection​. When you are ready to request the report, one thing to keep in mind is that the pageurl is a data warehouse dimension, so be sure to add "source":"warehouse" to the request:{ "reportDescription":{ "reportSuiteID":"INSERT-RSID-HERE", "dateFrom":"2017-11-01", "dateTo":"2017-11-07", "elements":[ { "id":"pageurl" } ], "source":"warehouse" }}

Here is an example of a deep link with context data:app://home/promo?a.deeplink.id=test-deep-link1&a.launch.campaign.trackingcode=promo1&a.launch.campaign.source=promo1source&a.launch.campaign.medium=promo1mediumIt looks to me like your structure is OK. For debugging, mobile hits are sent using POST so you need to make sure your debugger can see those hits. To see this data in reports, use Analysis Workspace and drag the Launch Name dimension to a freeform table. You should have instances of tes...

Make sure you are escaping your data variable correctly:data = """{ \"rsid_list\":[ \"myreportsuiteid\" ]}"""Also, you should take a look at this wrapper library: GitHub - dancingcactus/python-omniture: A high-level Python wrapper for the Adobe Omniture API.This library should save you some effort, there are several good examples in that repo.cathyw49544988,The Analytics REST API reference is available at Developer Connection | Adobe Developer Connection

Hi Craig, this doc is linked in the DTM help under "object model reference", here is the link: http://microsite.omniture.com/t2/help/en_US/dtm/object_reference.pdf

Try changing the first parameter from 'true' to 'this'var s_code = s.tl(this, linkType, linkName, null, function () { document.location = href; });Passing 'true' disables the (up to) 500 ms delay that helps make sure your image request goes through. More info here: http://microsite.omniture.com/t2/help/en_US/sc/implement/function_tl.html