I'm simplifying a bit here, but hopefully this helps....From a coding
perspective, there are two primary ways to send in data to Adobe
Analytics. In javascript, those two methods are:s.t() - page views.tl()
- link callThose methods determine the "page event" of the hit, which
are further defined here: Page Event Lookup . Any hit with a page event
of 0 is considered a page view.Bounces are determined during processing
as Adobe Analytics evaluates all hits of a particular visit.
To be clear, there is no longer a requirement to become certified to use
processing rules specifically.ACE Certifications, which are quite
different from the aforementioned processing rules certification, are no
longer handled through Pearson as you've outlined.
Also keep in mind that there is a "First Touch" attribution model as
part of Attribution IQ (Report time attribution). This works a bit
differently from the evar concepts so far discussed.From this lens, the
date range of the report can come into play, depending on your lookback
window (visit/visitor). There is a good example of first touch
attribution for attribution IQ here: Attribution IQ
Oh, I see. You are trying to load page-level metrics from Analytics into
the AEM page. That integration can be a bit tricky. The biggest issue I
have seen with the integration is a mismatch in the pagename value that
AEM uses in its API queries and the pagename values used for Analytics
tracking.I would recommend opening a support ticket with the AEM
Customer Care team to confirm if this is a mismatch of the pagename and
to discuss configuration options to correct the integration. They will
need...
Can you elaborate on what issue you are seeing with Activity Map? For
example, are you having trouble getting the Activity Map data to be sent
on the image requests or is it more of a problem with rendering the
overlays?Some things you may consider checking:On you web page, open up
Dev Tools and, in the console, run the command 's_c_il'. This should
return an array of analytics related objects, including the activity map
module. This is a good way to confirm that the library is loading as
expect...
See the appendVisitorIDsTo method of the visitor object. This will help
with passing the visitor ID via the query string when navigating from
one domain to
another.https://marketing.adobe.com/resources/help/en_US/mcvid/mcvid-appendvisitorid.html
How are CNAME's used with the ECID Service?Following the session, there
was a fair amount of confusion about the role of CNAME's in visitor
identification. We spoke about CNAME's in two different contexts, which
I'll attempt to clarify here.1. Cross-Domain Tracking:For browsers that
block 3rd-party cookies, including Pre-ITP 2.1 Safari, CNAME's could
facilitate using the same AMCV cookie values between domains, provided
that visitors first navigated to the CNAME domain, then to other
domains. Th...
There have been a number of reports of "links to projects/reports" not
working. In particular, the issue seems related to either user migration
and/or Experience Cloud Logins.From your example above, it looks like
you may still be using legacy Analytics logins, which breaks a little
from what we've seen so far. Either way, a support ticket would probably
be the best bet.
I would add that we have seen a few cases that are similar to what you
describe here. If you are on the latest version of ReportBuilder and are
still seeing the issue, I would recommend opening a support case with
the details.
For the most part, the results would be the same. However, I generally
recommend that rules be set up to pull from as close to the source of
truth as possible. So, if Tracking Code is pulling from a query string
parameter, the processing rule should also pull from the query string
parameter.The reason I like this approach is because, on occasion, you
run into javascript errors and/or network nonsense that may prevent
Tracking Code from being populated. If your processing rules are
dependent on t...
