Product Documents

Sort by:
Data Processing Addendum (DPA) This addendum includes all required terms for GDPR compliance, plus Standard Contractual Clauses which serve as a safeguard to govern transfers of personal data out of the EU/EEA/Switzerland. Adobe Sign Data Processing Addendum ​ PDF Data Processing Addendum (DPA)​ Japanese Dual Language DPA This addendum contains all required terms for GDPR compliance, as well as Standard Contractual Clauses in both English and Japanese. Adobe Sign Japanese Dual Language DPA PDF Japanese Dual Language DPA​ If you have questions about the DPA, please review the DPA FAQ document attached to this post and/or consult with your legal counsel .
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
Creating an A/B Test program in Marketo Create a new Program in Marketo:                2. Choose the Campaign folder, provide the program name and choose the program type and the channel: Channel should be Email blast 3. Create a new asset within the program: 4. Choose Email program as the asset: The idea of creating Email program as an asset within a program is to have the ability to track progression statuses in a better way with the original program being the one tracking statuses.        5. Give a Program name and choose the type and channel:     6. Create an email within the email program and approve the email:        7. Go to the Email program created: 8. Choose the email created and approved in the steps above: 9. Add the A/B Test to your email:    10. A/B Testing can be done based on Subject Line, Whole emails, from address and date time: 11. For this example let’s choose subject line: 12. Define the subject lines for the email on which we are trying to test and choose the sample size of the test: In the above example, we chose 20% as the sample size and we have 4 subject lines to test. So 5% of the audience list will each receive email with a particular subject line and the winner will be send to the remaining 80%. 13. Define the Winner criteria based on which the email would be treated as a winner and you can also declare winner manually after viewing the test results: 14. Schedule the test and the winner, choose the email address you want to send notification to: 15. Click on Finish: 16.Verify the details and click on close: 17. Define the smartlist(audience) for this email send: 18. Define the filters for the smart list:    19. The audience details will be reflected in the program now: 20.  Approve the program:    21. Once the test is run successfully, the results can be seen as shown below:   
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
Here are a couple campaign request form templates that were developed to capture all the information needed to build a webinar program in Marketo. I build a lot of these one-off programs and was finding myself spending too much time tracking down information from various people. The attachments are as follows: Campaign Request Form - External (used when campaigns originate from a department outside of marketing (ex. Sales)) Campaign Request Form - Internal (used when campaigns originate from a member of the marketing team) Campaign Request Form - External First tab: this is the tab that the campaign originator will complete Second tab: this is an example of what a completed webinar campaign request form will look like Third tab: this is an example of what a completed email campaign request form will look like Campaign Request Form - Internal First tab: this is the tab that the marketing team member will complete to originate the campaign Second tab: this tab contains the appropriate tokens used for emails/landing pages Third tab: this tab contains the appropriate information for GoToWebinar Fourth tab: this tab contains information need to post a portal ad The additional campaign tabs are added to the external request form once received by the marketing team. We also use a Google form for some project requests. That may be an option too!
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
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
This document contains contractual terms necessary for GDPR compliance and Standard Contractual Clauses. See here for more information on Marketo's Data Processing Addendum (DPA).
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
October 2021 Update https://nation.marketo.com/t5/product-documents/update-to-deprecation-of-programmatic-form-submission-methods/ta-p/317522#M1062 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. April 2021 Update   In November 2020, we announced that we will forbid programmatic Form POST submissions to our /save and /save2 endpoints beginning May 7, 2021. The reason for this change is to reject methods of unsupported form submissions used by bots to fill customer databases with spam data.   We understand that many customers may need more time to update the integrations to use a supported method such as the Forms2.JS API or the Submit Form REST API endpoint. We have decided to extend the deadline in which we will begin blocking all programmatic Form submissions to take place on October 15, 2021. Programmatic FORM submissions continue to be unsupported and while we are temporarily delaying enabling validation to reject these submissions, we cannot ensure uninterrupted submission following  upcoming product and infrastructure changes.   For customers that still wish to block this method of form submission to address bot attacks,   will allow you to opt-in to form submission validation on your subscription. This validation will check that form submissions are coming from Marketo Forms, Forms2.js API, or the Submit Form REST API and will reject it otherwise. This is expected to block many common sources of bot attacks.   However, if you have a form integration that currently uses programmatic Form POST to submit lead data, enabling this feature will also block your Form submissions. We encourage all customers to migrate to a supported method of form submissions as soon as possible to protect their subscriptions from bot attacks.   The original announcement is below for reference. The details remain the same aside from the schedule to block programmatic form POST submissions.   What’s changing? In our May 7, 2021 release, Marketo Engage will be making changes to our form platform to protect the stability and security of our infrastructure:   Forms 1.0 will be fully deprecated, resulting in loss of functionality of any remaining Forms 1.0 assets still in use. Marketo Engage will begin rejecting form submissions made through unsupported methods, such as programmatic form POSTs to the leadCapture/save and leadCapture/save2 endpoints.   Why is this change being made? On August 1, 2017, Marketo Engage deprecated the Forms 1.0 editor, removing the ability to create or edit Forms 1.0 assets. This change will complete our end of life efforts for Forms 1.0.   In addition, we have found that our Form endpoints “leadCapture/save” and “leadCapture/save2” are common targets for bot attacks. To protect the stability of the Marketo Engage infrastructure, and to aid customers in maintaining a clean database, we are completely disabling the “leadCapture/save” endpoint and enforcing checksum validation on the “leadCapture/save2” endpoint.   What customer action is required? Forms 1.0 deprecation Provisioning of Marketo Engage subscriptions with the ability to create Forms 1.0 assets ended December 31, 2014. If your subscription was provisioned after this date, then it will not have Form 1.0 assets. Forms 2.0 assets will be unaffected by this change.   Marketo Engage subscriptions provisioned before December 31, 2014 may still  be utilizing Forms 1.0 assets on their landing pages and website. These forms will need to be remade in our Forms 2.0 editor and replaced wherever they are still being used.   Programmatic Form POST deprecation Some integrations may be performing programmatic form POSTs to “leadCapture/save" or “leadCapture/save2” to submit data into Marketo Engage databases. This method of data ingestion has always been unsupported and will cease to work as part of this deprecation. All integrations using programmatic form POSTs must be updated to use our Forms 2.0 API, Push Lead REST API, or the Submit Form REST API endpoint releasing in the January 2021 release.   Customers using native Forms 2.0 assets on pages and/or the Forms 2.0 API do not need to take any action. Checksum validation will work natively with these supported methods.   What happens if customers don’t act? Customers that fail to replace any in-use Forms 1.0 asset with a Form 2.0 asset will find that their customers will be unable to submit to their 1.0 Forms.   Customers using integrations that perform programmatic Form POSTs to the “leadCapture/save” or “leadCapture/save2” endpoints will see these integrations fail, resulting in loss of form submission data.   Is my Form 1.0 or 2.0? Forms 1.0 and Forms 2.0 have different look and feel:   Forms 1.0 Forms 2.0 Marketo subscriptions provisioned after December 31, 2014 will only have Forms 2.0 assets.
View full article
If you have not heard or seen it yet, in the Fall 2016 Release, we were super excited to launch our Content AI (Predictive Content) for Email. This included a revamp of the Content AI App (previously known as Predictive Content).   Content AI i s an Application Marketo offers that helps you auto-discover your content, engage your web visitors and email recipients with the most relevant, recommended content powered by machine learning and predictive analytics. See more in Docs here:Predictive Content - Marketo Docs - Product Docs   Here are regular FAQs on Content AI we hear from customers and those interested in the App:   General   Where do I learn more about Predictive Content? Marketo.com Website Product Page: Content AI Recommendations - Marketo Customer Success Story using Content AI : Case Study​ / Webinar Video​ Webinar: Behold the magic of Predictive Content​ Marketing Nation Summit 2016: Predictive Content: Amplify your content through machine learning Request a demo from your Account Manager   How do I find the Content AI App? Is it the same as Web Personalization? Content AI is a paid for stand alone App offered by Marketo. It is a separate product to Web Personalization. If you have purchased the Content AI App, you will see a Content AI icon on your My Marketo page. If you are interested in hearing more about the App, speak to your Account Manager.   Setup   Do I need the RTP Javascript tag to enable Content AI on my website and landing pages? The set up process for Content AI (See Getting Started Docs​) includes adding the RTP Javascript Code onto all pages of your website, including landing pages. This helps us to "listen" to your web activity, to auto-discover your content and display it on your web or email channels as Content AI outputs.   A re there any restrictions on where the content resides? Does that content have to reside in Marketo or can it be in any CMS? The RTP Javascript tag is agnostic to CMS platforms, meaning it works on all types of CMS platforms. Once the tag is on your site, we can discover and track all your content (PDF, embedded video, HTML pages) and use it for Content AI . So, the content does not have to reside on Marketo or Landing Pages or Design Studio. The Content AI part that the marketer prepares based on the discovered content and the part that is shown Predictive on your website or within an email is managed and controlled within the Marketo Content AI App.   Content Discovery   How does Content AI discover my website content? Marketo Content AI "listens" to your website activity, and when any web visitor clicks and views a specific content piece (HTML, PDF, Embedded Video, PPT) on your domain, we capture and discover the content title and content URL and start tracking the content's views and engagements. This  discovered content piece is then displayed under the All Content page. For set up details of Content Discovery see: Getting Started with Predictive Content.   Does the Content AI reporting also show which content has the highest engagement? Yes, the All Content page shows all web content (html pages, videos, pdf, etc...) on your domain that web visitors viewed. These results can be displayed from highest views to lowest.   On the Content AI page, the reporting shows how many web visitors or email recipients clicked on the Content AI piece and can also be sorted to see which was the most engaged piece of Content AI per channel (web or email) or overall.   Tracking Content   How many contacts or content do I need to start using Content AI ? Content AI relates to web content. Content Discovery will find in most cases, we have seen hundreds of content pieces on your domain. The marketer can then go ahead and approve and enable these discovered content pieces for Predictive Content. You can also manually add content pieces to the collection. It is recommend you have 10-15 pieces of content enabled for Predictive (for any channel) to start and keep adding more to this.   Can you create your own Conversion Criteria ? We track and display the views on content and also clicks on Content AI . In addition, the metrics we show are conversions (direct and assisted) per content piece, which shows attribution to the content piece in bringing in new People. Conversions : The number of visitors who clicked on recommended content and completed a form in the same visit Assisted Conversion : Visitors who clicked on recommended content in a past visit and completed a form later Currently, you cannot create your own conversion criteria.   Content AI Algorithm   Can you clarify on how the algorithms predict the content? The Content AI algorithms use machine learning and predictive analytics to decide and recommend which pieces of content are relevant for each visitor or email recipient individually. We use a mixture of algorithms that are constantly optimized and improved for best performance and results analyzing clicks and conversions. The algorithms are based on trending, popular content viewed on your website, new pieces of content added to your site, and also takes into account URL paths and user behavior clicks and visits.   Will Content AI show content the visitor or email has already received? There are certain checks and validations in place in order to provide the best experience for the end user receiving Content AI . These include: The Recommendation Bar will not recommend a piece of content the web visitor is currently browsing The Rich Media Recommendation will not show repeat predictive content on the same page and if the user clicks on a piece, we will not recommend the same piece of content they clicked on during that visitor's session. In Predictive Content for Email, a email recipient will not see the same Predictive Content more than once in follow up emails sent with Predictive Content in them.   Does Predictive Content now take into consideration any type of segmentation? So predictive content for segment A versus segment B? No, it is not related to segments, and this would be more of a rule-based style Web Personalization campaign. Instead, Predictive Content takes into account many variables to calculate before producing the Predictive outcome result for each visitor. Predictive Content can also be categorized and shown per category in the Rich Media and Email. See more here: Set Up Categories in Predictive Content   Is the Predictive Content picked at random, or is it based on customer criteria? The Predictive Content is prepared and approved by you. You also select the look and feel of the outcome and where it will appear on your site or in your email body. However, in the end it's the Algorithm that decides which of the approved Predictive Content pieces is best to show the current web visitor or email recipient.   Displaying Predictive Content on Web or Email   What are the Character Limits (Char limits) for predictive content on Web and Email?   Content Name: 255 Chars Bar Title: 110 Chars Rich Media Title: 50 Chars Rich Media Description: 215 Chars Email Title: 50 Chars Button Label: 17 Chars   The char limits are in place in order for the text to fit into the defined styling and look for the bar, rich media and email layout.   Can you see which pieces will be promoted in the email before sending the email? As the marketer, you can prepare and approve the piece of content for each source (email, web). In the end, the Predictive Algorithm decides what the end user will receive. For Predictive in Email, you can preview the layout and category of the Predictive Content, however the Predictive image is not seen until the recipient opens the email, so what you see in the preview is just an example, and will not necessarily be the image the recipient sees. See the process for setting it up and previewing Predictive Content in Email here.​   Can we use only Marketo landing pages, or anything under our company webpage domain? Yes, you can define all html pages, including landing pages, as content pieces to use in predictive. You can also manually add new pieces of content to the application.   Do you recommend Predictive Content for Marketo landing pages? Particularly Thank you pages? Predictive Content for web in the form of the Recommendation Bar or Rich Media is suited for all types of pages. We have customers using rich media on their home page (3 pieces of Predictive Content in horizontal format) below the fold of the home page. We have the Bar running on Blogs or Resources pages. A Thank You page or Thank You email is a great use case to add Predictive Content as these pages or email, usually do not have any call to action, and adding Predictive Content can help create more clicks and engagement by the viewer. You can categorize your predictive content for Rich Media and Email so it would be recommended to show on that Thank You page Predictive Content related to the thank you submission (eg. white paper, case study, webinar, blog post).   Can you alter the code of the predictive content to be flush with a font style/coloring? Predictive Content Rich Media for Web can be styled accordingly with font and colors. See here: http://developers.marketo.com/javascript-api/web-personalization/rich-media-recommendation/​. Predictive Content for Email is a Predictive image generated upon email open, so it is offered as 8 different fixed layouts and the Marketo user selects one. See documentation here: Enable Predictive Content in Emails.   Can you use categories in the "web" or "rec bar" versions like you can in emails? You can use Categories in Rich Media for Web and in Predictive for Emails. Currently, the Recommendation Bar does not support categories. Categories allow you to group your content and present predictive outcomes on web (rich media) or email. For example, you can work only with blogs, or with content in a particular language.
View full article
  Whether you’re new to Marketo or trying to clean up a mess, you may wonder what you can do to keep your Marketing Activities organized within your instance. Through hiccups and hair pulling, our team has finally discovered a great way to keep ourselves organized, which has enabled us to work more efficiently. Take a look at what we’ve done and determine if it’s the right fit for your organization. In the Marketing Activities section of our Marketo instance, our main folders are set up to represent different activities that are performed in Marketo. Example: > Active Marketing Programs >Demand Generation Programs >Customer Support / Operational Activities >Operational >Archive Folder >Learning Folder Within those folders, we have additional folders that are broken out by the various channels we use. *Active Marketing Programs example below Example: > Active Marketing Programs > Digital Ads > Email Blasts > Events > Newsletter > PPC > Website Within those folders, we've create more descriptive folders for the various campaigns running in each channel. *Event example below Example: > Active Marketing Programs > Digital Ads > Email Blasts > Events                 > Trade Shows                 > Webinars > Newsletter > PPC > Website We have several campaigns running in each channel, so we've built out folders to specify by a specified time frame (year and quarter). *Webinars example below Example: > Active Marketing Programs > Digital Ads > Email Blasts > Events                 > Trade Shows                 > Webinars                                 > 2015 Webinars                                                 > Q1 – 2015 Webinars                                                 > Q2 – 2015 Webinars                                                 > Q3 – 2015 Webinars                                                 > Q4 – 2015 Webinars > Newsletter > PPC > Website Within the specified time frame folder is where we house our individual campaign folders that contain our programs and other local assets for the campaign. For these folders, I’ve found it helpful to follow a very structured naming convention. This helps to ensure that our instance stays organized and everyone working in our instance knows how to label items. My recommendation would be to use the channel type, the date (YYMMDD) and brief description of the program (for our webinars we use the time of the webinar, the service name we're promoting, and the target audience of the campaign). Below is an example of our webinar folder structure. Example: > Active Marketing Programs > Digital Ads > Email Blasts > Events                 > Trade Shows                 > Webinars                                 > 2015 Webinars                                                 > Q1 – 2015 Webinars                                                                 > Webinar – 150205 11 AM SERVICE A – PERSONA 3                                                 > Q2 – 2015 Webinars                                                 > Q3 – 2015 Webinars                                                 > Q4 – 2015 Webinars > Newsletter > PPC > Website This folder houses our event program for the webinar (the event program has the same naming structure as the folder). We also use the same naming structure for our SFDC Campaign Name. Check with your Sales team to see if that’s a viable option for your organization. The folder also houses our "granular channel programs" that we use to attribute success to the various channels we use to drive traffic to the webinar event (such as PPC, email, social, etc.). Happy Building!
View full article
General Icons Icon Name Folder, New Campaign Folder Create New Folder Delete Folder Edit/Rename Folder Name Archive Folder or Convert to Archive Folder (This can appear for any folder and archived Programs) Success! (Frequently shown as Program Success, Successful Run, or Active) Filter, View, View All Community History Help Subscription Information Customer Support About Marketo Admin Icons Icon Name Workspaces & Partitions My Account Security/Logout Users & Roles Login Settings Location Smart Campaign Email Communication Limits Field Management Integration Salesforce (SFDC) Sales Insight Landing Pages Munchkin Web Services LaunchPoint Webhooks Tags - Program Attribute Revenue Cycle Analytics Treasure Chest Admin Notifications - Important Systemwide Alerts Marketing Activities Icons Icon Name Event Program Program - Default Type Import Program Engagement Nurture Add to Engagement Program Change Engagement Cadence (Paused,Normal) Change Engagement Stream Smart Campaign - Active and Triggered Smart Campaign that is Requested (By Sales Insight or Marketo Flow Action) Smart Campaign - Batch (Has been executed before) Smart Campaign - Inactive, or never executed Invalid Campaigns Program - Email Send (A/B Test) Smart Campaign - Scheduled Batch (Check mark indicates it has been executed before) Scheduled Batch Campaigns Flow Action Edit Settings Form Clone Form Edit Form Form Approved Social Social Button Actions Edit Draft Preview Clone Delete Embed Code Youtube Video Actions Edit Draft Preview Approve Clone Delete Sweeptakes Actions Edit Draft Preview Approve Clone Delete Pick Winners Download HTML Move Delete Clone Unapprove Send Sample Preview New Test Deliverability Tools Design Studio Icons Icon Name Landing Page. Landing Page Actions Edit Draft Preview Unapprove Publish to Facebook Convert to Test Group Clone Landing Page Delete Landing Page URL Tools/URL Builder Move Program Enable Personalized URLs Landing Page - Approved Landing Page/Email Template - Unapproved Landing Page/Email Template - Approved Email - Unapproved or Draft Email Approved Forms - Unapproved Template - Approved with Draft Draft of an Approved Asset (not live until Draft is Approved) Images & Files Snippet - Unapproved or Draf t Snippet - Approved New Grab Images from Web Upload Image or File Analytics Icons Icon Name Revenue Cycle Model Revenue Cycle Model (RCM) - Unapproved Revenue Cycle Model (RCM) - Approved Revenue Cycle Model (RCM) - Approved with Draft Report Actions Report New Report Subscription Delete Report View Qualified Lead Interesting Moments Expand All Collapse All Group Leads By Custom Columns My Tokens Icons Icon Name Calendar ICS - iCalendars, (Integrated Calendars) Rich Text (not a Landing Page) Number Salesforce (also on all SFDC related items) Schedule the Smart Campaign to Run Once Edit Settings Refresh (Usually Run Count, Report, Smart List) View Smart Members (Previously qualified, and current) Campaign Menus Icon Name Schedule Recurrence of Campaign (Multiple Runs) Cancel the Run, Action, or Delete Edit Qualification Rules Salesforce (also on all SFDC related items) Text Only Relative Score (also visible on all Scoring flow actions) Relative Urgency Email Script (for Velocity only) Date - Formatted as "MM-DD-YYYY" Lead Database Icons Icon Name Smart List Smart List - Cached Segmentation Or Segment - Unapproved Segmentation Or Segment - Approved or Draft Segmentation Or Segment - Approved Field Organizer Email Script (for Velocity only) Static List New New Segmentation Import
View full article
Basic Nurturing Advanced Nurturing Measuring ROI Calculating the ROI of Nurturing Understanding the Engagement Dashboard Basic Reporting - (Login Required) Measuring ROI Understanding Engagement Scores Engagement Stream Performance Reports Defining Nurture How to Create a Nurturing Strategy Working with Engagement Programs (Login Required) Add Streams to Your Program Optimizing Nurture How to Test and Optimize Nurturing Engagement Engine, Scoring, and Data Management - (Login Required) Segmenting for Nurture Basic Nurturing Segmentations Segmenting for Nurture Advanced Nurture Segmentations Transition Leads Between Engagement Streams Engaging with Content How to Create Content on a Budget Content Marketing Tactical Plan Worksheet Add Content to a Nurture Stream Nurturing Across Channels Your Multi-Channel Nurturing Strategy
View full article
I previously answered a question in the discussions about this topic and figured I would share a bit more details about it. Feel free to post questions/feedback and I'd be happy to update this. UTM tagging, extra work and how to make your email templates more efficient Having even a few users simultaneously creating emails in Marketo risks a misalignment and if you have a tagging strategy for Google Analytics everybody might not follow it. Some may ask: "Why do we even need to use utm tags if we have Marketo?" - Well, for one everything should be tagged up both incoming traffic to Marketo and traffic generated by Marketo. The ideal situation is to be able to easily see what traffic is driving conversions/goals. What works vs What doesn't. The ideal situation is for these tags to always work without requiring users to need to think or spend too much time trying to figure out how to tag their link. With the new 2.0 email editor with variables all you need to do is add Local Variables to each module for both the link and the utm tag (this should be done in the template). Alternative 1 - Whole UTM string in one variable Variables defined: <meta class="mktoString" id="link-variable" mktoName="URL" default="#" mktoModuleScope="true"> <meta class="mktoString" id="utm-tag" mktoName="UTM" default="?utm_source=mkto&utm_medium=email&utm_campaign={{program.Name}}" mktoModuleScope="true"> To describe the values a bit better: mktoModuleScope (case sensitive): a boolean variable (true/false) meaning it needs to be included and marked true if you want it to be unique on a modular level, otherwise it will use the same value across the template. {{program.Name}}: The new program token for name can also show the program name from where the traffic came from, works great if you have a good naming convention. This should also fix itself if you are using spaces in your program names to not break the link and to show the same value in GA. default value: The value that will always be present mktoName (case sensitive): The friendly name to be displayed to whomever is editing your post Whenever you want to add a variable to an email (or landing page) template, you refer to it's previously defined id from the head: ${id} After these are defined, all you need to do is add the corresponding variables defined inside the links in the code for your modules. Looking something like this: <a href="${link-variable}${utm-tag}"> Alternative 2 - Split up each UTM tag into multiple variables If you are regularly adding e.g. utm_content tags for differentiating different variants this may be friendlier for you. This can also be done by defining five variables, one for each utm_parameter value and just have the default value blank (if you don't usually use it) or fill in the default like the example above (utm_medium=email etc..) <a href="${link-variable}?utm_source=${utm-source}&utm_medium=${utm-medium}&utm_campaign=${utm-campaign}&utm_term=${utm-term}&utm_content=${utm-content}"> If a link contains a blank utm_parameter with & following it, GA should skip it and move to the next one without causing a broken link. When this is done you are ready to get going with your email sendouts so they automatically track your defined UTM tags. For more tips and tricks, feel free to check out erikheldebro.com​​​
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
Great PDF File to help you organize Marketo.
View full article
Email performance analytics sits at the heart of every digital marketer, you want to be aware of how the performance has been and need the ability to report on the same using various dimensions relative to your marketing. More often than not, all marketing automation systems have a performance issue when it comes to providing analytics quickly with the parameters that you would like. Marketo has also been lacking in this area for quite some time since RCA is sold as a separate product and that also had performance issue till last year or so, when the UI was changed but still performance is not up to the mark and Marketo analytics is not that powerful a feature to suffice the digital needs of today. As a resolution to the same, Marketo has introduced Email insights to provide lightning quick reporting on Email performance with a plethora of dimensions/parameters to filter your report. It works real fast and allows you to report on performance which not only includes batch campaigns but can also include trigger campaigns and operation emails (You can choose to exclude them as well). There are options of choosing performance relative to one/multiple workspaces, you can add parameters such as segmentations, channels and program tags and include them as dimensions and report on them. There’s an option to filter the report on Audience (country and state parameters), Content (email, program, smart campaigns, theme) and Platform (Device OS and Device type). You can generate charts to assess the performance during selected period based on Time (Day, Week and Month) and filter on various parameters. On the right hand side you can also select metrics such as opens, clicks and unsubscribes to check on the performance by parameters of audience, content and platform. You also have the ability to save these reports as quick charts for periodic performance review, you can save up to 20 quick charts. Although it’s a fresh new option for analytics there’s a lot of scope for improvement, for example. The ability to export data/reports/charts is not available so if you want to share the data with anyone outside Marketo you can’t, which is a huge disappointment. There’s no option to report on custom parameters such as conversions, program successes etc.  There are only 10 custom dimensions that can be added which makes the set up limited. The ability to report on custom lead filters using smart lists as available in Email performance reports is not there. There’s no email link performance analysis. Overall a fresh new interface and a much needed option for Email performance reporting but still has a lot of scope for improvement. Here’s the Summary: Pros: Lightning quick reporting capabilities. Dimensions and work-space options for reporting. New filter options such as Audience, Content and Device. Ability to create quick charts. Cons: Inability to export reports Only 10 custom dimensions No custom lead filters and custom parameters No Email link performance analysis Here’s an example of how to use Email insights for your reporting purposes, it includes the steps you need to follow to leverage the various capabilities available for reporting. Log into Marketo and click on the tab on the top left hand side to go to Email Insights: This is how Email Insights home screen looks like: It provides you a lot of options of choosing to report on, you can select the Workspaces on which you want to see the performance: In this example, I want to check the performance in Europe, so I’ll choose Europe as the work-space. You can select the dates for which you want to check the email performance: There’s an option of comparing periods as well. You can click on sends on the top left corner to check the various email sends during the period and choose from it the one that you are interested in: If the desired email communication doesn’t show up here, then it could be because it is an operational email, the general settings of Email insights excludes the operational and trigger campaigns, you can change the same in the personal settings: There are a lot of parameters on which Email insights allows you to filter, one of them is Audience. You can filter the audience from country/state and check the email performance for them, for example: If you want to report on email performance during the last month in California etc. You can also filter on specific content, which can be either email sends: Select the email send you want to check the performance. You can also filter on Smart campaigns and the same would reflect in the report: Similarly program filters are also available: A new and fresh addition would be the ability to report device and OS performance, although this option is available as a constraint in Marketo Analytics, this is much better and faster, as it provides you comparative performance views on devices, which is nor the case with Analytics: You can select the Operating systems as a filter as well: There are filters available on your left and right side and you can select either to modify the report/chart: Here’s an example of filtering using parameters on the left side: On your right hand side you have options of choosing filters as well, by default all filter options will show: You can click on Audience, content and device to filter on and analyze the performance further: You have an option of viewing the performance by time as well in the selected time frame, you can select from day, week and month and the report will be modified accordingly: You can also add custom dimensions to these reports which can be used as a filter. To do so, click on the settings option: You can go to System settings to add dimensions, you can add segmentation, channels as dimensions and report the performance on them. Program tags can also be added as a dimension, a maximum of 10 dimensions are allowed with Email insights: Once you are done creating your report/chart based on all the filters and parameters, you can save it as a quick chart for periodic performance review: Name the chart and save it: You can it on the quick charts option on the right hand side, a maximum of 20 charts can be saved: Hope this was informative and helps you in leveraging Email insights for your organization. Your feedback matters a lot to me so if you have any suggestions/comments/queries relative to this, please comment below.
View full article
Included in this article Summary Anonymous Web Activity Logging Triggered Smart Campaigns Smart List Filters Summary The goal of the upgrade to the anonymous lead promotion process is to increase the capabilities of what Marketo can do for you. With this upgrade, Marketo will be able to increase the volume of web events we track significantly. With a substantial upgrade like this, there are many technical details, so here’s a peek under the hood to see what the moving parts are. Anonymous Web Activity Logging Anonymous lead activity will be logged in a new way that doesn’t create a traditional lead record. 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 Without a lead record, 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. 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.         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. 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. Smart List Filters The “Is Anonymous” filter will be removed so it can’t be selected any more. This doesn’t remove the filter from where it’s already in use, it just removes it from available filters. Any “Is Anonymous” filter still in use will have the following results:           1. “Is Anonymous” = True Smart Lists will return zero results, Smart Campaigns will fail and won’t run.           2. “Is Anonymous” = False The filter is ignored because all leads will be known.           3. “Is Anonymous” = True in combination with “Is Anonymous” = False using OR filter logic Smart Lists will return zero results, Smart Campaigns will fail and won’t run. The “Is Anonymous” filter needs to be removed from any place where it is in use. For more detailed information about this, please visit the Customer Action documentation here.
View full article
Included in this article Summary Since the “Is Anonymous” filter is being removed, Analytics reports won’t be able to add it into the smart list of the report. The “Is Anonymous” filter will be taken out of the available filters that can be chosen, but is not removed from any Smart Lists where it is currently in use. For more information about removing the filter, please visit the Customer Action documentation here. Reporting on Anonymous Web Activity Just because the “Is Anonymous” filter is being removed doesn’t mean you can’t get reports on anonymous web activity. The Web Page Activity Report and the Company Web Activity Report will continue to show anonymous web activity. To get anonymous activity to show in the report, follow these steps: 1. Navigate to the Setup tab and double click on the “Activity Source” setting. 2. In the dialog box, select which source you'd like to view. Your report will now show anonymous web activity! Affected Reports Not all Analytics reports allow smart lists, so not all Analytics reports will be affected by this upgrade. The reports below will be the ones affected and will have the "Is Anonymous" filter removed: Web Page Activity Company Web Activity Email Performance Lead Performance Engagement Stream Performance Email Link Performance Lead By Revenue Stage Leads By Status Sales Insight Email Performance
View full article