Product Communities

Pushing multiple data simultaneously into Adobe Client Data Layer can cause its computed state to return data that you don't expect. Overcome this problem in Tags (Launch) with Direct Calls. Preface / Background Adobe Client Data Layer, commonly referred to by its abbreviation "ACDL", is an event-driven data layer developed by Adobe. This article assumes that you are already familiar with ACDL and know how it works, or even how to use it. Otherwise, learn more about ACDL from its wiki. Like any event-driven data layer, ACDL's implementation is very simple: instantiate its array, then push a data object into that array, like so: // instantiate ACDL window.adobeDataLayer = window.adobeDataLayer || []; // push data into ACDL window.adobeDataLayer.push({ event: "my event", foo: "bar" }); After that, you can retrieve the pushed data from ACDL's computed data layer state. When using Tags (or Launch, as it is more commonly known), then you can use the Adobe Client Data Layer extension's

November 2022     This is a roadmap.  It is not a promise.  It is a snapshot of what we think we can deliver based on our priorities at this current moment .  You should expect things to move around.  New items will be added.  Individual items will move closer and farther when development teams refine scope, update priorities, or otherwise learn that things did not take the exact amount of time that we estimated.  We reserve the right to be smarter tomorrow than we are today. Most recent update: 2022-11-15

If you're using Adobe Client Data Layer (ACDL) in Tags (Launch) and ordering of Rules is important to your setup, then setup your ACDL Events to listen to "All Events" only. Preface / Legend For the rest of this post, I'm going to use specific upper- and lowercase spellings to distinguish various items. Uppercase "Event", "Condition", "Action": these refer to the Events, Conditions and Actions in Tags that come from extensions. For example, the ACDL extension has an Event called "Data Pushed". Uppercase "Rule": this refers to Rules that are setup in Tags. A Rule can contain 1 or more Events (where each Event doesn't have to come from the same extension), 1 or more Conditions, and 1 or more Actions. Lowercase "event": any other event that occurs during your web page's runtime, i.e. when it is loaded and interacted with in the user's browser. "ACDL event": an event that got pushed into ACDL / adobeDataLayer. Background Tags, or Launch as is more commonly known, has a fantasti

Community Members,This post will serve as a collection point for the various blogs and articles around Launch, by Adobe. As your community manager, I will do my best to keep this list updated and organized. If you have suggestions for this page, please let me know.Official Blog:https://medium.com/launch-by-adobe/adobe-web-browser-technology-performance-477c2bfeaa98https://medium.com/launch-by-adobe/none-data-element-storage-duration-a16433791048https://medium.com/launch-by-adobe/data-persistence-from-dtm-to-launch-52d26b834b54https://medium.com/launch-by-adobe/event-detection-from-dtm-to-launch-b4370cc21bb8https://medium.com/launch-by-adobe/launch-library-monitoring-hooks-8495dd91b57https://medium.com/launch-by-adobe/custom-code-event-type-9953b6f3d664https://medium.com/launch-by-adobe/client-side-help-for-gdpr-79e1cbcfc3c2https://medium.com/launch-by-adobe/migrating-from-dtm-to-launch-57548251a86dThird Party Blogs: http://www.stratigent.com/community/analytics-insights-blog/preparing-

This change was released on July 7th, 2020.--We've made a significant update to the Launch browser runtime to add a new capability. This article will clearly describe the legacy behavior, the new behavior, and some things you should consider as you make the move.  Let's dive in!1) Legacy behaviorWhen a rule contains multiple actions, Launch will call those actions in the same order that you have them organized in the interface.  In this example, Launch will call Action A, then Action B, then Action C.What Launch does not do is wait for Action A to finish before it calls Action B. If Action A is synchronous, then it doesn't matter much. But if Action A is asynchronous, then Action B probably starts to run while Action A is asynchronously carrying out its task. Over the long-term, we'd expect to see that sometimes Action A finishes before Action B, but sometimes it finishes afterward. The same is true for Action B

