I was referring this page browserWidth , as per this document browserWidth will be setup before "doPlugin" but this is not correct for AppMeasurement. It was working fine for s_code.
There is the option to add a user expiration, and to change / extend it but not to remove it so if you accidentally set an expiration or for example somebody decides to leave the business but we manage to retain them we can't ever remove that expiration. Minor but slightly annoying.
I LOVE the calculated metric builder and I've started using some of the more advanced functions to start producing some much more useful interactive Workspaces. One wall I've hit though is that if I want to create a table of top products that match metric criteria such as "show me conversion for products with more than 1000 visits" when I rank in the opposite direction all I get is 0%. While this is technically accurate it means I can't create a table of those top products I'm just ranking the most relevant ones at the top.The reason for this is the false value of the function is 0 which is still interpreted as a value and therefore displayed in the report, what I want to be able to do is set it to NULL instead so that if I sort by that metric ONLY those products are displayed and everything with no value is hidden.
In a previous post (http://ideas.omniture.com/t5/Idea-Exchange-for-Adobe/Segment-Toggle-quot-Normal-Exclude-qu ot-Feature/idi-p/14612) I mentioned it would be great to basically have a quick negative segment creation. It appears as if Adobe figured this logic out with the "Everyone Else" feature with Segment Comparison. While, Segment Comparison is nice, it really seems to give limited results outside of "next steps to investigate". For instance, it will give me a weight of say 0.20 for Mobile visitors and tell me, "hey this metric is important" but then I have to go investigate that and then to truly understand that metric, i have to create an "Everything else Metric" to continue this investigation. Where I think this becomes truly applicable is going to my own freeform table and being able to drop the segment of I am investigating and then be able to have the ability to select the segment, right clicking it, and have an option to negate the segment, which would be the same as "Everyone Else". This would be helpful because I could then do analysis on the metrics actual number and not on the algorithmic number by Adobe. Stakeholders want real numbers, not an algorithmic number. thanks,Mike
It would be useful to be able to have the option to see ranking maintained when applying a filter or segment to a report. With so many pages, we have to do a Data Warehouse export to Excel to be able to search for a page and see how it ranks.
Hello All,I was hoping you could get two things on the roadmap.1. Better documentation around your APIs (Though what you have is a great start) 2. Better responses from your APIs when the WSSE Header is wrong (which, though I'm no expert, I feel was stupid hard "unable to validate" is not helpful).Here's some things that aren't mentioned (Keep in mind, I'm not a network/IT guy, just trying to help):1. Nonce / Digest should be ASCII format when created (not sure if this is 100% correct, but it worked for me)2. Base 64 encoded Digest and Nonce must be DEcoded before sending (this may be common knowledge for some, but wasn't listed)3. When decoding, you have to remove the leading whites pace from the values that are decoded4. The POSTMAN example is a good start, but it would be great if you could explain in more detail what is occurring at each step.5. You don't need a SHA1, you can use any hashing algorithm as long as its sent in the header6. Each parameter value of the header should be a string, not its raw value at each step.7. Give a way to generate the header with hard-coded values (not sure how to work around the timestamp, but it would really help sanity check)8. Headers must be passed as a dictionary (in python)Again, I'm not a developer by trade, so I get there's going to be difficulty. But if you add a few more clear steps, maybe a tutorial video or two on the concepts involved here, everyone will be able to use the tools more effectivelyThese are the things I referenced:python-omniture/account.py at master · dancingcactus/python-omniture · GitHub Gathering the details to make Reporting API requests | Adobe Developer Connection GitHub - AdobeDocs/analytics-1.4-apis: Documentation and helpful resources for calling the Analytics 1.4 Apis Also, here is a quick python 3 example you should upload to your docs:import datetime, pytz, requests, uuid, hashlib, binascii#use this to get your secret dynamically from your normal login credentials#r2 = requests.request(method="POST",url="https://api.omniture.com/admin/1.4/rest/?method=Company.GetLoginKey",data = {"company":"yourcompany","login":"login ID", "password":"password"})Username = "user:company"Secret = "blabalafoobar"Nonce = str(uuid.uuid4())Datum = datetime.datetime.now(tz=pytz.UTC).astimezone(pytz.timezone("US/Mountain")).isoformat()ShaKey = Nonce+Datum+SecretHash = hashlib.sha256(ShaKey.encode())B64Nonce = binascii.b2a_base64(binascii.a2b_qp(Nonce))B64Digest = binascii.b2a_base64(Hash.digest())B64DigestDecoded = B64Digest.decode().strip()B64NonceDecoded = B64Nonce.decode().strip()Header = 'UsernameToken Username="{}", PasswordDigest="{}", Nonce="{}", Created="{}", Algorithm="SHA256"'.format(Username, B64DigestDecoded, B64NonceDecoded, Datum)r = requests.request(method = "POST",url ="https://api.omniture.com/admin/1.4/rest/?method=Company.GetReportSuites", headers={'X-WSSE':Header})
Hi I am one of the people who still use Ad Hoc more than Workspace. I do like Workspace, but there is one main reason for my love to Ad Hoc.When I search within my thousands of segments, it does not matter whether I write "Car sale" or "Sale Car" as search phrase in Ad Hoc. It will find the stuff nevertheless.In Workspace I have to remember exactly what order my segments are named.This is such a big difference for someone playing around with thousands of segments. I do have namestructures on them, but the order can be difficult to recall at times. Did I put the "." before or after "Sweden" for example.Anyway. Please update the workspace search box so that it does this as well as Ad HocMichael
Currently in workspace if you curate a project you have to select specific dimensions, metrics, segments and dates to include. What we would like to be able to do is curate a project to a specific dimension i.e. page but allow users to access any segment they wish.WHat would be even better is if you could just curate segments or metrics to any 'approved' ones.
Adobe Analytics User A is leaving their position. User A has created some segments and workspaces. Some of these workspaces are scheduled to be delivered to multiple people on the first of each month. Today we are able to transfer User A's workspaces and segments to User B, but not the Scheduled Projects (aka the scheduled delivery of the pdf/csv of the workspace).If a new person wants to also receive one of User A's projects on the first of the month, User B can schedule the delivery of the project. If a current recipient wants to be removed from the list, or if the report delivery date needs to change, User B cannot do so. Only the Adobe Analytics Admin can make these changes.It would be great if we could transfer Scheduled Projects from one user to another, just like workspaces, segments and reports.
Now that a working integration between Adobe Analytics and AAM is live (Marketing Cloud Help ), We need the ability to further classify the segments that are available within Adobe Analytics As of now you just get the ID and the name of each segment. Example of needed segmentation. Segment type (Demo,Behavioral,Modeled), Segment Source (1st Party, 3rd Party, CMS, etc), It will aid users in getting to the segments that are interested in faster.
When we delete any segment, it shows the notification that it could have been used in dashboards but it doesn't show the name of dashboards using this segment. Ideally, it should display all the dashboards which are currently using a particular segment so we can easily do segments cleanup whenever required.
Hi, In Adobe Analytics, I tried to get the overall sum of servercalls for all reportsuites together. Currently, I have to download the usage report for each of my 25 reportsuites for every month separately. Then I have to sum up all these numbers to see the sum of server calls of this month. So, if I want to know the servercalls for each report suite for the last year, I have to download it for Januar, Februar, March, ... and afterwards I have to sum up the data from report suite 1, report suite 2, report suite 3, ... It would be great to have an automatic process for this.Thanks and regards,Linda
ProblemI spend a good amount of time onboarding new Adobe Analytics end-users and have failed to develop a solid onboarding process. Adobe has done a good job of adding drop zone guides and tips, however, a lot of the valuable information is scattered throughout the Help and Reference section, YouTube, etc. HypothesisI believe if Adobe developed a standardized onboarding Workspace project, including high-level starter (How To) projects, a data dictionary for standard metrics, quick links to tutorials, etc., I’d be able to streamline the onboarding process. If I’m right, new end-users will not be overwhelmed with the tool, can self-serve at their own pace, and become more engaged through some sort of “gamification” method (i.e. tests to gain advanced access).
It would be extremely useful if we could have an option to add sparklines to tables containing metrics. See the below example. This would enable users to:1. Create workspaces with less tables and visualizations. Allowing for faster and more efficient workspaces.2. Analyze data faster.3. Isolate where we need to dig further faster.4. Reduce dependency on report builder for similar purposes.See below for an example. Let me know your thoughts.
Since minute granularity is available in Workspace, this provides some great insights! However it is a pity that for extracing larger sets of data, this needs to be done manualyl via Workspace. It would be great if you'd enable minute granularity in DWH requests!
In an organisation that is trying to centrally manage and curate workspaces and components, being able to understand and manage who components are shared with is key.Unfortunately, the tool does not current help us do this....With the segment and calculated metric manager there is a column called 'Shared with'. However, it is impossible to filter on this column (in fact you can't even sort by it!)Please can you considered allow us to filter by the 'shared with' column in a similar way to which you can current filter by the 'owner' column?This would be a great help in our management of components
Currently only Admins can share projects within Workspace. I have a customer who would like normal users to be able to share a Project to others within their Group.Could we add a permission/role that could be granted to users so that they can share a Project to their Group, without having to have Admin privileges?
Currently, analysts who want to understand variable settings (expiration, special settings like merchandizing, etc.) either must have administrative access or must rely on documentation provided by others. It would be really helpful to allow a level of access where administrative settings can be viewed but not changed.With more eyeballs on the settings, this could also have the added benefit of catching errors in settings, etc., more quickly.
It would be great to be able to put dimensions and segments into the same free-form table (as you can with different dimensions - after which the table is labelled "mixed dimensions.
It would be great if we could create a custom calendar when creating virtual report suites. Specifically, it would be great if we could create a week ending Friday calendar (which is what I need)
It would be great to introduce "seg-dims" into Adobe Workspace. What I mean by this is the ability to almost folder/group created segments. Current workaround for this is by naming segments 'x: abc' and 'x: def' - then searching for 'x:'.
Webmaster Tools provides great visibility into search performance - full keyword list of terms, with impressions, clickthroughs, average position, etc. This information has become even more valuable as most organic search terms are now blocked. The Webmaster Tools interface, however, isn't fantastic, and the ability to get the data organized and exported properly is frustrating. Google Analytics has helped here - you can link GA and Webmaster Tools, to allow users to take advantage of GA's better reporting functionality. It seems to me Adobe should do the same here - by using the Webmaster Tools API (https://developers.google.com/webmaster-tools/) full keyword data could be brought into the Analytics interface. Granted it isn't integrated with site usage data, but that's still a whole lot better than what is in place now. My guess is almost 100% of clients would want this functionality. Right now, we are running both Adobe and GA in parallel in order to get this reporting functionality, and frankly a lot of our internal users are logging in to GA more and more regularly. In terms of optics, it seems to me Adobe should really care about this. I've been having a lot of conversations with people who are under the impression that "search keywords are blocked in Adobe, but not in Google Analytics". While I know that's not technically true, it certainly appears that way when using the two tools side by side.
Login to Adobe Analytics web interface. Navigate to Admin > Logs.I would like to have an API version of this.Use case: Ability to create tools for GDPR EU law compliance (e.g. AA user from EU able to provide their credentials and receive AA access/usage logs about themselves).
I capture the pageName in an eVar on each page load. The expiration is on the hit. That gives me pageNames in a variety of additional reporting. However I'd like to associate the eVar pageName (and other page attributes stored in eVars such as Channel) with custom events captured on clicks that occur on the page. With the expiration occurring on the page load, the eVar completely misses them. I could use the Minute expiration, but this just isn't precise enough. If people stay on a page longer then I would miss events. Letting it expire at the end of the visit could really confuse things in the reporting even with overwriting. It would work better if the tool had an option to expire on the Next Page Load. That would capture all potential events without worry. As an additional option, Next Hit could be helpful as well.
...just some food for thought :-)I find it really confusing that we have to buy 'Mobile Services' to get access to the marketing link builder capability.It feels like it is just such a fundamental analytics requirement to understand what marketing channel is driving app downloads etc. that it should just be a standard part of Analytics rather than hived off and bundled with a push notification capability (always seemed like an odd pairing!).The website equivalent would almost be like trying to sell the s.campaign/marketing channel variables as a separate add on
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
