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...
We've developed a new guide with how-to videos to help you get started
with Mobile Services and the Mobile SDKs. This guide is available at the
following link:Mobile App Engagement Guide You'll LearnHow to set up a
mobile app in Adobe Mobile Services. How to add the Mobile Services SDK
to your app to enable Analytics, Target, Audience Manager, Acquisition
Tracking, and Push Messaging.How to collect lifecycle metrics.How to
collect custom metrics for analysis.How to deliver personalized
experienc...
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
Hi Warren, the guidelines in my post are for the lookup columns, not the
hit data columns. The column sizes for the hit data varies widely and
should be set based on the reference table Ryan linked above.For those
who haven't had the pleasure of consuming a raw data feed, some columns
contain a numeric key that is mapped to a human-readable string using a
lookup file. For example, a browser key in the raw feed might be '657',
you'd use the lookup file to find out that this represents 'Google
Chr...
The lookup key column will be at most a 32-bit unsigned integer.The
associated lookup value will be at most a 255 character string.Some of
the lookup key columns will never get close to that (connection type
comes to mind, I think it currently has ~5 values), but since you are
only looking at 15 or so lookup files for a typical feed, if you use
these max values you'll be set going forward.
Do you have access to the web server logs? You could import the log
files using Data Sources:
http://microsite.omniture.com/t2/help/en_US/sc/datasources/datasrc_web_log.html
Hi Sid,If you have not enabled a grace period, new visitors are given
only an AMCV cookie which is now used instead of s_vi. If a visitor
already had an s_vi cookie from a previous visit though, it will
continue to be used instead of the AMCV cookie.The table at the bottom
of this topic has more details:
http://microsite.omniture.com/t2/help/en_US/mcvid/mcvid_analytics.html
Hi John, your account manager or Customer Care can help you set this
up.You do have to pick which metrics and dimensions you want included,
though there isn't a limit as to how many you can include, and you can
request multiple independent streams. This is done to preserve bandwidth
and processing. For example, if you received a stream of everything
available for a visualization that displayed 30 metrics/dimensions,
you'd still be processing then discarding 90% of the transferred data
(300+ metr...
Hi Chris, it sounds like you are being impacted by the data processing
issue that is currently reported on http://status.adobe.com/, hopefully
you were able to get in touch with Customer Care and get additional
info.
If you are implementing for the first time, you might be be better off
looking at the demo app that is available at
https://github.com/Adobe-Marketing-Cloud/mobile-services/tree/master/samples/Android
rather than at a project that uses an earlier SDK. As you noticed the
code and approach have changed significantly. If you do end out looking
at the older SDK, this topic describes the changes between versions:
https://marketing.adobe.com/resources/help/en_US/mobile/android/migration_v3.html
You ca...
Variable names in JavaScript are case sensitive, replace 's.evar' with
's.eVar' for each of these variable (and any others I missed):s.evar6 =
"";s.evar7 = "";s.evar10 = "Approved";s.evar17 = "@Model.Id";
This can happen if the s variable is being overwritten somewhere in your
code. To find where it is happening, add an assert to
doPlugins:s.usePlugins=true function s_doPlugins(s) {
console.assert(s.pageName, "pagename is empty"); // ..other code that
may or may not be here already } s.doPlugins=s_doPluginsThis will output
a stack trace to the console so you can see where the call came from.
After you find the call, add a call to s_gi to reset s to the global
AppMeasurement object:
http://microsi...
Are you getting any data at all in your report suite? Run a visits
report with hour granularity to see if any hits are making it to data
collection. If you don't even see visits, it is likely that the hits
aren't making it to the network due to proxy configuration.If you see
visits but not any mobile metrics, make sure that you have enabled the
mobile reports:
http://microsite.omniture.com/t2/help/en_US/mobile/ios/analytics.htmlThe
output in bloodhound and your configuration look correct, so I d...
#2 happens when the s.namespace variable isn't set, so you get a
different s_vi cookie for each report suite. When s.namespace isn't set
it means that users are identified uniquely for each report suite
instead of uniquely for the tracking server.You can set s.namespace and
the cookie will be migrated automatically.
To help minimize the impact of changing the data collection domain, you
can migrate visitors from the old data collection domain to the new one.
More information here:
http://microsite.omniture.com/t2/help/en_US/sc/implement/index.html#Visitor_MigrationOther
than that I can't think of anything else that might impact reporting.
Hi Lando, I haven't heard of any issues on Windows 8.1 launching ad hoc
analysis, this is usually caused by the browser not starting Java. Here
is something your user can try to narrow the issue:1. Right-click the
Launch Ad Hoc Analysis button, and save the link. This will be a file
called discover.jnlp.2. From a command prompt, run: javaws
c:\path-to-file\discover.jnlpThat should launch the app. You could also
try launching some of the demo jnlp files on the Java site, here are a
few:
http://do...
Hi John, since your iframe and parent are on the same domain, you should
be able to use window.parent in the iframe to access the s object and
s.t() call defined on your main page. From there, you can update your
SendForm() function to verify the form data, set variables on the s
object, and then call s.tl() directly (you probably don't want to call
s.t or you'll get two page views).
You are correct about s_vi being the visitor ID, this should stay the
same for every visit (at least we hope so!). The visit ID (the visit
number part) is calculated after the hit is collected so it isn't
available through dynamic variables.I think you can get what you are
after using a combination of the visitor ID and visit number from the
getVisitNum implementation plugin,
http://microsite.omniture.com/t2/help/en_US/sc/implement/#getVisitNumInstead
of using the s_vi dynamic variable, I'd sugg...
Are you using a popup blocker or ad blocker? I was just on a call today
with a co-worker who was getting that same redirect error in Firefox and
we thought that might be what was causing it.
Adobe gives it a time stamp, so you can safely remove the t= query
parameter from your static image request. The t= query parameter
(date/time in DigitalPulse Debugger) is used to populate the Time Zones
report, all other metrics are calculated using a time that is set by the
data collection server when the request is received. In your case it
makes sense to remove it so you don't have incorrect data on the Time
Zones report.
Mobile: Web traffic that was identified as coming from a mobile
device.Mobile App: App data that was collected by the iOS, Android, and
other AppMeasurement SDKs.The report suite that collects web and app
data will have both of these panes, others will have only Mobile.