IssueYou want to understand how Company IDs work within Marketo and how you can interact with these IDs, particularly when dealing with the Person's Company Object. You want to know: The nature and standard of the Company ID in Marketo.Can the Company ID be checked or modified by users without CRM or API integration?If people belonging to the same company share the same Company ID.How to update the Company Object information via the API for multiple leads associated with the same company?Clarification on which field should be used as the basis for updating Company Object information. SolutionMarketo manages Company IDs using two distinct identifiers: Company ID: This is a Marketo-specific identifier that is used to organize the link between companies and people within Marketo.External Company ID: A hidden system field used in non-native company object integrations. The Company ID can be accessed through the {{company.Id}} token, while the External Company ID is not directly viewable

MobileSDK – CDP: Data Refresh StrategyAuthors: Meera Ankam, Raminder Singh Bagga IntroductionIn mobile app development, ensuring data accuracy and completeness is crucial. Mobile SDKs capture user interactions and other relevant data, but transmission failures can lead to incomplete or lost batches due to network issues, server downtime, or SDK bugs. Reingestion mechanisms retransmit failed data batches to prevent data loss.This blog presents strategies and best practices for reingestion to effectively manage and mitigate the impact of failed batches from Mobile SDKs to the Edge Network and into the Adobe Experience Platform (AEP) Dataset.Real World Customer ExampleBackgroundWe're diving into a strategy guide on re-ingesting failed batches using Adobe Mobile Edge SDK for data collection. Many of our customers rely on this SDK to construct XDM (Experience Data Model) on the client side, ensuring consistent data structure and interoperability across Adobe Experience Cloud solut

IssueThere are discrepancies in the leads activity logs within Marketo, where the Email Delivered activity timestamp is sometimes recorded a few seconds before the Email Sent activity. This sequencing issue causes confusion for analytics teams, particularly when using external analytics platforms like Tableau, as the logical sequence would typically show that an email is sent before it is delivered. SolutionUnderstanding email statuses and utilizing Campaign Run ID for analytics: The confusion arises from a misunderstanding of how Marketo logs email activities and the meaning behind the statuses Sent and Delivered.   Email Sent Status: In Marketo, when an email status is logged as Sent, it indicates that the email has been considered for sending or queued for sending. The status does not mean the email has been physically sent through the servers but rather is prepared to be sent. The logging of this event happens shortly after the email is queued, which could be almost instan

IssueMultiple alerts are sent from the same campaign.  SolutionRecognize that Send Alert functions at the person level, triggering an alert for each individual in a campaign. Utilize Marketo's reporting to send a consolidated notification: Create an Email or Campaign Performance report.Tailor the report settings for the specific campaign.Schedule the report to be sent after campaign completion. This method provides a summarized notification, avoiding the repetition of alerts per campaign member.  Alternatively, use Send Alert for individual notifications where needed, such as: Alerting a lead owner of a form submission.Triggering personalized alerts for specific lead activities.  

IssueFiles uploaded to Marketo's Design Studio, like PDFs or image files, are assigned an HTTP URL instead of HTTPS. This discrepancy can trigger security warnings in emails, as modern browsers and mail clients expect secure links that match the SSL certificate's domain.  SolutionTo address this issue, follow these steps: Ensure you have a custom landing page rather than the default domain. See under Admin > Landing Pages.Apply an SSL certificate to any new domains added. Marketo won't do this automatically. You can contact Marketo Support to request an SSL application for your domain. Provide necessary details.After SSL implementation, send test emails to check for proper HTTPS encryption and the absence of security warnings.   By implementing these actions, asset URLs and landing pages in Marketo communications should be secure.

IssueLearn how to design smart campaigns using triggers and filters within the same campaign. Create a campaign that reacts to several different initiating actions or conditions, such as a change in lead status, form fills, or change in data values. Find out whether triggers and filters can be used together, how to combine them effectively, and how to apply advanced filter logic to achieve the desired workflow.  SolutionMarketo allows the combination of triggers and filters within a smart campaign. Triggers are considered as initiating events that start the campaign, while filters are used to further refine the selection of leads based on specific criteria. Triggers are always evaluated with an OR logic, meaning if any trigger event occurs, the campaign will consider it for further action. Filters, on the other hand, can be evaluated using AND logic, OR logic, or advanced logic, depending on the requirements. Steps for smart campaign configuration: Combining triggers and filters:

IssueLeads were uploaded into Marketo with the wrong opt-in date and time, which also synced with Microsoft Dynamics 365.  SolutionTo correct the opt-in date and time, do the following.Update information in Marketo. Prepare and upload a corrected list for the leads.Confirm the opt-in field in Marketo is not blocked from updates. CRM Sync The corrected data in Marketo will auto-sync with Dynamics 365.If auto-sync fails, manually update the opt-in dates in the CRM. Additional Steps Check for any automated actions triggered by the wrong data and rectify them If needed.Confirm data accuracy in both systems after updates.Back up data before mass updates to prevent data loss.  

SummaryWhen attempting to approve snippet error Access Token is Invalid appears. Have the customer sign out and sign back in. Seems maybe they got logged out somehow. IssueWhen attempting to approve a snippet you receive  "Access Token Is Invalid" error. SolutionThe error can occur when your internet browser logs you out of Marketo in the background. To resolve, sign back in to Marketo and retry the approval. 

IssueNew leads created through form submissions in Marketo are not being registered by the "Fills Out Form" trigger in associated campaigns. SolutionTo address this issue:Verify Referrer Value:You'll see a referrer value in the Fills Out Form. Confirm that the referrer value in the Fill Out Form activity aligns with the campaign trigger criteria.Check Configuration Changes:Inspect any recent changes to URLs that may affect form submissions.Communicate these changes to the Marketing Operations team for proper adjustments.Review Campaign Setup:Ensure the campaign is set up to include the specific form and that no filters exclude new leads.By following these steps, you should be able to resolve the issue and have new leads correctly trigger the Fills Out Form activity in Marketo campaigns.

IssueWhen attempting to move a folder with a program into a different workspace, the below exception is thrown:Rule is incomplete, '<Field Name> is...' requires valueIn the below example, the field name is 'New Status ID':  SolutionThis exception is thrown when a smart list within the Folder contains an incomplete filter. To resolve, you can either:1. Remove the Smart List filter that is incomplete2. Set a value for the Smart List filter

IssueWhen using Interactive Webinars, if a host changes the layout, previously on-camera speakers must switch on their cameras again.Is there a way to keep the camera always on when you move from one layout to another? SolutionThis is not supported due to privacy concerns. If a video pod is not present in a layout, the camera is turned off. If a video pod is present in the next layout again, the presenters need to switch on the camera again to consent to their video being shown again to everyone.There however is a workaround to this. A video pod can be placed on the poll pod layout but it can be positioned so that it is behind the poll pod.The size of video pod does not matters on this layout so it can be reduced so that it is completely hidden behind the poll pod. This way the video pod will be hidden and not visible to participants but since the video pod is present, the camera will not be turned off on this layout.On switching to the next layout (Intro), presenters will not need to

IssueYou may see the error "Program with name already exists" when saving a program name, and this is because Marketo requires each program name to be unique.There may be a scenario where you are trying to re-name an existing program to correct capitalization. (For example, your program is currently called "Test program" and you want to re-name it to be "Test Program", but you get this error message.)  SolutionAs a workaround to resolve this:1) Re-name your program with an extra character at the end, essentially to temporarily make it a different program name2) After that, re-name the program back to your original desired program name and it will save

(Disclaimer: The following recommendation is based on my personal experience with actual client setups. It is not endorsed nor recommended by Adobe or any of its partners.)I'm sharing this scaffold for using Adobe Web SDK to send events for Adobe Analytics to consume, with Adobe Client Data Layer (ACDL) as the data layer and Adobe Experience Platform Tags (a.k.a. Adobe Launch) as the tag management system.The full gist is at https://gist.github.com/yuhui/0cb20fdcc21a03357c4a217edc58d63a. I've listed out the minimal set of:extensionsdata elementsrulesthat need to be set up in Adobe Launch to enable complete tracking of your website's usage data to Adobe Analytics via Web SDK + ACDL, i.e. your website with Adobe Launch -> ACDL -> Web SDK -> Analytics.Hopefully, this scaffold is useful for those of you who are getting started with implementing Web SDK for Analytics, or migrating from Analytics' AppMeasurement to Web SDK.If you find any errors or have any comments, please fee

