Product Communities

Here are a few helpful tips regarding assigning a record to a queue when using the Sync Person to SFDC flow step:     If the record flowing through the flow step is a Marketo only record a new SFDC lead will be created SFDC Lead any field updates will be synced from Marketo to SFDC and the owner will change to the Queue SFDC Contact a new SFDC lead will be created The value in Marketo for Lead Owner for any records assigned to a SFDC Queue will be empty   Additional resources for learning about the Marketo integration with SFDC.

  The SFDC is Deleted field can be used to identify a SFDC Lead or Contact which used to be in SFDC but was deleted and now only lives in Marketo. Typically the record is deleted from SFDC for a specific reason and most customers will honor the deletion in SFDC by also setting up a smart campaign to also delete the record from Marketo.    If you decide to keep the deleted record (SFDC Lead or Contact) in Marketo to nurture it, the next time the record flows through the SYNC Person to SFDC flow step Marketo will insert it into SFDC as a new lead record. A strategy should be in place to make sure you're not syncing/inserting records you really don't want.   If you decide to delete a SFDC Lead or Contact in Marketo only you should only do it if you have a custom sync rule set-up. Otherwise the next time the record is updated in SFDC it will sync again to Marketo with a new Marketo ID.    Here are the steps to delete a SFDC record which is syncing to

SummarySales Insight Email Performance Report grouped by Sales Rep exports file sorted by template rather then by sales rep.  Issue Sales Insight Email Performance Report grouped by Sales Rep exports file sorted by template rather then by sales rep. Subscription email displays report grouped by email template as wel Report within the Marketo UI will show as expected Solution   The current workaround exists for the CSV exported.            1. Export the report to a CSV          2. Format Columns A (Sales Rep) and B (Email Name) to sort A to Z in order to get a view by sales rep. Root CauseThis issue is scheduled to be addressed and resolved in the 2021 Q2 release Environment Sales Insight for SalesforceThis issue occurs within the subscription email that gets sent out of the report This issue occurs when exporting the report to a CSV file

This tip is for extension developers (most likely applicable for web extensions only, since I haven't tried this with mobile extensions).TL;DR create a "global.turbine" variable to mock the turbine free variable, before running your unit tests.I use jasmine (https://jasmine.github.io/index.html) for testing my extension. One difficulty that I had was figuring out how to test the "turbine" free variable (https://experienceleague.adobe.com/docs/launch/using/extension-dev/turbine.html).After numerous trials-and-errors, I finally stumbled on this solution:describe("description of the test suite", function() { // create the turbine free variable with "logger" global.turbine = { logger: jasmine.createSpyObj('', ['debug', 'info', 'warn', 'alert', 'error']), }; // rest of test suite it("description of unit test that logs to the logger", function() { // run the test expect(global.turbine.logger.info).toHaveBeenCalled(); }); });Hope this works for you too!

Update: Roadmap Updates are now posted at Data Collection Roadmap!As the Adobe Experience Platform has evolved, so has the Launch team and our place within the Platform.  Our portfolio has expanded beyond web and mobile - and now includes Launch Server Side, the Edge Network, the Web and Mobile SDKs, and a bunch of other exciting things.  Our team has welcomed new product managers and engineers.  Our managers have been given new teams to manage.  All with the goal of making it as easy as possible to gather data from client devices and send it wherever you need it to go - Adobe and otherwise.  To reflect this expansion of our scope, we have put together the Data Collection Roadmap to provide broader insight into the things we're working on.  Roadmap updates will be posted on the new page.  We'll leave this one here for the archives and bookmarks.--When the Launch product team receives a feature request, we need to weigh it against all the oth

IssueWhy is there a difference between the Exhausted Count displayed in an Engagement Program Stream vs. a smart list using the "member of engagement program stream is exhausted" filter? SolutionTo account for the difference in a smart list that is displaying a different number of people that have exhausted the content in a stream, in the smart list account for the other conditions the Exhausted Count uses: Engagement Program Cadence of "normal" - this can be included as a constraint on the "Member of Engagement Program" smart list filterThe members were not blocked - this can be included in the smart list by using the smart list filters: member of smart list is not blocklisted, unsubscribed = false, marketing suspended = false, email address is not empty and/or email invalid is false.Have not exceeded the communication limit at the last nurture cast - there is no specific smart list filter for this, so it will need to be manually checked in a lead's activity log.

SummaryThis method can be used when moving a CNAME from an old instance to a new instance. Often at times, when changing to a new instance, this question can come around, and ones would wonder how to do it or a solution on how to do it. This steps will show you the two phases which I will explain below. (Note: This would need to be done before the old instance deactivated) IssueA CNAME needs to be moved from an old instance to a new instance SolutionNOTE: You cannot have the same CNAME in two different instances (Pointing to two instances, e.g. cname1.company.com pointing to instance1.mktoweb.com and instance2.mktoweb.com)  Key terms:CNAME 1 = Initial cname in the old instanceCNAME 2 = Additional cname created in the old instanceINSTANCE1 = Old instance (Instance Name)INSTANCE2 = New instance (Instance Name)   Phase 1:--------------- 1. Create an additional CNAME (a replacement CNAME) which you would want to swap as the default in the second step. CNAME 1 > INSTANCE1

March 2023 update: The deprecation of the legacy URL patterns will occur on August 1, 2023.   June 2022 update: We have decided to extend the deadline until the end of 2022 with support of old URL patterns ending in January 2023. More information to be provided once a precise date has been chosen.   In 2021, Marketo Engage made changes to the URL structure for Landing Pages, Forms, and Images & Files assets. On August 1, 2023 we will be deprecating usage of old URL structures and these references will no longer load on the web.   Why is this change being made? Technical Details Landing Pages Images & Files Forms What customer action is required?   Why is this change being made? When a Marketo Engage subscription is not configured with a branded CNAME, Design Studio assets use a common hostname shared among all customers on the same pod. This behavior can be exploited in a phishing attack where a user cannot be sure a link to a Marketo Engage hosted asset bel

SummaryCreating many-to-many relationships with Marketo custom objects requires an intermediary object with one link to a Lead or Company and another link to a secondary custom object. Here's how to solve the problem of the secondary custom object not showing up to be selected as the linked object. IssueCreating a many-to-many or N:N custom object structure such that a lead or company can be associated with multiple custom objects and a custom object can be associated with multiple leads or companies at the same time. When adding a link to the secondary custom object, that secondary object is not list as an available linked object.    SolutionIf you find that the custom object you'd like to link to is not list in the "Link Object" list, there are two things two check: The secondary CO must be approved.The secondary CO must not have any link type fields. Since it's not possible to change a link field once a custom object is approved, if you already have link fields, the on

Issue-Error editing image in email: “image URL does not exist” or “image URL cannot be found”  Environment-SSL not enabled on Marketo instance-Browser blocks unsecured content SolutionOption 1-Set up SSL for landing pages (Recommended!  SSL should be a baseline configuration for all landing pages and tracking domains).Add SSL to Your Landing Pages | Adobe Marketo EngageOption 2 (Not recommended!   Warning! This is a security risk.)-Allow browser to view unsecured content (can choose to turn this setting back off in the browser after viewing the content)This link below describes how to enable this content in Chrome.https://docs.adobe.com/content/help/en/target/using/experiences/vec/troubleshoot-composer/mixed-content.htmlThis link below describes how to enable this content in Firefox.https://support.mozilla.org/en-US/kb/mixed-content-blocking-firefoxOption 3-Try to use a different browser or try turning off all browser extensions. Root CauseThis issue could be cau

IssueIn Salesforce on the Account level for Marketo Sales Insight, it does not show all the activities of the associated contacts. SolutionMarketo Sales Insight only shows certain activities depending on how recently they occurred on the account level. Interesting moments: last 60 days Web Visit: last 3 days Score Change: last 30 days Email: Everything If you wanted to check activities past these dates you would need to go to the contact level and check the history there. The reason behind this is because at scale if there were 100s of contacts under one account and all contacts are active and creating activities it would be difficult to sift through the activities and may cause performance issues due to the sheer amount of data being displayed which is why this limitation is in place.  

SummaryUnable to update Person Source as expected for records created with the LinkedIn Lead Gen Forms and Facebook Lead Ads integrations. IssueNew records created through LinkedIn Lead Gen forms as well as Facebook Lead Ads results in the records not updating the Person Source field as expected.  SolutionPerson Source may be set to block updates to the field as noted in the example for Block Updates to a Field - Marketo Docs - Product Documentation. To resolve the issue ensure the field is not set to block updates for the desired update method. Alternatively the Person Source values populated by the integrations can be kept and expected values can be updated to include these sources.  Root CauseThe LinkedIn Lead Gen Forms and Facebook Lead Ads integrations automatically update the Person Source to preset values when a new record is created in Marketo through the integrations. Blocking field updates to the field may prevent the value from changing to pre-co

What is Changing?Adobe Experience Platform Launch will soon require that all ports on SFTP Hosts be on the list below (or fall within the specified ranges).212280200-2994432000-2999434380808888ImpactWhen creating/editing an SFTP Host, Launch will perform validation on the Host's port. If the port is not on the list above, the save will fail with an error.If you happen to create a Host with a disallowed port before these changes, once they go into effect, builds sent to that Host will fail.RationaleWe consistently take steps to improve security and reduce our risk exposure. Limiting the allowed outgoing ports is required by our network and security teams to enhance the infrastructure that supports Launch.Why These Ports?When we conducted our analysis, all existing SFTP Hosts on our customer organizations were already compliant with the list of ports above. You will recognize many as commonly allowed incoming ports for corporate firewalls. The listed ranges let us include the other exist

SummaryResult for Smart List using Web Page constraint is greater than the result for the total of conversion on Landing Page Performance Report.  IssueResult for Smart List using Web Page constraint is greater than the result for the total of conversion on Landing Page Performance Report.  SolutionEnsure to append version number to the Landing Page when renaming and ensure each Landing Page has a unique name. Root Cause•             Smart List looks at the information written to the lead’s activity log.•             The Web Page constraint looks at the label and not the ID of the Landing Page.If the Landing Page was renamed, it will show a different result depending what is written to the lead’s activity log.>> Example 1:Lead A filled out the Form when the Landing Page was called LP1.Lead B filled out the Form when the Landing Page was called LP2.S

Questions? Ask Support! Securing your Adobe Marketo Engage Landing Pages By default, Marketo Engage serves domains as HTTP, and historically we’ve given our customers the choice of whether or not to secure their Marketo Engage domains (HTTPS); however, in 2018, browsers enforced new security measures to better protect their users - one of which was to flag all non-secure (HTTP) web pages with a visible "Not Secure" warning (the unlocked pad lock icon in the address bar). This effectively shifted the choice of using secured (HTTPS) domains from a best practice to a requirement. Marketo Engage's Secured Domains solution secures any and all domains defined in your instance so they will be served via HTTPS.  For a full explanation of the benefits Secured Domains provides, in contrast with a basic SSL certificate, please see this Nation Post.   NOTE: As of late 2019, Marketo Engage changed it's pricing/packaging to now automatically include a base Secured Domains package with ALL

If you have submitted a support case and you feel that the case was improperly handled or that the solution being offered does not meet the communicated Marketo support expectations, then we would welcome the opportunity to look deeper at your specific support engagement and work with you on delivering a better resolution.Caution:If the item you're looking to escalate is related to a Production Down incident, please call the support line for your region to receive immediate assistance. Support Manager escalations are only handled during normal business hours. The phone numbers for each region are listed below, follow the prompts for P1:Americas: +1.877.270.6586, Direct: +1.650.376.2303Europe, Middle East, & Africa: +353 (0)1 242 3030, UK: 0800 151 3030Asia Pacific: +61 2 8031 8188Japan: +81.03.4233.9014How to Escalate:Step 1.Navigate to the "Case Management" area of the support portal either by mousing over the Support tab and selecting "Case Management" or clicking the Suppo

IssueYou need to know the version of the munchkin script which is used by a particular web-page. SolutionMunchkin version can be found by following the below steps: Open up your web browserOpen developer console on your browser. Most other browsers use F12 to open developer tools.Visit the page on which the munchkin script is embeddedNavigate to the network tab of the Developer console and search for munchkin You should find two attributes named “munchkin.js” and one of them will show a similar request URL as seen below munchkin.marketo.net/154/munchkin.js The numerical value 154 is the munchkin version. NOTE: If you are not able to finds anything over the network tab, we would suggest that you refresh the webpage which has the munchkin script is embedded on it  

IssueYou need to locate the Munchkin ID for a specific Marketo instance. SolutionWhat is a Munchkin ID? Marketo's custom JavaScript tracking code, called Munchkin, tracks all individuals who visit your website so you can react to their visits with automated marketing campaigns. Even anonymous visitors are tracked along with their IP addresses and other information. The Munchkin ID is the unique identifier for a specific Marketo instance and insures tracked activity goes to the correct instance.  How to find your Munchkin ID  1. Log into the specific Marketo Instance you need the Munchkin ID for. You can verify the instance name by checking the listing in the top left of your browser.   2. Go to Admin and click Munchkin in the tree on the left in the Integration section.     3. The Munchkin Account ID will be the first thing listed in the Tracking Code box.  

IssueYou're receiving an error that states 'Not Allowed - Error approving <asset-name> - {{token-name}} : Token key not found' when trying to approve an email asset. SolutionCheck that token syntax is correctly inserted with no missing left or right 'curly' brackets '{{' '}}'Check that the field name of the token does not have any incorrect spelling (e.g. Email Address)If the token syntax is correct and the field name of the token is spelled correctly, it is possible that the field name of the token contains a Unicode non-breaking space (e.g. between 'Email' and 'Address'). This would have been inserted if it was copied across from a platform that was encoded with Unicode (e.g. Microsoft Word) - To rectify this, delete the space in the token and re-insert it with a normal space using the spacebar on the keyboard. Once this is corrected, the email approval should work.

IssueDiscrepancy between Marketo webinar atttendance and webinar provider attendence report SolutionCompare Webex report with Marketo Program members list to determine which leads are involved.Check to see if the leads involved have the same email address but used different names to register/attend. Workaround: Upload Webex final report to a static list and use the list to update the program attendance.  Root CauseWebex issues two reports, a preliminary when the webinar is finished and a final report approx. 12 hours later, which may have updated attendance info.  Marketo Engage uses the preliminary report to set the attended status in the program and does not update when the final report is released. EnvironmentWebexMarketo Event Program synced to Webex webinarFinal attendance report from Webex, not preliminary

  When a new lead enters Marketo from a form fillout or List Import, Marketo automatically searches for a lead with the same email address.  If that lead exists, the existing lead is updated instead of creating a duplicate. However, Marketo does not automatically de-duplicate leads who are already in your database. This is especially a problem for new customers who often have many duplicate leads in their database. Also, if you add a new lead directly into Salesforce (through the Salesforce import process or web-to-lead forms) Salesforce will create a duplicate lead that gets synced into Marketo. When this happens, you can use Marketo to find and fix those duplicates.   How Marketo handles duplicates   The primary consequence of duplicates is that one lead record could have the most relevant information about that lead while your sales rep is looking at the incomplete duplicate.   For example, say that you have a duplicate lead in your database

Required Profile Permissions for Marketo Synchronization API EnabledManage Public DocumentsManage Public TemplatesEdit HTML TemplatesEdit EventsEdit TasksConvert LeadsTransfer Lead*Transfer Record* Enable Read/Create/Edit/Delete access on the following required Standard Object Permissions: OpportunitiesContactsLeadsAccountsCampaigns (if you choose to enable campaign sync) From the Profile Detail page, click Edit and complete the steps in this section.In the old profile layout the following should help: Enable the following Administrative Permissions: API EnabledManage Public DocumentsManage Public TemplatesEdit HTML TemplatesTransfer Record * Enable the following General User Permissions: Edit EventsEdit TasksConvert LeadsTransfer Lead* Enable Read/Create/Edit/Delete access on the following required Standard Object Permissions: OpportunitiesContactsLeadsAccountsCampaigns (if you choose to enable campaign sync) Click Save to save your changes and return to the Profile Detail

Marketo users can configure Marketo to manage, nurture, and measure leads that are created from Google AdWords. We offer 2 options, depending on what type of web page is linked to your Google AdWords ad. Option 1: Link Google Adwords Ad to a Marketo Landing Page with a Form   This solution does not require custom codingThis solution does not require any additional cost Option 2: Link a Google Adwords Ad to Any Page on your Website This solution does require custom coding so that you can capture the PPC (pay per click) information when the lead comes back 'later' to fill out a form on your pageDepending on whether you have resources internally to do the custom coding, this solution may or may not require additional cost Reporting Available (for both Option 1 and 2) Number of new leads acquired by Google Adwords ProgramCost per new lead acquired by Google Adwords ProgramNumber of leads acquired by keyword/search phraseTop 10 keywords/search phrases which acquired new lead

Common questions around how Marketo can be used to track Google AdWords information:   Q: Do I have to install a special Marketo App from the Salesforce.com AppExchange to get this functionality? A: No, there's no special Marketo App to install.   Q: Will this require custom coding? A: For the first scenario, Linking a Google Adwords Ad to a Marketo Landing Page with a Form, there is no coding required at all. The second scenario, Linking a Google Adwords Ad to Any Page on Your Website, requires a little bit of coding. To help with that, the links to the appropriate KnowledgeBase articles are included in this document.   Q: I can not code, but I still want to capture my Google Adwords PPC information using Marketo. What should I do? A: If you do not have coding experience, it's best to go with the first scenario since it does not require any coding. If you are interested in the second scenario, then we recommend leveraging any internal resources you may have who c

When a Salesforce-specific flow step runs, sometimes extra steps are performed automatically. Here are the rules, so you know: These rules will apply when the lead is not currently in Salesforce.com as a contact or lead. Marketo Flow stepAutomatic ActionAdd to SFDC CampaignSync Lead to SFDCChange Status in SFDC CampaignSync Lead to SFDC Add to SFDC CampaignChange Owner Sync Lead to SFDC Convert Lead Sync Lead to SFDC Create TaskSync Lead to SFDC     You can filter out SFDC records in a Smart List using the SFDC Type Filter with the operator set to "is not empty".  All SFDC records have a value in this field.