Build better products with our product team
The current document for A4T says that every metric is available, including any custom or calculated metrics that are built-in in Analytics. However, when we select the calculated metrics as the primary goal for an activity in Target, the lift and confidence calculations are not available in Target and Analytics.Edit: While this idea is being considered for future, it would be awesome if Adobe can share how to build a calculated metric in Adobe Analytics for confidence interval calculation. I understand that the calculated metric builder has some advanced formula and functions but how to use them for the confidence calculation?
Hi Marketo Team, We have been trying to find a solution for URL links with dynamic parameters (i.e. some of the parameters which use Velocity Email Tokens) which cannot be tracked. Attempting to track them would result on the Email Token code not being evaluated. Will it be possible to have a solution for the same in next updates of the platform. It would really solve major setbacks and help us track leads and their behavior. Thanks & Regards Kushal Arya
We have a few standard Issues configured that we apply to our projects using the Queue Setup. These Issues use custom forms to ensure consistency in the data that needs to be provided, depending on the type selected. For example, in our case we have one for Action Items and one for Status Reports. When the user needs to provide either of these for a project, they simply navigate to the Issues tab, click the new issue button, and select they type of Issue that they need to add. After they select the type of issue, the appropriate form appears. This works great except when we get that one rogue resource that uses the "Add More Issues" link at the bottom of the Issue tab, instead of using the New Issue button located at the top of the Issues tab. The "Add More Issues" link at the bottom of the page does not honor/recognize the Queue Topics that are available for use on the project. Only the "New Issues" button does. It would be so helpful if we had the ability to hide the "Add More Issues" link at the bottom of the Issues tab, at least by Group or Project. It just creates confusion for the users and problems for reporting.
Hello friends, I think everyone who works with Adobe Analytics has run into a situation where we would like to combine the value of two or more dimensions into one value for reporting. If you have an eVar for City and a prop for Country, it would be awesome to be able to combine both to a value like "City in Country", just like a Calculated Metric. If it only works for dimensions on the same hit we would already have a lot of value. Today, I solve this by tracking the value in a combined way and utilize Classification Rules to separate them afterwards. This works for new implementation but does not help for historical data or new use cases. Please vote for this idea if you want it as well! Best,Frederik
Request for Feature Enhancement (RFE) Summary: I'd like to request that the dispatcher flush is done prior to a deployment/pause. This will facilitate testing during the pause. It would be fine to then again clear the cache as it does today when the pair is reattached to the load balancer. Use-case: When testing during a deployment/pause it is beneficial to have the dispatcher cache cleared to ensure we are testing against the current code and not something in the cache. Current/Experienced Behavior: We need to request our CSE to flush the cache during the deployment/pause. Improved/Expected Behavior: Doesn't require the CSE to flush the cache during the deployment/pause. Environment Details (AEM version/service pack, any other specifics if applicable): 6.5 AMS Customer-name/Organization name: NEW YORK LIFE INSURANCE COMPANY Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Localized Reference for Experience Fragment Use-case: We are using AEM 6.4.8/6.5.8 and using experience fragments component in our page templates for header and footer implementations similar to WKND sites. In template, we add experience fragment component with "/content/experience-fragments/us/header" as fragment path and when we create pages in /content/<project>/us/page, we are able to see the US Header. Now we created language copy of the experience fragment to "/content/experience-fragments/fr/header", and now created page under "/content/<project>/fr/page", due to Localization implementations in experience fragment core component, automatically FR header is picked up on the FR page. Current/Experienced Behavior: Now US Team, changed something in US header and planned to publish sometime next week. parallelly FR team changed some page content and when trying to publish FR page, it is showing US Header as outdated as part of References publish.. which is weird. Improved/Expected Behavior: the localization implementations done in core component experience-fragments model (com.adobe.cq.wcm.core.components.internal.models.v1.ExperienceFragmentImpl" also to be done for "com.adobe.cq.xf.impl.ExperienceFragmentsReferenceProvider" so check only for localized references. Environment Details (AEM version/service pack, any other specifics if applicable): https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/reference-for-experience-fragment-not-working-as-expected/m-p/405575#M28658 Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Allow text mode and HTML on home page customizations.
If a person subscribes to a MSI notification through Salesforce, their is no way for a SFDC admin, Marketo admin, or Marketo support to unsubscribe that person from the notification, such as: You are subscribed to Marketo Sales Insight Interesting Moment for "Type: Registered"\n\n When a Salesperson clicks this accidently, they can get 100's of emails, which can block our Marketo notifications, lead to spam filter issues, etc. The only way this can be unsubscribed is from the email link itself, and by that specific user who clicked the notification icon. Please add to roadmap to give a way for Marketo admins to clear these subscriptions. Marketo Support confirmed this old ask article was accurate - 0 way to clear these out: https://nation.marketo.com/t5/product-discussions/unsubscribe-from-an-interesting-moment-alert/m-p/69023#M35890
On a text-based document, I wish there was a way to edit the doc in the proofing area while it is routing through the flow? Similar to change tracking in Microsoft word.
The variables set in the Analytics extension's Global Variables seem to not fire on all rules/rule types (see Global Variables - Direct Call Rule ). This is similar to how it was in DTM.It would be great if we had some control over this (maybe give me the ability to say "fire for all beacons" or "fire for all s.t beacons" or "fire immediately before any beacon, but after other rules" or something), or by default they DID fire anywhere the Analytics Extension was in a rule. Otherwise, folks still have to resort to using doPlugins, or setting up a rule for global variables that somehow fires on all other AA rules/beacons.
Hi, It would be great if marketo could provide ABM tokens to use in emails. A use case that i could think of is to leverage named account while targeting an ABM campaign. Thanks, vineela.
It's getting annoying having the debugger "reset" every time I go back to it.... My workflow will sometimes just be looking at a single page, but other times I'll be looking at a page, checking the variables, going to Confluence or Jira to verify requirements, then I come back to the debugger and it's all collapsed and set to the first column again, so I fix it, put it where I want it, go back to confluence or jira and then have to come back and reset things. The other issue with this is that sometimes I'll be comparing QA against Prod, in the old version (Experience CLOUD Debugger)I could have the network requests appear on the same panel, so I could easily compare my changes in QA against what's in Prod. Also for some reason tables in this version isn't as good as the previous version, not sure if it's the fonts or what.
I have set up one of our request queues to accept issues based on incoming emails. However, it picks up a default Queue Topic (which is the last one used by anyone submitting an earlier issue). I would love to have more controls while setting up the request queue to be able to specify a Queue topic or a topic group. It will help in managing requests (which generally come in 100s/day for this queue I have set up).
The idea is to add the following system information to all notifications emails, doesn't have to be prominent, but at least it enables you to differentiate them. Subscription: xyzData center: lon09Munchkin ID: 123-ABC-456 If you are admin for multiple instances it is currently a nightmare always having to guess where this or that error took place. Also, user invitations - people can not differentiate if they are activating sandbox or production (we're on SSO, so the login IDs are the same across systems).
I was very excited about this feature, but I think it does not provide any value as is. There's never a scenario where I only need to breakdown the top 5 items, so I am stuck in the old method of manually breaking down each second level line item by the 3rd variable for anything beyond 5 items. It would be great if this could be increased to up to 25 at least. Ideally the breakdowns would be applied to the full table (including new values after it is built!) This may be a separate issue, but once I build a table and additional values populate, they are not broken down along with the rest of the table even if they move into the top 5 position. The manual maintenance lift on this is huge.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK