Product Documents

Sort by:
In January 2021, we released the Submit Form API endpoint to give Marketo Engage integrators the ability to submit to Marketo Forms through a supported and authenticated REST endpoint. Thanks to customer feedback we were able to identify a lack of parity for critical functionality such as correct handling of duplicate records and support for Program Member Custom Fields. These issues blocked some integrators from successfully onboarding onto the Submit Form API endpoint.   In our August release, we have enhanced the Submit Form endpoint to handle duplicate records the same way as Marketo forms. When there are duplicate records that match an email address submitted to the form, the endpoint will update the record with the most recent Last Modified Date.   In our October 22, 2021 release, we plan to release support for Program Member Custom Fields for the Submit Form REST API endpoint. We understand that integrators will need time to update and test these new changes before they can fully onboard onto the Submit Form endpoint. To allow additional time for migration, we are delaying blocking programmatic POSTs to the /save2 endpoint to our January 21, 2022 release. This will be the final extension.   Programmatic submissions to our form endpoints remain unsupported despite this delay. Please work to update integrations submitting via this method to one that is supported: Marketo Engage forms on Landing Pages or using the embed code, our Forms2.js API, or the Submit Form API endpoint.   Previous announcement: https://nation.marketo.com/t5/product-documents/updated-april-2021-upcoming-changes-to-the-marketo-engage-form/ta-p/306631
View full article
Apple recently announced new features in their upcoming iOS and macOS releases which are designed to protect data from third parties. A broad set of FAQs on the potential impact can be found on  Adobe Experience League . We have provided an additional set of Marketo Engage-specific FAQs below. Since the new features have not yet been released by Apple, much of the information below is speculative. We plan to post updates as we learn more, so please stay tuned.   UPDATE: iOS 15 is now generally available on both iPhone and iPad.  We have conducted tests using iPhones running iOS 15 with Mail Privacy Protection enabled.  Please see updates to this FAQ below (in red).    Will this impact email open-tracking in Marketo Engage?   Highly likely. Early reports suggest that the open-tracking pixel contained in Marketo emails may be obscured and downloaded as a background process, irrespective of how you interact with the email. It is possible that an email open could occur without opening the email, which could artificially inflate the number of email opens. Also, the timing of when an email open activity is generated could be impacted since it may be decoupled from the actual open.   UPDATE: Yes, we confirmed that unopened emails can trigger an email open activity.   Test Methodology We used a batch campaign to send a test email to 5 testers with Mail Privacy Protection enabled on their iPhones.  We instructed each tester to not open the email and then waited 1 week before checking results.  Create a static list of test leads Create a batch campaign to send an email to members of static list Run campaign once Wait for 7 days and inspect campaign results   Observations After the 7 day wait, we found that 3 of the 5 unopened emails had open email activities logged in Marketo.  These activities were “machine-generated” due to a background load of the open-tracking pixel that occurs when Mail Privacy Protection is enabled.  For the 3 machine-generated opens, we found that 1 occurred within minutes of delivery, and the other 2 occurred several hours after delivery.    We then had testers go ahead and open the delivered emails.  For the 2 emails that did not machine-generate an open,  we found 2 email open activities were logged as usual.  For 3 emails that did machine-generate opens, no additional open activities were observed as expected.  This is because Marketo only ever records a single email open activity for any given campaign/mailing/lead combination.   We ran same test with Mail Privacy Protection disabled and did not observe any machine-generated opens.   To summarize: When Mail Privacy Protection is enabled, some delivered emails will have machine-generated opens, and the timing of when machine-opens occur is unpredictable. When Mail Privacy Protection is disabled, no machine-generated opens occur. Will this impact email link click tracking in Marketo Engage?   It is unlikely that tracked links will be impacted.   UPDATE: No, we confirmed that click email activities are logged as expected.  No change here.   Which product areas within Marketo Engage might be affected?   While there is no immediate impact right now, here is a quick look at the potential areas of impact within Marketo Engage.    Assuming that email opens may not be accurately trackable in the native Mail app, and that a user’s IP address will be altered by the native Email app and the Safari browser, we have identified the following areas of potential impact.   Activities It is hard to predict what the impact will be on the “Open Email” activity. For example, if the open-tracking pixel request is generated even though the email is not actually opened, then email opens could be overcounted. Also, the time of the open-tracking pixel request could differ from the time of the actual email open. Finally, there are activities that contain a “Client IP Address” attribute which may not be as accurate as before (Visit Web Page, Fill Out Form, Click Link, Unsubscribe Email).   UPDATE: There is no way to identify which open email activities are machine-generated, and which are not.  Machine-generated opens will likely increase the overall number of opens, but by how much is hard to know.   The User Agent on iOS15 has changed to simply “Mozilla/5.0”.  Since some activities contain metadata that is derived from User Agent, some of this metadata has changed (Platform, Device, User Agent, Is Mobile Device).   Open Email Activity - Before iOS15 Open Email Activity - After iOS15   This could impact your smart lists should they leverage these attributes as constraints.   Here is an idea that could help provide insight into iOS15 adoption.    First, build a smart list that looks for leads that have opened email using an earlier version of iOS. Since at the time of writing, iOS15 is only available on iPhone/iPad, we limit results to those devices only. Click on the People tab and record the number of list members (in lower righthand corner). Next, add another filter to smart list for leads that have opened email using iOS15. Since at the time of writing, iOS15 user agent is "Mozilla/5.0", we limit results to that browser only.  This provides the list of leads that have opened email using a prior version of iOS and using iOS15 in past 30 days.  Click on the People tab again and record the number of list members. You can then compare the two results and gain insight into iOS15 adoption.     Here are some of our test results over the past 30, 60, and 90 days. Date of Activity (in Past) 30 Days 60 Days 90 Days Device iPhone/iPad 23,723 38,901 52,964 Device iPhone/iPad & Browser Mozilla/5.0 1,160 2,621 3,444 iOS 15 Adoption Rate 4.9% 6.7% 6.5%   From this list, you can inspect the lead activity history and identify when a lead switched over to iOS15. Your mileage may vary!   Reporting Email opens can be inferred through email link clicks without the open-tracking pixel being activated, but reporting may be impacted. The “Opened”, “% Opened”, and “Clicked to Opened Ratio” columns in  Email Performance Report  columns may contain less accurate data. Also, any open-related measures or fields in Revenue Cycle Analytics  Email Analysis Report  may contain less accurate data.     UPDATE: There is no way to identify which open email activities are machine-generated, and which are not.  Machine-generated opens will likely increase the overall number of opens, but by how much is hard to know.   A/B Testing If you use  Opens as Winner Criteria , then test results may be impacted since this criteria relies on accurate email open tracking.   UPDATE: See Reporting (above).   Web Personalization The “Location” and “Industry” firmographic  Web Segments  may not match as they had before. This is because the segment attributes are derived by doing a lookup using the client IP address.   UPDATE: See Inferred Fields (below).   Inferred Fields Since client IP address may not be as accurate, Inferred Fields may be impacted.  Send In Recipient Time Zone  can use inferred fields to calculate time zone (as a fallback when known location fields are not populated).  Lead to Account Matching can also use inferred company name field in matching logic. UPDATE: The client IP address behavior on iOS15 has changed.  To allow users to hide their IP addresses from websites and network service providers, requests now go through an Apple proxy server. The proxy server assigns an IP address from a pool of users grouped by their approximate location.  As a result, the location information stored in Marketo inferred fields will be less precise.  Best practices for using inferred data can be found here.   As a Marketo Engage user, what can I do now to prepare for this change?   Review your usage of product areas described above and assess potential impact. Reduce dependency on email open rates. Look for activities from the click onward to measure engagement. Think about how you measure success of your email campaigns and how email opens fit into your overall methodology. Gather device and OS data to understand potential impact. This can be done using either Email Insights or Smart Lists as described  here .   UPDATE: Reduce dependency on email open rates.   As a Marketo Engage user, what should I be thinking about in the future?   Email opens are not the most important indicator for measuring success of your email campaigns. Email is the vehicle by which you drive your customers to a landing page to convert via filling out a form or other action. Web page visits, link clicks, and form fills are the high value activities that you should concentrate on.     Geographic and firmographic data based on client IP address lookup is not entirely accurate since many IP addresses return data for the Internet Service Provider instead of the actual user. In some cases, an IP address lookup will return no data at all. An alternative could be to use a third-party data enrichment service.     Privacy changes are transforming email as we know it. Changes to proxies, location data, and blocked email opens present new challenges to email measurement. Here are Deliverability resources that may prove useful to address those challenges:   Optimizing Marketo Engage Email Deliverability   Email Deliverability 101: 4 Tips to Inbox Success  
View full article
Deprecation of Email V1 began  almost  two years ago  and beginning with the  March  maintenance   release to London & Netherlands subscriptions on  March 17 th , 2021  and all other subscriptions on March 19 th , 2021 , all API support for V1  e mails will b e ended.  A fter this release,  any attempts to interact with V1 emails via the Asset APIs will result in errors and no actions taken .  All known remaining users since  February 24 th , 2021  have been notified ,  but  it is possible  that there are still integrations which may attempt to interact with these assets.  The most common types of affected integrations are services  which  offer digital  asset management, translation, and localization .     If you do observe integration failures as a result of this change,  you will still be able to upgrade problematic assets  by editing and approving them .  Once an email asset is upgraded to V2, you should be able to resume using it with integrated services.  
View full article
Support for Formula fields in batch campaigns was deprecated in 2013 and a notification was added to the product documentation here: Formula Fields. Currently, if a user attempts to schedule a batch campaign with an email that contains a formula field token WITHOUT spaces in the field name, the UI will show an error message saying this is not supported. However, due to an anomaly in the UI, if a user attempts to schedule a batch campaign with an email with a formula field token WITH spaces in the field name, the batch campaign will run. This UI issue was addressed in the January 2021 release of the product.   After March 19, 2021, these unsupported Formula Field tokens WITH spaces will no longer render correctly. Consequently, the tokens, and not the expected replacement strings, will appear in the final email. The deprecation is necessary to place all clients on a new, faster campaign processing platform.  To avoid further issues we recommend migrating the Formula Field tokens to Email Script Tokens immediately. Please refer to the following article which discusses how to use this option: https://docs.marketo.com/display/public/DOCS/Create+an+Email+Script+Token   If you have further questions about this issue, and/or best practices on migrating to Email Script Tokens, please contact Technical Support.  We want to ensure you have all the information you need to address the issue.   Kind Regards, The team at Adobe
View full article
In 2021, Marketo Engage will be making changes to the URL structure for Landing Pages, Forms, and Images & Files assets.   Why is this change being made? Technical Details Landing Pages Images & Files Forms What customer action is required?   When is this change being made? Starting January 21, 2021, we will begin gradually provisioning new Marketo Engage subscriptions with the new URL structure. On March 5, 2021, all new Marketo Engage subscriptions will be provisioned with the new URL structure in place.   For existing Marketo Engage subscriptions, we will begin gradually rolling this change out beginning April 1, 2021. More details on our rollout timeline will be released in March, 2021.   April 2021 update Starting in March 2021, a subset of new Marketo subscriptions will be provisioned with the new Design Studio URL structure. Beginning with our May 7th release, all new subscriptions will be provisioned with the new Design Studio URL structure.   Existing subscriptions will be gradually migrated through a rollout beginning May 20th.    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 belongs to the business they expect it to belong to. By updating each instance to use its own unique hostname, it is clearer to users the destination of URLs they are accessing.   Technical Details Landing Pages, Form embed code, and resources stored in Images & Files will have URLs updated from a hostname shared among all subscriptions on the pod to a hostname unique to each Marketo Engage subscription. Subscriptions configured to use a custom CNAME for their landing pages will be minimally affected by this change.   Landing Pages Subscriptions without a configured landing page domain Landing page paths will change to a unique hostname for your subscription. Before: http://na-sj01.marketo.com/lp/123-ABC-456/unsubscribePage.html After: http://123-ABC-456.mktoweb.com/lp/123-ABC-456/unsubscribePage.html   Subscriptions with a configured landing page domain Landing pages will continue to load from your configured landing page domain. No changes will be made. Before: http://example.marketo.com/unsubscribePage.html After: http://example.marketo.com/unsubscribePage.html   Images & Files Subscriptions without a configured landing page domain Paths to resources stored in Images & Files will change to a unique hostname for your subscription. Before: http://na-sj01.marketo.com/rs/123-ABC-456/images/cuteKitten.png After: http://123-ABC-456.mktoweb.com/rs/123-ABC-456/images/cuteKitten.png   Subscriptions with a configured landing page domain Resources stored in Images & Files will continue to load from your configured landing page domain. No changes will be made. Before: http://example.marketo.com/rs/123-ABC-456/images/cuteKitten.png After: http://example.marketo.com/rs/123-ABC-456/images/cuteKitten.png   Forms Subscriptions without a configured landing page domain OR subscriptions without landing pages secured by SSL Before:           <script src="//app-sj01.marketo.com/js/forms2/js/forms2.min.js"></script> <form id="mktoForm_1"></form> <script>MktoForms2.loadForm("//app-sj01.marketo.com", "123-ABC-456", 1);</script>           After:           <script src="//123-ABC-456.mktoweb.com/js/forms2/js/forms2.min.js"></script> <form id="mktoForm_1"></form> <script>MktoForms2.loadForm("//123-ABC-456.mktoweb.com", "123-ABC-456", 1);</script>             Subscriptions with a configured landing page domain secured by SSL In our October 2020 release, we updated our form embed code to load from the landing page domain when it is secured by SSL. No further changes will be made. Before:           <script src="//example.marketo.com/js/forms2/js/forms2.min.js"></script> <form id="mktoForm_1"></form> <script>MktoForms2.loadForm("//example.marketo.com", "123-ABC-456", 1);</script>           After:           <script src="//example.marketo.com/js/forms2/js/forms2.min.js"></script> <form id="mktoForm_1"></form> <script>MktoForms2.loadForm("//example.marketo.com", "123-ABC-456", 1);</script>             What customer action is required? Marketo Engage subscriptions provisioned after May 7, 2021 will have the new URL structure already in place for all Design Studio assets.   Existing Marketo Engage subscriptions will be migrated in a staggered rollout to the new URL structure during nightly maintenance cycles beginning on May 20th. There will be no downtime, but landing pages may experience a short period of degraded performance during migration.   Existing URLs and references will continue to work after the migration to the new URL structure until June 30, 2022.   To begin preparing for this change, we suggest doing the following: Configure your Landing Page URLs with a CNAME https://docs.marketo.com/display/public/DOCS/Customize+Your+Landing+Page+URLs+with+a+CNAME Secure your Landing Pages with SSL https://docs.marketo.com/display/public/DOCS/Add+SSL+to+Your+Landing+Pages Begin updating pages where you embed Marketo Engage forms with the new embed code introduced in our October 2020 release (requires secured landing pages) Begin an audit of where you reference Design Studio assets on the web. This will help you begin a plan to update any existing references to our older URL structure before we begin deprecation in 2022. Generally this will be on non-Marketo pages, as our Landing Page editor will automatically format embedded images and forms in a compatible manner. Only references hardcoded to the old URL structure need to be updated, e.g.   http:// na-sj01.marketo.com /rs/123-ABC-456/images/cuteKitten.png. Relative references will continue to work without need changes e.g.  /rs/123-ABC-456/images/cuteKitten.png. Please work with your web developer to determine where you may need to make updates.
View full article
What’s changing?   On  October 16, 2020 ,  Marketo will deploy new versions of  line, bar, column and pie charts  throughout the  Marketo  Engage Application .  This includes all reporting features, as well as data visualizations that appear in the Marketing Activities screen.     How will this change impact customers?   Customer impact will be minimal.   The  content   of the new visualizations will be identical to  that of  the previous ones ,  with some impro vements to axis labels and legend positioning to maximize use of the plot area.     Why is this change being made?   The previous visualizations were implemented using Adobe Flash, which will reach its official end-of-life on December 31 st , 2020 , and as a result the charts needed to be rebuilt using a different charting library.     What customer action is required?   No customer action is required.  The new visualizations will automatically appear in the  Marketo  application following  Marketo’s  product release on  October 16, 2020 .  
View full article
  Beginning on  2020-05-07 ,  Marketo  will start to roll out version 159 of the Munchkin  JavaScript  Client.   Subscriptions which have the  Munchkin Beta f lag enabled  will see changes from this release first, after which deployment will begin on a rolling basis to subscriptions which  do not have this flag enabled.    The  most significant change in this re lease is the  deprecation of Munchkin Associate Lead.       Changes     Deprecation of Associate Lead       Beginning with this release, when the  Associate Lead method  is invoked, a warning will be issued to the browser console, indicating that the method will be removed in a future release.  For more details on what to expect from this deprecation  process   read this announcement .     Reversion of Domain Selector V2       Despite best efforts to offer an improved the selection of the domain for the munchkin cookie, the change proved disruptive in certain cases.  We will be reverting the mainlining of this change, and the f unctionality will be  hidden behind a configuration flag  as it was prior to version 158 .     Fixing Undefined Referrer when Calling Visits Web Page       Previously when calling the  Munchkin API to submit a Visits Web Page event , the referrer would be submitted with a value of ‘undefined’.  With version 159, the referrer will now be cor rectly recorded.  This bug did not  affect  normal web visit tracking.       Rollout     As with all Munchkin releases, this version will be a phased rollout,  initiallity  to customers who have enabled  Munchkin Beta  for their subscriptions, and later for all  Marketo  subscriptions.  Th is schedule is subject to change.   Customers who need early access to these features in their subscriptions should consider enabling Munchkin Beta.   Date   Release Type   Percentage   2020-05-07   Beta   10%   2020-05- 21   Beta   50%   2020-0 6-05   Beta   100%   2020-06-19   General Availability   10%   2020-07-10   General Availability   50%   2020-08-04   General Availability   100%    
