Welcome to the Adobe Experience Platform Community! Connect with peers to ask questions, share best practices, explore release updates, and contribute ideas that shape the future of Adobe Experience Platform.
最近はアクティブ
We were previously doing our setup on mobile services and now I'm creating our app events on report suite, including the processing rules. Some of our events are elapsed time between actions but Im not sure witch condition is the correct one to choose. For clicks I´ve been usinga.action(context data) What is the correct one for elapsed time? Would it be a.action.time.total(context data)?? thank you in advance
Use this thread to ask any questions related to the Experience League LIVE session titled, "Ask the experts: Useful extensions in Tags (Launch) to help super charge the Web SDK." Experts are monitoring this thread to ensure your questions are answered. Thanks and we hope to hear from you!
Hello all, It seems that listVars are not automatically mapped to Analytics when ingested from the Adobe Edge. _experience.analytics.customDimensions.lists.list1.list = [ { value: 'a' }, { value: 'b' } ... ] This validates just fine in the dataset, but "list1" in Analytics doesn't get any love. Is there a plan to automatically map list variables? In lieu of that, is my only option to send the value as a single comma (or whatever delimiter is configured) separated string (encoded of course) as non-XDM data and map it manually in the Processing Rules? For example:data: { list1: 'abc,def, ghi' }, then map "a.d.list1" in the processing rules to my real listVar1? Or am I missing a secret hiding place in the standard XDM _experience namespace that can do this for me easy peasy?I did see something odd in the documentation that made me wonder... https://experienceleague.adobe.com/docs/experience-platform/sources/connectors/adobe-applications/mapping/analytics.html
Are you using the Akamai hosting option for your Launch libraries? If the answer is yes, then this post is for you!We have been working with Akamai to implement cache control headers on DTM and Launch libraries. This functionality is now in production for both Adobe and Akamai. This means that all production libraries hosted on Akamai will now have a cache request of 60 min included in the header. However, this still a request and is up to the browser to respect the request.Previously, we were not setting the cache control request, so browsers would make their own caching decisions, which lead to unexpected results occasionally.If you are using Launch, there may be action required to fully deploy this feature. Your production library will have a request of 60 min without any action on your part. However, development and staging libraries for Launch will need to have either "-development" or "-staging" in their filename. If they do not, their cache control will be set to 60 min instead
Hey guys!the person who did the starting setup in some of our sites created specific rules to track some button clicks (using CSS) - including the evars (page name, page URL, report suit, and click text (%Event Text Content%) and in the data element part created one called "Click Info - Click Text" where I believe collects the text of the button. However, now that I´ve to create new ones, I realized that we have buttons with the same CSS class (our system is the low code ones), and also the same texts.. So I don't really know specifically which button was clicked. In this case they are all in the banner slider but some are in other parts of the website.How can I know specifically what buttons were clicked in this case?
Use this thread to ask any questions related to the Experience League LIVE session titled, "Ask the experts: Useful extensions in Tags (Launch) to help super charge the Web SDK." Experts are monitoring this thread to ensure your questions are answered. Thanks and we hope to hear from you!
Hi All, I've integrated query service with DB visualizer client and querying dataset. But it gives me syntax error. Query : Select * from my_dataset Error : [Code: 0, SQL State: 42601] ERROR: line 1:28: mismatched input ',' expecting {<EOF>, '.', '[', 'AT', '+', '-', '*', '/', '%', '||', '::', '^'} Query Service log : To check this issue, I've integrated query service with HeidiSQL client and executed the same query successfully. Thanks.
hi, I have an existing Connection under source, since option to delete that connection in not available in UI, how can we delete any existing connection ? (Fig1) How to delete any a folder under a connection and retain other folders, Need to backup(fig2) Couldn't find any related explanation under "Source Connectors Guide" https://experienceleague.adobe.com/docs/experience-platform/sources/home.html?lang=enin Fig1: Fig2: Thanks,Sandeep
Hello, I'm implementing the following use case and I'm stuck with the AEP Edge segmentation. The use case : As a web visitor, browsing three different products pages should trigger a banner on any page of this web site. The banner disappears as soon as the visitor clicks on it or buy a product, otherwise the banner is visible for 30 days. The ecosystem I work with includes: AEP and Adobe Target Premium. My approach is to detect distinct product pages browsed by the visitor, and provide them toward the XDM Experience Event based schema inside a property (string array type based) created for this purpose: This array is filled with an alloy("sendEvent") call from a script included inside the <head> section by Target. Checking some profile confirm the array is filled with up to three product page URL successfully: Then I would like to create a realtime segmentation which detects when the XDM Event schema string array contains at least 3 entities i
Description - A simple query takes an unexpectedly long time to complete. See examples below. This indicates that AEP Queries is just not ready for widespread, "production" use, really. Why is this feature important to you - 99% of writing a correct, working query is figuring out the way to write it. This requires a lot of iteration from a simple "SELECT * FROM table" to the final query. Querying speed is especially important here, so as to help the analyst improve upon the query until the final one is obtained. Any time spent waiting for a query to complete is time that could have been used to more productive use. Without this speed increase, Adobe can expect all of its AEP customers to flock to Google BigQuery and never look back. How would you like the feature to work - Improve the querying engine's processing from minutes to milliseconds. Current Behaviour - See examples. SELECT * FROM table LIMIT 10; --> 2.5 minutes SELECT * FROM table WHERE table.eventType = "something"
Why do these queries throw the same error in Queries? SELECT * FROM table WHERE table.eventType LIKE "purchases" LIMIT 10; SELECT * FROM table WHERE table.eventType = "commerce.purchases" LIMIT 10; Error: ErrorCode: 08P01 Unknown error encountered. Reason: [Column 'commerce.purchases' does not exist. Did you mean one of the following? [... list of table column names ...]; ...] abfss://gen1@sndbxsomethingsomething.dfs.core.windows.net/platform/alphanumericID Yet when I run "SELECT * FROM table;" I can clearly see "commerce.purchases" in the "eventType" column.
HiWe are receiving security errors in Google Play Console in the SDK, see screenshot aboveWas there a patch that fixes this before? Thanks
Description - Strangely, there is no vertical scrollbar in the data governance table. Why is this feature important to you - The table almost always has a loooooooong list of rows. Scrolling with a scrollwheel is ridiculous (and noisy!). Scrolling with a trackpad is likewise ridiculous. A scrollbar allows the user to control how fast/slow to scroll, allowing for easier manual eyeballing of the row items. How would you like the feature to work - Show a vertical scrollbar in the data governance table. Current Behaviour - There is no vertical scrollbar in the data governance table.
Description - It looks like the dataset preview overlay has been designed for large monitors and/or large resolutions. However, on a standard laptop screen, the preview overlay's table needs a lot of scrolling, and that causes the table's headers to be gone from the view. Why is this feature important to you - There is a lot of unnecessary scrolling to identify the column names (need to scroll up and down repeatedly). How would you like the feature to work - Freeze the table headers to the top of the table, so that scrolling down still allows the column headers to be seen. Current Behaviour - see screenshots:
Description - Schemas that are in use by datasets cannot be edited directly. This contradicts https://experienceleague.adobe.com/docs/experience-platform/xdm/schema/composition.html?lang=en#evolution . Why is this feature important to you - Descriptions add human-readable metadata about what the schema is. While the schema might not change, including its name, there could be some wordings in the descriptions that need to be updated from time to time. How would you like the feature to work - Allow editing of descriptions directly, as expected. Current Behaviour - Schema descriptions cannot be updated without temporarily changing the schema name too, i.e. Edit the schema. Change the schema's name. Update the schema's description. Save the schema. Edit that same schema. Revert the schema's name to its original name. Save the schema. Notice the additional extra steps needed.
Hi Everyone, We have a service setup within Data Science Workspace (and models and a query) all produced by someone that no longer has access to our instance of AEP. As a result the service (training and scoring) and the query they wrote--that are scheduled to run every week--are failing due to authentication/access errors. Is there a way to assign the service/query to a different user (or a generic user)? Or does the entire process need to be recreated with a different user? It seems like there should be a more generic way to set these up as people may come and go? Thank you in advance for any ideas!
What's the best practice now for creating Datastreams in relation to the development environment (i.e. development, staging, production)? I remember that when Datastreams were first introduced, creating a single datastream would result in 3 datastreams, 1 for each development environment. All 3 datastreams retained the same datastream ID, though the development and staging ones had ":dev" and ":stage" appended to their IDs respectively. But now, when I create a datastream, I end up with just 1 datastream. Does this mean the best practice now is to create separate datastreams -- that end up with different datastream IDs -- for each development environment?
We would like to update only the event trigger from Page bottom to window loaded for around 2k rules. Is there a more manageable way to do that over manually updating each rule?
In our company, we have more than 20 websites/apps that were set up by a consulting company. However, their devs set up each product in different ways (some used code, some extensions, etc). In one product in particular instead of adding the name of the report suit into the adobe analytics extension in the data collection platform, the dev added %Report Suit%: (I don´t know why I cannot add the image here but here is a link to it) https://ibb.co/yd05L2N This is the only setup that doesn´t contain the name of our product´s report suit and I have no idea why considering the website has 2 report suits, one for production and one for development stages. Can someone explain please what is the difference between using %report suit% instead of "name of the report suit"? what is the best practice? In case I change the report suite in the analytics launch extension, would this cause any major issues to the setup? the debugger recognizes the correct report suit name tho.
Hi Team, I have few queries regarding data science workspace How are the files and folders hierarchy of a model/recipe structured? How does a run work (either loading, training, scoring, evaluating, or writing process)? Including: Which class calls which classes? In which order are they called? 3. In what data type should the input parameters be in each class?
Original article Feature Flags or Feature Toggle is a common practice used by developers. It allows to deploy specific functionalities in an incremental manner and only enable them when needed. In the tagging world feature flags is a little-known concept. Most of the time a standard tagging release will consist of creating the tag, testing it with the tag management system dev endpoint then publishing it to production. This means that sometimes the release timing is crucial as it needs literally to be done at the same time as the new platform feature has been released to production so it does not impact user experience. What are feature flags? Feature flags are a development concept that allows to wrap a functionality inside an if condition that checks a specific variable value. This variable is usually a Boolean, so the possible values are either true for enable my feature or false for disable my feature. This allows the development team to deploy
Will analytics data continue to flow when Ver4 SDK is retired on 31Dec2022?
Hi everyone,What's the purpose of firing _satellite.pageBottom() code right before closing </body> tag? I debugged the satellite library and found out that it's fired automatically just before DOMReady event.D.domReady(function () {D.domReadyFired = !0, D.pageBottomFired || D.pageBottom(), D.firePageLoadEvent("domready") })Can someone clarify why the code is so important?Thank you!
Welcome to the 1st edition of the Adobe Experience Platform Community Lens! Adobe Experience Platform Community Lens is like your community bulletin board highlighting the latest updates from the Adobe Experience Platform Community in one place. In this edition, we are sharing updates from July 2022, including, the most viewed Adobe Experience Platform content on Experience League, as well as the latest product releases, upcoming and past learning opportunities, and a lot more! Adobe Experience Platform Community Lens LATEST RELEASES Learn about all the new capabilities, upgrades, improvements, and fixes that were included in the latest release for Adobe Experience Platform: Dashboards: Adobe Experience Platform provides multiple dashboards through which you can view important information about your organization’s data, as captured during daily snapshots. Data collection: Adobe Experience Platform provides multiple dashboards through which you can view important information abo
Hi All,I am trying to retrieve the mcid using visitor api, I just want to understand a couple of things.1) When the getMarketingCloudVisitorID method uses a callback(var mcid = s.visitor.getMarketingCloudVisitorID(cb)) to return the mcid compared to not passing the callback(var mcid = s.visitor.getMarketingCloudVisitorID()). Reason for asking is, s.visitor.getMarketingCloudVisitorID() without callback returns mcid most of the times when I am not clearing my cookie and cache before loading the page. 2) Is there any chance the mcid generated in the user machine matches with any previous mcid(returning user), in case the user clears the cookie and cache in the second visit.ThanksShinov
すでにアカウントをお持ちですか？ログイン
アカウントをお持ちではありませんか？ アカウントを作成
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
