oh hey @JSP2, I have a solid update for you on this one. I've inherited
the Mobile Services docs, making sure that they have a nice and
comfortable retirement. As a part of this, I've been kept in the loop
regarding EOL notice stuff. This page should have everything you
other words, we are migrating all Mobile Services processing rules to
Adobe Analytics sometime soon. I've heard rumors that it could be as
soon as the ...
Hello Analytics community!One of our community members recently brought
to our attention a component in Usage Logs that makes it difficult to
use. A given log is recorded in the language of the user performing the
task, not the language of the individual viewing the logs. While this is
not an issue for organizations who use a single language, performing any
kind of analysis on companies that use multiple languages can be quite
burdensome.As it turns out, fixing this on the backend is not nearly ...
Great post, thank you for sharing!There is one use case where
clearVars() is ideal, and that's in single-page applications when you
genuinely want to clear everything so it doesn't bleed over into the
Hi everyone! We have received many questions about the impact of Apple’s
on Adobe Analytics and hope to address some questions you might have.
Note: all information contained on this page is provided solely for
informational purposes and should not be relied upon as legal advice.
What is Apple’s App Tracking Transparency framework? Apple’s ATT
framework requires organizations to obtain user authorization to share
their data where the app (i) collects the user’s data and, (ii) shares
said user’s ...
Search the source code on your site for getQueryParam. You should be
able to find the campaign variable, and it will tell you which query
string parameter it is getting assigned to within the method's
argument.Alternatively, you can share your site URL and we can check out
how Analytics was implemented.
Certainly!Navigate to the doc page on getTimePartingCopy the code block
on that page, which contains the latest version of the plug-inIn Adobe
Experience Platform Launch, locate the custom code block containing the
old version of the plug-inPaste the new version of the plug-in over the
old versionImportant note: The dimension items that the latest version
of this plug-in returns is a lot different than old versions. Make sure
that you also update variables that reference this plug-in so they
Hello Analytics community and implementation experts! With 2020 drawing
to a close, I wanted to resurface an issue we saw crop up at the
beginning of the year. This is simply a precautionary warning to make
2021 rolls around.In older versions of the getTimeParting plug-in, years
were hardcoded in to help accommodate some daylight savings logic. While
this issue was fixed well ahead of time, many implementations did not
are not case-sensitive. If you send the same value in different cases
(for example, "DOG" and "Dog" ), Analysis Workspace groups them together
into the same dimension item. The case of the first value seen at the
beginning of the reporting month is used. Data Warehouse shows the first
value encountered during the request period.
The way I see it, using segments as dimensions would be your best bet.
You can then apply any number of metrics to your freeform table, and
even save copies of the project if you need different reports on all
those markets. Once you've created the 20 segments and dragged them onto
the table, you should be good to go.