View full article
LinkedIn updated their permissions model on April 1. Marketo already supports the new permissions, so if you have not already done so, all you need to do is re-authorize your LinkedIn LaunchPoints to update your authentication token to ensure continued syncing. If you have both LinkedIn Matched Audiences and LinkedIn Lead Gen, you will need to re-authorize both LaunchPoints.   LinkedIn Matched Audiences LaunchPoint To update the permissions for the LinkedIn Matched Audiences LaunchPoint, a Marketo admin with access to your LinkedIn Business Account(s) will need to go to LaunchPoint in Marketo Admin. Select the LinkedIn Matched Audiences LaunchPoint and click "Edit Service" at the top.     Once in the Edit Service modal, click "Next". This will show you the user that authorized the integration and the date the LaunchPoint will expire.   Click on "Re-Authorize", which will open up a new window with a prompt to log into LinkedIn. You do not require the same user who originally set up the LaunchPoint.   Once you've signed in, the window will close and your LaunchPoint will now have an updated expiration date shown in the modal. Make sure to click "Save" to save the updated permissions.   And now your Matched Audiences LaunchPoint has updated permissions!   LinkedIn Lead Gen LaunchPoint To update the permissions for the LinkedIn Lead Gen LaunchPoint, a Marketo admin with access to your LinkedIn Business Account(s) and either admin or Lead Gen Form Manager permissions on your Company Page will need to go to LaunchPoint in Marketo Admin. Select the LinkedIn Matched Audiences LaunchPoint and click "Edit Service" at the top.   Once in the Edit Service Modal, click "Next". This will show you the user that authorized the integration and its expiration date. Click on the gray "Re-Authorize" button. This will open a new window with a prompt to log into LinkedIn.   Once you've logged in, the window will close and your LaunchPoint modal will show a new expiration date. Click "Next".   You will then see your list of LinkedIn Accounts. You do not need to update this screen. Click "Next" again. The final screen will be your field mappings. You do not need to update any field mappings to update permissions. Click "Save" to save updated permissions.   And now your LinkedIn Lead Gen LaunchPoint has updated permissions!  
View full article
I wanted to share a step-by-step on our solution to track multiple landing pages with a Person Attribute Field while using one generic form, without relying on URL UTM parameter. I hope this will be helpful to anyone looking for a solution. This solution was pieced together through some research from different sources and some trial and error. Feel free to share your thoughts or comments on it! Let's begin. [Problem] We have multiple landing pages linked to different campaigns and different assets to download. We wanted to use one generic form for all of those landing pages, and capture a Person Attribute Field to track the campaign, we didn't want long UTM parameters following our URLs or multiple forms so we built it into the page instead. [Solution] Populate a Hidden Field on your form through HTML code embedded into your Landing Page to capture campaign information. An alternate solution which doesn't use Person Attribute fields –  you can also use the "Add Constraint" option on the Fills Out Form trigger to select any form and the web pages you want to capture for the campaign, as shown below. If that's all you need, this simple solution would suffice. Step 1: Setting your Generic Form Field In your generic form, add a new Field and select the Person Attribute you're going to use to track the landing page. For our form, I used the "utm_campaign" Person Attribute because we're already tracking through that field. You can choose to use any Person Attribute that is appropriate for your Marketo instance to track campaigns. The Label doesn't matter, set Field Type to "Hidden", and set Form Pre-fill to "Disabled". Edit the Autofill , set Default Value as "utm tracking missing" (or anything similar of your choice, we'll get into why later) and Get Value from as "Use Default Value". If you don't set a default value Marketo defaults to "null" which will block changes to that field for this form. Once you're happy with your other fields, save your form. Step 2: Populating the Hidden Tracking Field through your Guided Landing Page HTML In your Design Studio , find the Landing Page Template you're using for your Landing Pages , and edit it. Note this step is only for Marketo Guided Landing Pages*. In your head section, place the following Marketo String with your meta tags (more information on Marketo Strings here) . This will allow you to easily adjust the landing page campaign later as you create more pages. Find where your Marketo form div is located, and insert the script code following the mktoForm div as shown below. This script will change your hidden "utm_campaign" field to the value indicated on your landing page. "utmcampaign"** is your Person Attribute Field name, and ${hiddencampaign} points to the Marketo String you set up. Save your Landing Page Template and you are done with this step. *Note: You can also do this step with embedded forms on non-Marketo pages using the code for setting Hidden Fields on this page. Note that you'll skip setting the Marketo String Syntax and input your desired Person Attribute value directly into the script as Marketo Syntaxes cannot be used on non-Marketo pages. **Note: You'll notice that the HTML form.vals "utmcampaign" is different from the displayed Person Attribute "utm_campaign" in your form editor and Marketo record. Sometimes the actual SOAP API value used by the backend is different from the Friendly Display value in Marketo, I will include steps on how to check the SOAP API value in the appendix at the end of this tutorial. Step 3: Create your Landing Page Once your HTML is set in your Landing Page Template , create or edit your Landing Page using that template. Set your generic form from earlier, and in your right-hand elements bar you should see a section for Variables , where you'll see the "Hidden Campaign Field" you created using the mktoString meta tag . Type in the campaign name you want to track with there. I chose "Example Campaign" for the purpose of this tutorial. Once you're happy with the rest of your landing page go ahead and save it. Your landing page form will now populate the "utm_campaign" Person Attribute for the Person with "Example Campaign" once the form is submitted. Step 4: Set your Trigger Capture Campaign Now that all the client facing elements are ready, you can create your Trigger Smart Campaign to capture and update the Person record. In your Marketo Program , create a new Smart Campaign . I've named mine "Campaign Capture" for my own organization, but you can name it whatever you want. Description is up to you, or just leave it blank. Once it's created, go to the Campaign's Smart List and add the Trigger Filter "Fills Out Form", and indicate one or more forms that feed into this campaign. Now add a Filter for "utm_campaign" and set the value to the "Hidden Campaign Field" you indicated on your landing page, in this case "Example Campaign". Insert any other Filters you want to exclude or include People that come through the program, and make sure to adjust your Smart List Rule Logic accordingly. Once you're happy with it, move onto the Flow step and set your form fill success actions. For this tutorial, we've opted to "Change Program Status" to Responded and "Send Email" confirming form success. Now "Activate" your Trigger Smart Campaign and you're ready to go! Step 5: Error Reporting No process is without errors, so now we'll set up a simple error reporting Trigger Smart Campaign to notify you when your campaign capture process fails at the form step. You'll recall that in the form, we set the Default Value for our "utm_campaign" as "utm tracking missing". This is so that in the event the HTML code in your Landing Page fails to populate the field with a value, the form sets this as the "utm_campaign" Person Attribute . To catch this error and notify myself, I set up a new Default Program with our "Operational" channel settings and named it "Tracking Error Notification". Inside it I created Smart Campaign and and an Alert Email (information on creating Alert Emails using the specific Alert Token) . In the Smart Campaign Smart List , insert a Trigger Filter for "Data Value Changes", Add Constraint "New Value" set it as the default error value, in this case "utm tracking missing" Now all that's left is to create a Flow Step to "Send Alert" (information on how here). Now you'll receive an email alert anytime the utm_campaign field fails to populate through the Landing Page form. *EDIT: A commenter recommended that the error message be cleared so that multiple exceptions can be flagged, which would be a great step. To do so, add a "Change Data Value" flow step for the Person Attribute, in this case "utm_campaign" and set the new value to "NULL", which will clear the "utm_campaign" field after the alert is sent. You're done! Now for all future Landing Pages with this generic Form , just remember to populate the "Hidden Campaign Field". I hope you've found this tutorial helpful. Cheers, Lawrence Mien Marketing Operations TigerText The Very Short Appendix So you've set your hidden Person Attribute field and indicated it in your HTML code, but the Person Attribute is still not populating correctly through the form. The issue may be that the Friendly Display Person Attribute field name is different from the SOAP API Person Attribute field for HTML. If you don't have Marketo Admin access, or don't feel like exporting the full field list, here's how you can check it: Publish or preview your Landing Page and go to it in your browser. Right-click at the bottom of the form (on Chrome) and hit Inspect. This will pull up the righthand side development panel to show you the HTML. Find the where the Marketo Form HTML is located and expand the mktoFormRow where the hidden field is. In the highlighted section below, you'll see that the SOAP API name of the Person Attribute is "utmcampaign" and not "utm_campaign". Simply drop this correct SOAP API Person Attribute name into your code back in Step 2.
View full article
Over the last few years all these translations have been gathered together by my colleagues. One of them had kindly gathered them into this beautiful display and I thought it was worth sharing with you all. CTAs English Simplified Chinese (CN-S) Traditional Chinese (CN-T) Portuguese (PT) Japanese (JA) Spanish (ES) Korean (KO) German (DE) View Now 现在就查看 現在就查看 Veja agora 今すぐ見る Vea ahora 지금 보기 Read More 阅读更多 閱讀更多 Leia mais さらに読む Lea más 더 읽기 Watch Video 观看视频 觀看視頻 Assista ao video 動画を観る Vea el video 비디오 보기 Learn More 了解更多 了解更多 Aprenda mais さらに学ぶ Aprenda más 더 알아보기 Read the brochure 查看资料手册 查看資料手冊 Leia o material 小冊子を読む Lea el folleto 브로슈어 읽기 Broschüre lesen Register today 今天就注册 今天就註冊 Inscreva-se agora 今すぐ登録する Regístrese hoy 오늘 등록하기 Explore more opportunities 发掘更多机会 發掘更多機會 Explore mais oportunidades 他の機会も探る Explore más oportunidades 더 많은 기회 알아보기 Read full report 查看完整报告 查看完整報告 Leia o relatório completo 完全レポートを読む Lea el informe completo 보고서 전문 보기 Read article 阅读全文 閱讀全文 Leia o artigo 記事を読む Lea el artículo 기사 보기 Read press release 阅读新闻稿 閱讀新聞稿 Leia o release de imprensa プレスリリースを読む Lea el comunicado de prensa 보도자료 보기 View tool 查看工具 查看工具 Veja a ferramenta ツールを見る Vea la herramienta 도구 보기 View quotes 查看报价 查看報價 Veja as cotações 相場を表示する Vea las cotizaciones 시세 보기 View contract specifications 查看合约规则 查看合約規則 Veja especificações de contrato 商品仕様を見る Vea las especificaciones de contrato 상품 명세 보기 Listen to podcast 收听广播 收聽廣播 Ouça o podcast ポッドキャストを聴く Oiga el podcast 팟캐스트 보기 View presentation 查看 查看 Assista à apresentação プレゼンテーションを見る Vea la presentación 프리젠테이션 보기 Get started 开始 開始 Aprenda 今すぐ始める Comience a aprender 시작하기 View offerings 查看产品及服务 查看產品及服務 Veja ofertas 商品とサービスを表示する Vea las ofertas 제안 보기** View schedule 查看日程安排 查看日程安排 Veja programação 予定を見る Vea el programa 스케줄 보기*** Read white paper 阅读报告 閱讀報告 Leia relatório oficial 白書を読む Lea el libro blanco 백서 읽기 Read fact card 阅读事实卡 閱讀事實卡 Leia o cartão de dados パンフレットを読む lea la tarjeta de datos 팸플릿 읽기**** Download PDF 下载PDF文档 下載PDF文檔 Baixe o PDF PDFをダウンロードする Descargar PDF PDF다운로드 PDF herunterladen Items found on Research Articles English Simplified Chinese (CN-S) Traditional Chinese (CN-T) Portuguese (PT) Japanese (JA) Spanish (ES) Korean (KO) German (DE) View this article in PDF format. Leia este artigo em formato PDF. Ver este artículo en formato pdf. Diesen Artikel als PDF anzeigen. About the Author 关于作者 演说者简介 해설자 소개 Über den Autor Disclaimer Common Headings English Simplified Chinese (CN-S) Traditional Chinese (CN-T) Portuguese (PT) Japanese (JA) Spanish (ES) Korean (KO) German (DE) Resources 资源 資源 関連情報 참고 자료 View in: English 简体中文 (CN-S) 繁體中文 (CN-T) 日本語 (JA) 한국어 (KO) Português (PT) Español (ES) 语言: 語言: Ler em: 使用言語: Ver en: 언어: Key Features 主要特点 主要特點 Principais características 主な特長 Principales características 주요 특징 Key Benefits 主要优势 主要優勢 Principais benefícios 主なメリット Beneficios clave 주요 혜택 Contact Us 联系我们 联系我们 Entre em contato conosco: お問合せ先 Contáctenos: 연락처 In the News 相关新闻 相關新聞 É notícia 関連ニュース Recursos 뉴스 화제 Figure 1 图1 圖 1 Gráfico 1 図1 Figura 1 그림 1 Abb. 1 Getting Started 简介 簡介 Começando ご利用を始めるにあたって Primeros pasos 시작하기 Related Content 相关资料 相關內容 Conteúdo relacionado Contenido relacionado Forms English Simplified Chinese (CN-S) Traditional Chinese (CN-T) Portuguese (PT) Japanese (JA) Spanish (ES) Korean (KO) First Name 氏 氏 Primeiro nome 氏 Nombre 이름 Last Name 姓 姓 Sobrenome 姓 Apellido 성 Business email 电子邮箱 電子郵箱 Email corporativo 業務用メールアドレス Correo electrónico empresarial 이메일 Phone number 电话号码 電話號碼 Telefone 電話番号 Número telefónico 전화번호 Country 国家 國家 País 国 País 국가 Address 地址 地址 Endereço 住所 Domicilio 주소 City 城市 城市 Cidade 市町村 Ciudad 도시명 State 省 省 Estado 州・都道府県 Estado 주 Firm name 公司名称 公司名稱 Nome da empresa 会社名 Nombre de la empresa 회사명 Company Type 公司类型 公司類型 Atividade da empresa 会社の種類 Tipo de empresa 회사 유형 Job Function 工作职能 工作職能 Função 職務権限 Función del cargo 담당 업무 Comments/Specific Interest 评论/咨询 評論/諮詢 Comentários/Interesse específico コメント/質問 Comentarios/Interés específico 건의사항 또는 관심 사항 Submit 提交 提交 Enviar 送信 Enviar 제출 Regulator 监管者 監管者 Regulador レギュレータ Regulador 규제당국 Vendor 供应商 供應商 Fornecedor ベンダー Proveedor 벤더 Other 其他 其他 Outro その他 Otro 기타 Indicates required fields. 必填项 必填項 Indica campos obrigatórios 入力必須の項目です。 Indique los campos requeridos 필수 항목을 가리킴 Contact Us 联系我们 聯繫我們 Entre em contato conosco お問合せ先 Contáctenos 연락처 Must be valid email. Example@yourdomain.com 请填写有效邮箱, Example@yourdomain.com 請填寫有效郵箱, Example@yourdomain.com E-mail válido é necessário. Exemplo@seudominio.com 有効なメールアドレスでなければなりません。例: Example@yourdomain.com Debe ser un correo electrónico válido. Ejemplo@sudominio.com 유효한 이메일이어야 합니다. Example@yourdomain.com This field is required. 该项是必填项 該項是必填項 Este campo é obrigatório. この項目は必須です。 Se requiere este campo. 이 항목은 필수항목입니다. Thank you. Your message has been received. Someone will contact you shortly 您好,您的信息已收到,我们的工作人员会尽快与您联系 您好,您的信息已收到,我們的工作人員會盡快與您聯繫 Obrigado. Sua mensagem foi recebida. Você será contatado em breve. ありがとうございました。メッセージを受信いたしました。こちらよりご返信いたします。 Gracias. Hemos recibido su mensaje. En breve, una persona se pondrá en contacto con usted. 감사합니다. 귀하의 메시지가 접수되었습니다. 곧 연락 드릴 예정입니다. Executive 行政管理 行政管理 Executivo 幹部 Ejecutivo 임원 Finance 金融 金融 Finanças 財務 Finanzas 재무 Marketing 市场营销 市場營銷 Marketing マーケティング Marketing 마케팅 Research 研究 研究 Pesquisa リサーチ Investigación Research Sales 销售 銷售 Vendas 営業 Ventas 영업 Technology 技术 技術 Tecnologia テクノロジー Tecnología 전산 Trading 交易 交易 Negociação トレーディング Operaciones 운용 Other 其他 其他 Outro その他 Otro 기 Select… 选择… 選擇… Selecione... 選択してください…… Seleccionar… 선택… Submit 提交 提交 Enviar 送信 Enviar 제출 First Name: 名: 名: Nombre: 名: Primeiro nome: 이름: Last Name: 姓: 姓: Apellidos: 姓: Sobrenome: 성: Comments/Questions: 评论/问题: 評論/問題: Comentarios/Preguntas: コメント/質問: Comentários/questões: 코멘트/질문: Submit 提交 提交 Enviar 送信 Enviar 제출 Contact Us 联系我们 聯繫我們 Contacto お問合せ先 Entre em contato conosco 연락처 Welcome back, [name] 欢迎回来, [姓名] 歡迎回來,[姓名] Bem-vindo de volta, [name] 再ログインありがとうございます、 [氏名]様 Bienvenido nuevamente, [nombre] [이름]님 다시 오셔서 환영합니다. Click here if this is not you. 如果您并非所示姓名本人,请点击这里。 如您並非所示姓名本人,請按此。 Clique aqui se não for você. [氏名]様ではない場合は、ここをクリックしてください。 Haga click aquí si éste no es usted 다른 사람이시면 여기를 클릭하십시오 Topic 主题 主題 Tópico トピック 주제 Select One 请选择一个 請選擇一項 Selecione um 一つ選択してください 하나를 선택하십시오 Register for future communications 注册日后接收通讯 登記日後收取通訊 Inscreva-se para contatos futuros 今後の通知を受け取るための登録 향후 커뮤니케이션을 위해 등록하십시오 Thank you for registering. ご登録いただき、ありがとうございます。
View full article
Marketo Users often create a Trigger Campaign to trigger "Clicks Link” or “Open Email” activities on AB Test Email Program. They are surprised that they cannot find the emails in question under the Smart List drop menu for the trigger (1). Or, they successfully selected the Emails without issue and activated the Trigger Campaign, but after all it is throwing errors (2). What happened? 1. When Emails are used under AB Test Email Program, their name is wrapped with the Program Name + Test Type Name. E.g.  TEST AB TESTING.Whole Emails Test (it will look different depending on Test Type you select. But, it will always start with the Program Name). Then, targeted Emails name can be located under Constraint Trigger “Test Variant” as shown below (Emails Name here are Email A/Email B & Test Type: Whole Emails):   Note that Link & Test Variant can be found under “Add Constraint”. Also, it is very important to approve the AB Test Program before you create the Trigger Campaign otherwise those data won’t be available there for you to use. 2. Errors can be the result of not activating the AB Test Email Program before doing so for the related Trigger Campaign. Because, if it is activated in the first place there is no way to find the Emails' Name under the Trigger Smart List. Meaning that after initiating the AB Test, the system can no longer retrieve the targeted Emails name. Consequently, you get an error under the Trigger Campaign Smart List and it won’t fire.          
View full article
A customer who has been using Marketo as a standalone system for the past year asked me recently for some tips for integrating with SFDC. Please note the following tips will also apply if the customer had a custom integration and was not using Marketo's connector for Microsoft Dynamics or SFDC. Check in the Marketo Admin area for the CRM icon Create a strategy for handing the duplicates which will be created in Marketo So if you've been using Marketo for a while you've probably imported a lot of lists Records synced from SFDC are NOT deduped against existing records in Marketo based on email address Any records including duplicates based on email address syncing from SFDC will sync to Marketo, records syncing from SFDC are considered intended behavior The easiest way to handle the issue is to delete all the records in Marketo before syncing with SFDC Unfortunately, you will lose all your activity history Another option is to work with Marketo services or a Launchpoint partner to merge the duplicates together If you have a lot of duplicates, it may take many weeks to merge all the records together Merging records will preserve the activity history but may cause smart campaigns to fire, always test and be prepared to adjust your campaigns accordingly Consider a hybrid approach by deleting the least valuable records Create a strategy for the fields you want to sync from SFDC Marketo will automatically map the most common SFDC fields with your existing fields Consider switching from your Marketo custom fields to your SFDC fields or merging the fields together. Here are some resources about fields Read about implementing a custom sync filter following the best practice Read about how the sync works. If you are using SFDC Lighting, be aware of the unsupported features. Understand how Marketo treats records deleted in SFDC Understand the different ways you can insert/sync a Marketo record to SFDC unintentionally Finally, here are some handy references in case you are wondering about using the SFDC Opportunity Object or a SFDC Custom Object. Feel free to add your own tips. Thanks!
View full article
Hi All, I recently inherited a marketo database and am new to administrating the platform in general. I come from a salesforce background and have been spoiled at having the ability to look up what each permission does and exactly what it controls. I've searched out there for something similar with marketo and haven't had a whole lot of luck finding a consolidated document that describes the roles well. I have tried compiling my own and there were a few things I didn't know, but if there is an expert out there, can you take a glance at this and let me know if I've misunderstood any of the permissions? Thank you! Kelly Access Admin Access Admin: Ability to click on ‘Admin’ in the upper right corner of Marketo. Also allows user to see Admin | My Account. Access Channels: Ability to see and manage Admin | Tags | New Channels or Tag Actions. Note this only applies to channel type tags. Access Communication Limit: Ability to see and manage Admin | Communication Limits. Access CRM: Ability to see and manage Admin | Database Management | Salesforce Objects Sync and Admin | Integration | Salesforce. Access Data.com: no current subscription, assuming this assists in downloading leads from data.com Access Email Admin: Ability to see and manage Admin | Email. Access Event Partners: Ability to see and manage Admin | Integration | LaunchPoint. Access Field Management: Ability to see and manage Admin | Database Management | Field Management. Access File Upload: not sure what this does Access Landing Pages: Ability to see and manage Admin | Integration | Landing Pages. Access Location: Ability to see and manage Admin | Location. Access Login Settings: Ability to see and manage Admin | Security | Login Settings. Access MK Denial: no current subscription - not sure what this is Access Munchkin: Ability to see and manage Admin | Integration | Munchkin Access Revenue Cycle Analytics: Ability to see and manage Admin | Revenue Cycle Analytics. Access Roles: Ability to see and manage Admin | Security | Users & Roles | Roles. Access Sales Insight: Ability to see and manage Admin | Integration | Sales Insight. Access Single Sign-on: Ability to see and manage Admin | Single Sign-On. Access Smart Campaign: Ability to see and manage Admin | Smart Campaign. Access SOAP API: Ability to see and manage Admin | Integration | Web Services. Access Tags: Ability to see and manage Admin | Tags | New or Tag Actions. Note this only applies to non-channel tags. Access Treasure Chest: Ability to see and manage Admin | Treasure Chest. Access Users: Ability to see and manage Admin | Security | Users & Roles | Users. Access Webhook: Ability to see and manage Admin | Integration | Webhooks. Access Workspaces and Partitions: Ability to see and manage Admin | Security | Workspaces & Partitions Marketo Custom Objects: only granted to the standard Admin role. Access Analytics Access Analytics: Ability to access the Analytics module. Includes the ability to see all reports, create new reports, and modify existing reports. Can create new folders and archive content. Access Revenue Explorer: Grants full access to the Revenue Explorer module. (Includes export from Revenue Explorer). Delete Report: Ability to delete existing reports in the Analytics module. Export Analytics Data: Ability to export reports to Excel in the Analytics module. Access Calendar Presentations - Requires a Marketing Calendar License Access Calendar Presentations: Ability to access the Calendar module and view the details of calendar events. Can view Calendar Presentations. Can create new Calendar Presentations Edit Calendar Presentations: getting odd behavior, would assume additional permissions required for this to work correctly Access Design Studio Access Design Studio: allows access to the design studio tab and to view the tree. This access alone does not allow the users to see the details of the asset. Access Email Access Email: allows the user to view the details of the email. Approve Email: allows the user to approve the email. Delete Email: allows the user to delete an email. Edit Email: allows the user to create an email and update an existing email. Access Email Template Access Email Template: allows the user to view the details of an email template and use it. Approve Email Template: allows the user to approve the email template. Delete Email Template: allows the user to delete an email template Edit Email Template: allows the user to create an email template and update an existing email template. Access Form Access Form: allows the user to view the details of a form. Delete Form: allows the user to delete a form. Edit Form: allows the user to create and update an existing form. Access Image Access Image: allows the user to view the details of an image or file. Delete Image: allows the user to delete an image or file. Upload Image: allows the user to upload an image, including overwriting existing ones. Access Landing Page Access Landing Page: allows the user to view the details of a landing page. Approve Landing Page: allows the user to approve a landing page. Delete Landing Page: allows the user to delete a landing page. Edit Landing Page: allows the user to create and edit a landing page. Access Landing Page Template Access Landing Page Template: allows the user to view the details and use a landing page template. Approve Landing Page Template: allows the user to approve a landing page template. Delete Landing Page Template: allows the user to delete a landing page template. Edit Landing Page Template: allows the user to edit a landing page template. Access Snippet: snippets are reusable blocks of rich text and graphics that can be used in emails and landing pages. Access Snippet: allows the user to view the details of a snippet and use it. Approve Snippet: allows the user to approve a snippet. Delete Snippet: allows the user to delete a snippet. Edit Snippet: allows the user to create and edit a snippet. Access Social App: these are typically accessed under Marketing activities and not design studio. Access Social App: allows the user to view the details of social buttons and use them. Approve Social App: allows the user to approve social apps/buttons. Delete Social App: allows the user to delete social apps/buttons. Edit Social App: allows the user to edit social apps/buttons. Access Lead Database Access Lead Database: grants access to the Lead Database module Access Segmentation Access Segmentation: grants the user access to view the details of a segment and use them. Approve Segmentation: allows the user to approve a segment. Delete Segmentation: allows the user to delete a segment. Edit Segmentation: allows the user to create or edit a segment. Advanced List Import: Delete Lead: allows the user to be able to delete a lead record from the Lead Actions list. Delete List: allows the user to be able to delete a list (static or smart). Edit Lead: allows the user to be able to edit a lead record by double clicking on a lead. Also allows the user to be able to add to other programs. Export Lead: allows the user to be able to export a list of leads from marketo. Import Custom Object: if there are custom objects in marketo, this allows the user to be able to import the data for custom objects. Import List: allows the user to import data into marketo via right click on group list | Import List. Merge Leads: allows the user to be able to merge lead records from the Lead Actions list. Run Single Flow Actions: extends the edit lead functionality by allowing access to single flow actions that can sync with salesforce. View Opportunity Data: allows the user to see the opportunity tab when viewing a lead record. Access Marketing Activities Access Marketing Activities: grants access to the Marketing Activities module. Requires additional access from the design studio to view the design assets. Requires additional access from the lead database to view smart lists and results. Access Push Notification: requires a webhook to a 3 rd party that uses SMS distribution. Once that’s been established then push notifications can be accessed. Approve Push Notification: allows a user to approve a push notification. Delete Push Notification: allows the user to delete a push notification. Edit Push Notification: allows the user to create and edit a push notification. Access Awards: not sure what this is, possibly requires a subscription Activate Trigger Campaign: allows the user to activate a triggered campaign. Approve Email Program: allows the user to approve an email program. Clone Marketing Asset: allows the user to clone a marketing asset. Delete Marketing Asset: allows the user to delete an individual marketing asset. Edit Marketing Asset: allows the user to create and edit a marketing asset (think programs). Import Program: allows the user to mass clone all assets under a program to create a new one. List Import: allows the user to create a new list and import members into it. Schedule Batch Campaign: allows the user to schedule and run a batch campaign. Access SEO: need to review this more, not sure of all of the differences between the two dashboards. Access SEO: grants access to the SEO module. Requires one of the following two permissions in addition. Administer SEO: grants admin access to the SEO Dashboard. Standard SEO: grants read-only access the SEO Dashboard. Workspace Administration – requires a subscription to workspaces & partitions Workspace Administration – cannot confirm, could be that it grants the user access to all workspaces Move Assets Between Workspaces – if a subscription is active, allows the user to move assets from one workspace to another. Access Mobile Application Access Mobile Application – grants the user to two mobile apps: Event Check-in and Marketo Moments Hi Kelly, First off, thanks for taking the initiative to share this! I feel like Marketo's own documentation is a little weak in this respect, since it only lists permissions without explaining what those permissions actually control. To answer a few of your questions: 1e/1m. For whatever reason, Marketo has the permissions for data.com and MKDenial​ defined even on instances that do not subscribe to either service. 1i. I believe this specifically refers to the ability to upload files other than images in Design Studio, but would love clarification from Marketo. 7a. This specifically refers to the ability to create and administer workspaces themselves; granting a user access to workspaces is actually done when assigning individual users roles (since you may want someone to be an admin of one workspace, but have less permissions on another, for instance.) Also, throwing this one out there: what is "Access/Administer Vespa"? I completely realized I posted this under my test user's account and not my own. *sigh* Is there anyway to change the ownership of the thread? If not, no worries. Wow, this is a great summary!  While I haven't verified every role to be correct, I would highly encourage the Marketo documentation/education team to add this to product docs. Hi Frank Passantino​, Might be interesting to you -Greg Hi: Thanks for publishing this!  As a word of warning: I was recently told by Support that certain rights are not entirely dependent on that check box in the role.  For instance, if you have a user you would like to manage communication limits and the global footer, they need to be the default Admin, despite checking that box when creating a custom role.  I would really like to see an easier way to manage access in the application.  I have users I want to empower for every Marketing-related functionality, but, because we are fully integrated with several other databases within our company, I need to keep tight restraints on mass edits to the database, field creation/additions, etc.  This is the first application I worked with that makes administration this murky. I haven't run full tests on each of the admin functions you outlined, but I know communication limits and the footer are dependent on the user having full admin rights.  Channel Tags are not; you can give a user access to these without granting full admin privileges.  Noted. Thank you for mentioning that. Hi Kelly, Thank you for documenting all of this!  Quick question.. Clone Marketing Asset: allows the user to clone a marketing asset. Does this permission encompass cloning entire programs?  I'm researching the possibility of allowing an international user who works in one work space the ability to clone programs from the US work space. Yes, Anna, when cloning a Program, it will clone all assets/items underneath. The ability to Clone items under Marketing Activities encompasses this as well. Sharing a document page I came across today, as I'm researching what permissions/access each role has. Looks like you got the list covered! Descriptions of Role Permissions - Marketo Docs - Product Docs Access Admin - view and make changes to settings in the Admin section. Access Audit Trail Access Channels - access only to modify the Channel tag, not other custom tags Access Communication Limit Access CRM Access Data.com Access Email Admin Access Event Partners Access Field Management Access File Upload Access Landing Pages Access Location Access Login Settings Access Marketo Custom Activity Access Marketo Custom Object Access MK Denial Access Munchkin Access Revenue Cycle Analytics Access Roles - access to manage and edit roles, but not users Access Sales Insight Access Single Sign-on Access Smart Campaign Access SOAP API Access Tags - access to all custom tags except the Channel tag Access Treasure Chest Access Users - access to edit and manage users, but not roles Access Webhooks Access Workspaces and Partitions Access API Approve Assets Execute Campaign Read-Only Activity Read-Only Activity Metadata Read-Only Assets Read-Only Campaign Read-Only Company Read-Only Custom Object Read-Only Lead Read-Only Opportunity Read-Only Sales Person Read-Write Activity Read-Write Activity Metadata Read-Write Assets Read-Write Campaign Read-Write Company Read-Write Custom Object Read-Write Lead Read-Write Opportunity Read-Write Sales Person Access Analytics - see the Analytics tabs, view and edit reports Access Revenue Explorer Delete Report Export Analytics Data Access Calendar Presentations Edit Calendar Presentations Access Design Studio - see the Design Studio tab Access Email - view Emails Edit Email - edit, create, and clone emails Make Email Operational Approve Email Delete Email Set Branded Domain Access Email Template - view Email Templates Approve Email Template Delete Email Template Edit Email Template - edit, create, and clone email templates Access Form - view Forms Delete Form Edit Form - edit, create, and clone forms Access Image - view Images Delete Image Upload Image Access Landing Page - view Landing Pages Approve Landing Page Delete Landing Page Edit Landing Page - edit, create, and clone landing pages Access Landing Page Template - view Landing Page Templates Approve Landing Page Template Delete Landing Page Template Edit Landing Page Template - edit, create, and clone landing page templates Access Snippet - view Snippets Approve Snippet Delete Snippet Edit Snippet Access Social App - view Social App Approve Social App Delete Social App Edit Social App Access Lead Database - view the Lead Database, view and edit Smart Lists and static lists Access Segmentation Approve Segmentation Delete Segmentation Edit Segmentation Advanced List Import Delete Lead Delete List Edit Lead - prevents manual editing and running single flow actions. You can still edit leads by running campaigns against them Export Lead - export spreadsheets with from your Lead Database lists Import Custom Object Import List Merge Leads Run Single Flow Actions - Enable users to run 'Change Data Value' action on Leads from the Lead Database View Opportunity Data - hides the opportunity info on the lead detail page Access Marketing Activities - view the Marketing Activities tab, campaigns, and campaign folders Access SMS Message Approve SMS Message Delete SMS Message Edit SMS Message Access Push Notification Approve Push Notification Delete Push Notification Edit Push Notification Access Awards Activate Trigger Campaign Approve Email Program Clone Marketing Asset Delete Marketing Asset Edit Campaign Restrictions Edit Marketing Asset Import Program List Import Schedule Batch Campaign Access SEO Administer SEO Standard SEO Targeting and Personalization Administer Web Personalization CRE Campaign Editor CRE Campaign Launcher Web Campaign Editor Web Campaign Launcher Workspace Administration - Admin access for a specific Workspace (only if you have Workspaces enabled) Move Assets between Workspaces - (only if you have Workspaces enabled) Access Mobile Application This document was generated from the following discussion: 
View full article
Included in this article Summary How Leads Become Known Anonymous Web Activity Logging Triggered Smart Campaigns Revised 2/19/2016 Replaced screen shots with corrected versions Summary When a person visits a web page with your Munchkin tracking code on it, that web activity is tracked for that anonymous lead. When a lead takes action to become known, a lead record is created in your Marketo lead database and the anonymous web activity that lead had prior to becoming known is included in that new lead record. Any smart campaigns that would have triggered off of that web activity will then fire in the order of when the web activity occurred. How Leads Become Known There are three main ways that an anonymous web activity record can be converted into a known lead in your Marketo lead database.           1. Fills out form . If the anonymous lead fills out a Marketo form, that will create a new known lead record. The anonymous web activity that lead had before becoming known will be associated to that new known lead record.      2. Clicks a link in an email . Hyperlinks in emails are automatically decorated with a tracking code that is used to associate an anonymous record back to a known lead record. If you have a lead in your database that hasn’t had any web activity yet (like a lead that was added from a list import), when the lead clicks the hyperlink in the email, that tracking code in the hyperlink will associate their Munchkin cookie to your known lead record and all of that anonymous web activity will be logged into that known lead record.      3. API call . You can use an API call to associate an anonymous web activity record to a known lead record. This can be done through a SOAP API syncLead call​, or by a REST API Associate Lead call. Anonymous Web Activity Logging Anonymous lead activity is housed in a different database. This doesn’t create a lead record until the lead is promoted to a known lead. All activity a lead had prior to becoming known will be logged chronologically in the new lead record with the correct corresponding date/time stamps once the lead becomes known.                Triggered Smart Campaigns Anonymous leads can’t trigger smart campaigns. However, when a lead becomes known, the active smart campaigns that would have triggered from the anonymous activity will be triggered. All trigger campaigns currently active at the time the lead becomes known will be triggered if the lead took the action being triggered on while anonymous. Only campaigns currently active at the time the lead becomes known will be triggered.                The campaign definition at the time it is triggered is what will be executed. For example, if the campaign has a Score Change of +10 but is changed to +5 just before the lead becomes known, the new lead created will be given a score of 5, not 10. The campaigns that are triggered by the anonymous activity will be processed in order of the activities that occurred, oldest to newest. In the lead’s activity log, all campaign activities (with one exception below) will be logged with the time stamp of when the lead becomes known, right before the New Lead activity. Interesting Moment flow step activities will be backdated to the date and time when the corresponding anonymous activity occurred.                Not all flow actions in the campaign will be executed. When leads flow through campaigns as a result of the promotion to known lead, only specific flow actions will be processed. All other flow actions will be ignored. The flow actions executed will be:           1. Change Score           2. Interesting Moment           3. Change Data Value           4. Add to List           5. Remove from List Secondary campaigns (campaigns triggered off of activities performed by the campaigns triggered by the lead promotion) will not be triggered.                Pruned activities will not trigger campaigns. Anonymous web activity is not stored forever—it gets pruned over time, so any activity that has been pruned is no longer there to be triggered off of.
View full article
In our first post, we discussed the concept of URLs and UTM tracking. Now that those are in place, we will dive into the setup with Marketo. Here are the high-level steps: Create the UTM fields in order to have a place to store the values Add the fields on your form pages as hidden fields, add to a landing page Setup the Marketo programs and/or smart campaigns to process them Test and check to make sure it's working Step 1 - Create UTM fields If you are setting this up for the first time, or you have inherited a Marketo instance, I recommend checking to make sure these fields are not already in place, or they exist, but are named something else. If you have access, go to Admin > Field Management, and search for any fields containing "utm" or "ppc" to see if they are there. In the screenshot below, you'll see that all 5 fields have been created and are currently mapped to the SFDC lead and contact records. *Side note: The mapping is important if you want the values for leads or contacts since SFDC treats them differently. Also, if you are creating them for the first time, make sure to do it in SFDC and wait for the fields to sync to Marketo or you'll have to get it re-mapped. ​ Step 2 - Add fields to your forms Now that you have the fields created, add them to any relevant data forms. There are two main options for this. If your website uses custom non-Marketo forms, ask your web developer to add the extra fields to the forms and make them hidden. In the field management screen, there's an "Export Field Names" button which will export all the necessary fields that you can provide to your developer. The file provides a mapping for the UTM values that need to be written to from the website form field to the Marketo field. There might be other options such as native plugins that might already accomplish this. If you are adding them to a Marketo landing page, drag those new fields onto your forms and make them hidden. In the Autofill property, choose Edit and you'll see options to chose where the field values will populate from. Choose URL Parameter and type in "none" for the default value or anything that you can filter on later to troubleshoot if it's not working. At this point, the landing page is just waiting for a referring visit with UTM values. Consider what happens when someone clicks a link, but does not sign up right away? The values from the URL parameter must be present at the time of submission in order for this to work. So if someone navigates away and the parameters disappear, then the UTM values will not be captured. To solve for this, we have created a tracking script that will store any UTM parameters it finds into a cookie. Now when a visitor fills out a form that contains the hidden UTM values on a form, the cookie will store the UTM value across the main and subdomains. *Technical Stuff: You can upload the extracted file into the images directory or on your web server. Before doing so, take note to make one change to the file and re-save it for it to work. Open the file with any text editor and looking for a line that says "domain=digitalpi.com" and change it to your domain. Once set, it won't expire for another 365 days. The script should be place where your Munchkin script is also placed. It's a simple script that does the following. If UTM parameters are present, store those into a cookie. This means if it comes from a URL and it's the first time seeing it, the script creates the cookie. If the visitor comes back by clicking another link with different UTM parameters, it will replace with the new ones and continue to do so. It's not session specific which means if the visitor closes the browser and comes back at a later date, it will still be in the cookie and keep it for 365 days. Here's a link to the tracking script: dpi-ppc-tracking-script.js.zip So that you can see this process in action, I created a simple form with visible UTM fields on a landing page. When you click on one of the sample links, you should see the UTM values in the UTM fields where they would normally be hidden. If you want to experiment with it, change any of the UTM values after the equal sign and refresh the page. You'll see the new value populated in the field that was changed. Long version: http://info.digitalpi.com/Marketo-UTM-Sample-Page.html?utm_source=blog&utm_medium=email&utm_term=utm&utm_content=utm-tracking-blog-p2&utm_campaign=blog-sub Shortened version: http://goo.gl/O6VyL9 Step 3 - Setup Marketo processing This next part is just ordinary Marketo smart campaign building. Setup the trigger filtering on UTM values. Make sure it's unique enough to process for the individual UTM parameter (campaign, source, medium, etc.). Step 4 - Test and validate Create a few URLs to your landing page and use different combinations of UTM parameters and click on your form submission. Look for the test record and in the custom fields look for the values. If they are there, it's working properly. Keep in mind these values will change each time a new set of UTM values are set. You can run reports on the different campaigns or even down to the add level if programs are setup to track that. This feature is used frequently, so we hope this article saves a lot of time and frustration. Happy Marketing!!
View full article
Our sales team is very new to Sales Insight, so I did a training with them last week to show them some of the features and how they can use it to interact with their prospects better. I figured this is probably something a lot of us have to do at some point, so I am attaching my powerpoint that anyone can adapt to use for their own sales teams. Warning: it has many gifs and memes. Our sales team is very young, so I knew this would keep their attention also, my gif game is strong. Some of this is specific to our instance - for example, I created a marketing suspend campaign to allow them to suspend a prospect from marketing for 30 days if they are actively working a deal or about to do a demo - but it can probably be adapted for anyone.
View full article
Our Community Blogs are a great way for our customers to have a voice. We want you to share your the successes, innovations, experiences, and ideas with your peers to help build your personal brand and heighten your awareness. The Nation is a powerful tool, and it's at your fingertips, don't be afraid to use it! Not all of our blogs are open, some you have to participate and earn status to be able to contribute to ( Blog) while others are open and free for everyone to contribute to ( Blog)! To see a full list of the different blogs Marketo has (both on and off the Community) you can visit our ​ page in ​. When posting to one of our Community Blogs, here are a few guidelines to remember: Do not duplicate content, meaning do not simply cut and paste content from your personal blog and post it. See "Re-purposed content" below Have a thesis, POV, or CTA Feel free to link to your personal blog if it is relevant to the post Limit external links in your posts, as we aren't trying to drive users off of Community Keep it focused on Women in Business and how it relates to topics like digital marketing, marketing automation, engagement marketing, building teams, workplace equality, and more Do not sell or pitch products...we are monitoring these. Soliciting your personal products or services could result in removal from the blog Share something new and actionable. We want our reader to walk away with the sense that they learned something 400 - 500 words. Re-purposed content: You are welcome to re-purpose content you already have, as we understand you have day jobs and can't dedicate your life to solely writing new content for Marketo No more than 75% overlap with existing content. In other words, rewrite the content with the Marketo user in mind. Make it unique to the Marketo Community Different headline than original post Again, limit / omit external links. It's recommended you include these as part of your author description if you plan to include them at all Frequency: This blog is featured on our page, so we are always needing fresh and relevant content there consistently No spamming (don't post more than once a day) Recommendations: Write when you have time, but don't feel like you have to post right away. Store some content up, and come up with your own content calendar Keep an eye on the blog and post when you see it's becoming stale Comment and participate in other customers blogs, your input is valued greatly Pay attention to the what's hot in the industry Pay attention to what our customers are interested in by scanning conversations in ​ & ​ Ready to post? Find your blog by viewing and get started! If you have questions, let us know! HAPPY BLOGGING!
View full article
Personal thanks to Stephane Hamel ​ for providing this document. If you have an feedback, .. if you find it useful, if it helps you, if you see any errors or things that could be improved - let me know! Please let Stephane Hamel​ know.
View full article
As part of my role in Marketing Operations is to manage data quality. Data comes form many sources and not always in the optimal state I require it to be for lead routing. Not all Marketers are data savvy and will need some coaching when they hand over a CSV file from an event they have just ran. As we collect data from a variety of regions, not all of it is going to be perfect. Some folks expect Marketo platform to cleanse the data on upload. Some maybe missing mandatory data points in order for them to be routed to the appropriate sales rep for follow up. Bad practices of data collection can leave your data base with gapping holes and will require extra scrutiny at some point. One of the first things I do each Monday morning is check on how many leads we are collecting from our marketing activities with missing data by running a Marketo report. We took advantage of Marketo lead report in Revenue Cycle Analytics with the ability to add custom smart lists to the report. This report can then be subscribed to on a weekly or monthly cadence. Below are the steps to take to build a database health report: First off, we need to build smart lists for every field we need visibility into. Create a new folder in your Smart List section of Marketo Data base, name it ‘Data Base Health Report Smart Lists’ and create a new Smart List and start off with First Name. Make sure to name your Smart Lists the way you want them to be named in your custom columns as they will appear exactly the same. Drag and drop in First Name field into your smart list, select ‘Is empty’. This smart List will group all leads in your DB with a missing First Name. Do the same for Last Name, Company Name, Country, Lead Source, Industry, Phone etc. All the ones you need to monitor. Now go to Analytics section and create a new lead report. Go to set up and add in your custom column smart lists, the first two columns will be your 'Grouping' and 'Total leads', so be sure to add them in the order you want them to appear in the rendered report. Note: can only add up to 10 smart lists as custom columns to the lead report. Now group your report by lead create date and select to view monthly. Go to subscription section and add yourself and pick whatever cadence you want your report to be sent out. In the smart list section of your lead report, add any filters you need to segment your report by, E.g. try to look only for leads created by a certain date or from a large static list etc. Below I'm making sure I don't pull leads with empty email address and a lead type of Corporate. This area helps you to focus your lens to a smaller set of data or leave blank and pull in your whole data base to the report. Now hit report to render, once rendered, you may need to adjust the columns. Your report will now show you your total leads by your chosen create date and grouped by created month. Along side will have columns to show total leads and how many of that total are missing First Name, Last Name, Company Name, Country, Lead Source, Industry, Phone etc. Advanced actions: Using this method of reporting can show many more ways to chop your data up. Try using smart list columns for certain Marketo forms your monitoring for engagement. Filter on lead sources with lead source detail.
View full article
[FAQ attached below this article]   What's Changing? On August 31, 2020, Marketo Engage will implement a new retention policy specifically for Sent & Delivered Email activities. Under this policy, data for these two activity types will be stored for a rolling 90-day period from the activity date for use in Smart Lists. This is a change from the current default retention period of 25 months, and from the current  Extended Data Retention subscription option period  of 37 months.   Upon the policy taking effect, data older than 90 days for these two activities will be deleted and no longer available for export. Any Smart List with the “Was Sent Email” and “Was Delivered Email” filters (including NOT Was Sent and NOT Was Delivered) should be updated to ensure the maximum lookback date is 90 days.  If the lookback date is greater than 90 days, the Smart List will continue to function, but only activities that are 90 days old or less will qualify.   Why? In 2020, we are improving critical parts of the underlying Marketo Engage infrastructure, including Batch campaign processing, similar to the Trigger campaign improvements made in 2019. This new infrastructure, in combination with the new retention policy, is expected to result in shorter lead time with large email sends and faster segmentation processing to deliver significantly faster processing to our customers. Note, the revised retention policy is one, among several, aspects that come together to deliver this improved performance, but broadly speaking reduced retention helps with faster database look ups and search across the run-time infrastructure.     What's NOT Changing? Aggregated data – including Reports, Dashboards, and Analytics – will not be affected by this change (unless they reference a Smart List with these activities).  The new policy will not affect any activity type other than Sent and Delivered (for example, Was Opened activity data is not affected). Further, this change does NOT affect Engagement Program casts.   What Customer Actions Are Needed? First, you'll want revisit where and how you're using these two activity types. Audit your Smart Lists and ensure the date ranges for these two activity types are less than 90 days - if you must use a date greater than 90 days, we suggest running a process to export to an external system. You will need to create this before the new retention policy takes effect on August 31, 2020.  Information on how to export activities using APIs can be found on our Developers Documentation website.   We appreciate you understanding as we move toward an enhanced Marketo Engage experience for all customers. Please download and review the FAQ attached below for further suggestions, workarounds and additional information.  
View full article