We would love your feedback on the attached documentation in the next 1-2 months while we are awaiting the final feature. Please reply to this thread and let us know what you like and what improvements can be made. Thanks!

When configuring a click event in Adobe Experience Platform Launch, there is a setting that is commonly referred to as “link delay”. This is a complex piece of functionality that is not well understood. Today I want to demystify this capability. I will explain what it is doing, potential issues that you’ll face, and some workarounds for those scenarios. What it does The first thing of note is the element definition. Link delay will only trigger at runtime if your defined selector is a link element (an <a> tag). It will do nothing for any other types of elements. The next thing to know is what happens at runtime when you turn this on the link delay. When a click event is triggered on a link element that matches your selector definition, the Platform Launch runtime will: Call the event.preventDefault(); function - this has the impact of preventing the browser

On the Launch team, we consider openness and transparency to be items of high value. One of the requests we’ve heard from many customers is that you don’t really know what you’re getting when you install a new extension from the catalog. This is of less concern for mobile extensions since the source code is available through package managers and part of the compiled apps. But in a browser, it’s much more dynamic and harder to know what you’re getting.  JavaScript can dynamically inject more JavaScript and do many other things. Many of our users in industries with heightened security and privacy concerns have strict requirements around the code that is allowed on their sites. For users in this situation, extensions provided by 3rd parties can be a risk vector that must be accounted for. Some use

IssueWhen retrieving result sets from the /rest/v1/activities.json end-point using a Paging Token, the result set returned by the API appears to be less data than what is in the Marketo UI.In this scenario, we're going to explore how and why Paging Tokens work when utilizing them in REST API calls. SCENARIOSay we wanted to grab all 'Send Email' activities (activityType = 6) that have occurred since 2024-04-12T12:00:00Z, and we're planning to pull these activities every two hours, and increment our paging token every two hours prior to making the /activities.json call to obtain the latest data. Current TimeApr 12, 2024, 8:00:00 AM (MST) == 2024-04-12T14:00:00ZWhat We Want1. Retrieve all Send Email activities SINCE  Apr 12, 2024, 6:00:00 AM (MST) == 2024-04-12T12:00:00ZWe would start by retrieving our Paging Token with the sinceDateTime parameter = 2024-04-12T12:00:00Z: /rest/v1/activities/pagingtoken.json?sinceDatetime=2024-04-1

SummaryLearn how to resolve the issue where Marketo only recognizes the first LinkedIn Lead Gen form and does not recognize any additional forms. IssueMarketo only recognizes the first LinkedIn Lead Gen form and does not recognize any additional forms. The problem persists even after disconnecting and reconnecting the LinkedIn account with Marketo. SolutionTo resolve the issue where Marketo does not recognize multiple LinkedIn Lead Gen forms, follow these steps:  Verify submissions:Ensure that each LinkedIn Lead Gen form has at least one submission. Marketo will not display a form in the dropdown lists for triggers or filters unless it has been filled out at least once.  Preview and test the form: Go to the LinkedIn campaign and use the ad preview feature to fill out the Lead Gen form yourself. This step is necessary for Marketo to recognize and sync the form.  Check for form activity: Once the test submission is complete, check the activity lo

SummaryLearn how to monitor the synchronization status between Marketo and Salesforce to ensure data consistency and operational efficiency. IssueYou want to check the Salesforce sync status to maintain data alignment and workflow effectiveness. SolutionMarketo now offers a user-friendly, built-in tool to monitor the Salesforce sync status. To use this tool: Log into Marketo.Go to Admin > Integration > Salesforce.Click on the Sync Status tab.

When Launch was still in the planning phases and we were first figuring out how extensions would work, we realized that Launch users were going to want to have private extensions.  Private extensions can be installed and used on a property like any other extension, but they are only available within the company that owns the extension.  Nobody else can see it.In order to deliver this feature, we need to make a few tweaks to the way that Extension Developers test their extensions prior to release.  These changes will put you as developers in full control of the lifecycle of your Launch extension.If you are (or want to be) a Launch extension developer, please keep reading for some important info. Also, please come join fellow extension developers and members of the Launch engineering team in the Launch Developers Slack workspace (click here to join).If you're a Launch user who is anxious to use Private extensions, stay tuned for updates, the Release Notes will probably you