Your Achievements

0% to

Next /

to gain points, level up, and earn exciting badges like the new !

View All Badges

Open Alert Bar

Knowledgebase

Featured article

(Article Updated - August 2024) Overview A blocklist is a database of IP addresses or domains that have been associated with the sending of unsolicited commercial email or spam. Internet Service Providers (ISPs) and business email networks use information from blocklists to filter out unwanted email. As a result there can be a drop to inbox delivery rates if the IPs or domains involved with sending email are listed on a blocklist. Marketo’s Email Delivery and Compliance team monitors blocklist activity on our IPs and domains daily. When an impactful listing occurs, we reach out to the blocklist, attempt to identify the sender that triggered it, and work with the blocklist organization to get the listing resolved. There are thousands of blocklists, most will not have a significant impact on your delivery rates. Below, we have compiled a list of the blocklists that commonly appear across our sender ecosystem. Each blocklist has been grouped into a top tier (Tier I) by most impactful, to the bottom least impactful tier (Tier III). These may have little to no impact across our sender network. Tier I Blocklist Spamhaus (SBL) Impact: Spamhaus is the only blocklist that we categorize as a Tier I for a reason: it has by far the greatest impact on delivery. It is the most well-respected and widely used blocklist in the world. A listing at Spamhaus will have a negative effect on your ability to deliver emails to your customer’s inbox and can cause bounce rates of over 50%. Evidence suggests that most of the top North American ISPs use Spamhaus to inform blocking decisions. How it works: Unlike many blocklists, Spamhaus lists senders manually. This means they are proactively watching sender activity, collecting data, and base listings on a number of variables. Most commonly senders are listed for mailing to spam trap addresses that Spamhaus owns. Sometimes Spamhaus will list senders based on recipient feedback as well. Next Steps: Please note that every Spamhaus email can be quite different depending on the information provided and the nature of the listing . Because Spamhaus has multiple types of listings, the remediation steps are based on which type of blocklisting has occurred. We have listed the most common types to affect Marketo customers, from most to least impactful. Impact can range from a full block of top severity, to a partial block that is less severe (CSS Data, DBL). If remediation isn’t performed and the problem not addressed, these listings can increase in severity and turn into a full blocklisting. Spamhaus Blocklistings Types SBL (full blocklisting) Considered the most impactful. Remediation steps: Our team monitors closely for Spamhaus listings. Once alerted to the listing, we send an email notifying the customer, and reach out to the Spamhaus contact to start the remediation process. Only a Marketo delivery team member should be in direct correspondence with the Spamhaus contact, to speak on behalf of the customer, and to relay their questions and instructions, ensuring quick resolution and reduced impact. Senders that trigger this listing on a shared IP range will be moved to a more isolated, penalty range (IPB), so as not to impact the other shared senders. Those affected on a Dedicated IP, only impact their own sending and will not be moved. However, depending on the severity of the issue, our team may need to revoke a customer’s ability to send any emails until full resolution. The listing will last until Spamhaus is satisfied that the offending sender has taken the appropriate steps to mitigate the problem. SBL CSS Customers are alerted of the listing with an email containing all the information needed to immediately begin the remediation process. This is part of an automated trigger listing, that allows for a customer to delist directly on the Spamhaus website, after they’ve completed remediation. Remediation steps: Customers will go to the Spamhaus IP lookup website, at https://check.spamhaus.org, where they can check on the status of their IP and continue to monitor it in real time, until it is no longer listed there. Follow the remediation and delisting instructions provided, and check for specific details in the blocklist notification email. DBL (Domain blocklisting) Customers will receive an email notification alerting of the company domain being listed. The email will contain specific information to help narrow down and identify which email source likely triggered it within Marketo. It’s important to note that any email sent from outside of Marketo, that contained the company domain, is suspect. This means, if the sender uses multiple IPs and/multiple email platforms, then any of those could be the source. Remediation steps: Follow the detailed instructions in the email, which will also provide a link to the Spamhaus Domain reputation checker webpage, to check the real time listing status of the affected domain. Once the email source is identified and cause addressed, this customer will follow the online instructions to request to be delisted. Tier II Blocklist SpamCop Impact: SpamCop is not used by any of the major North American ISPs to inform blocking decisions, but it makes it to the Tier II list because it can have a significant impact on B2B email campaigns. SpamCop is considered a Tier I one blocklist for B2B marketers but a Tier II for B2C marketers. SpamCop is a dynamic IP blocklist, that can affect a single IP or a subset of IPs Typically, the block will automatically lift within one business day, but can take longer for relisted IPs. To have triggered a SpamCop listing likely means the sender has a list management problem that should be addressed. How it works: SpamCop lists IPs for one of two reasons: Either the email hit SpamCop spam trap addresses OR A SpamCop user has reported the email unwanted. Most of SpamCop’s spam traps are previously valid addresses that have not been active for 12 months or longer. Remediation steps: If you are seeing a significant number of bouncing emails caused by a SpamCop blocked IP but aren’t sure if your email activity triggered the listing, first identify whether you are sending on a shared sender network or not. If sending from a shared IP range when this occurs, you or any other customer sending from the same network may have contributed to the IP block. This IP block will automatically get dropped within a business day. For those on a Dedicated IP that trigger a listing, refer to the above remediation steps and resources, to address the list management issue. Tier III Blocklist (Low/ No impact ) These are considered the lowest tier and therefore cause the least impact across the Marketo sender ecosystem. Some of these blocklists were more impactful at one time, while others are only impactful based on the sender region (Manitu). Others still can suddenly flare up (Lashback). There are also many blocklists that are ignored (0spam), and are not taken seriously because they do not provide any means to delist once on the list (NoSolicitado) or that they charge money to have the listing removed ( UCEPROTECT ). The pay-to-delist model is not well respected in the email industry. When using blocklist tool checkers, such as MXToolBox, many blocklists will appear, but very few are relevant. Here is our selection of Blocklists you may come across that are least impactful: Project Honey Pot SpamAssassin URIBL/SURBL DrMX PSBL 0spam HostKarma Ascams ZapBL Barracuda Trendmicro Inc. Cloudmark Proofpoint Invaluement ISP Blocklists Some ISPs use internal blocklists to make blocking decisions. Examples include AOL, Yahoo, Gmail, Outlook and Hotmail. If your IP is being blocked by one of these networks, and those networks have a large presence in your lists, a block of this kind could have a noticeable negative impact on delivery. Marketo monitors for significant ISP blocks. Those experiencing deliverability issues with emails not making it to the Inbox and bulking in the spam folder may benefit from additional services with our Email Delivery Consultants. Remediation Steps: Email Delivery Compliance Team works to resolve any ISP blocks. ISP blocks are are usually resolved or lifted within less than 24 hours of a delisting request. Customers experiencing significant blocks for Microsoft domains (outlook.com, live.com, microsoft.com), can submit a request to the delivery team to seek mitigation on their behalf. Additional Resources: Blocklist Deep Dive Abuse Report Deep Dive What is a spamtrap, or spam trap, and why does it matter? Blocklist remediation Blocklist resolution flowchart Successful lead reconfirmation What is a blocklist?

Issue Several types of fields in Marketo have requirements for the type of data that can be stored, as well as the limit to how much data can be contained in that field type. The Custom Field Type Glossary can tell you what fields are available, and this article will show you details on the type and maximum limits for those fields. Field Types & Limits Boolean Can only be set to “true” or “false” (stored in the database as 1 or 0). Currency Maximum value of 9223370000000000000. Will be displayed with the currency set in your instance under Admin -> Location. Date Must be formatted “MM/DD/YYYY”. Datetime Must be formatted “MM/DD/YYYY HH:MM:SS”. Email Must be a properly formatted email (user@example.com). Float Can include decimals up to the hundredths place. The value will round to the nearest hundredth (eg. 99.999 rounds to 100, 99.985 rounds to 99.99). Maximum value of 10000000000. Formula See this guide: Create and Use a Concatenated String (Formula) Field Integer Values are limited to between -2147483647 to 2147483647. Percent Must be a full number without decimals. Maximum value of 9223370000000000000. Phone Can have letters, numbers, or characters. Maximum of 2,000 characters. Score Maximum score of 2147483647. If the score is increased higher than that, the score will reset to -2147483647. String Can contain letters, numbers and special characters. Limit of 255 total characters Text Area Can contain letters, numbers and special characters. Limit of 65,535 total characters URL "http://" will automatically be appended to the value if the value doesn't have that prefix or "https://" already. Does not have to be formatted any further (Generic top-level domain not required).

Issue You receive the below sync error notification which states "CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY: [process/workflow name]: System.LimitException: Apex CPU time limit exceeded" Solution The error means that you have one or more triggers running when the leads are inserted that consume too much CPU time. You are hitting what are called SFDC Governor limits. This is really something you need to review with your SFDC admins and developers. Consider moving some workflows from Triggers (synchronous) to batches (asynchronous).

Issue Executing a GET API call to retrieve a list of available activity types in the target instance using the '/rest/v1/activities/types.json' endpoint, resolves with an unexpected attribute name for a field with the display name ID in the context of Marketo Custom Objects. An example of that may be a Marketo Custom Object with the following name: '3 to be', as can be shown in the image below: One of the '3 to be' Marketo custom object fields name is 'ID'. (highlighted in red). When performing a GET API call using the '/rest/v1/activities/types.json' endpoint, you will be getting a list of available activity types in the target instance, along with associated metadata of each type, however for a Marketo custom object with an ID field name, you may see it returns back with a slightly different name, in this case, it would be returning the following output for my test Marketo Custom Object activity: { "id": 100019, "name": "Add to 3 to be", "primaryAttribute": { "name": "3 to be ObjRef", "dataType": "integer" }, "attributes": [ { "name": "3 To Be Person Id", "dataType": "integer" }, { "name": "ID (3)", "dataType": "string" }, { "name": "Linkfield4", "dataType": "string" } ] } ], Here's an image of what it may look like when making the call using POSTMAN: In fact, the character in the brackets next to the ID field represents the very first character of your Marketo Custom Object name. Environment Customers who have Marketo Custom Objects where one of the custom object fields is named 'ID'. Solution If this is interrupting your business, you may want to select a different name for the ID field under your Marketo Custom Object. (ie. ID number, Transaction ID etc.) Root Cause This behavior is expected and is a result of the 'ID' field being a unique field in the context of Marketo custom objects world and while it may be possible to create a Marketo Custom Object field with the name 'ID', it may be better to give it a distinct name that will be better describing what kind of ID field it is.

Issue Clicking a tracked link in an email either leads to a 404 page or the fallback page. Environment Tracked links Tokens Specific Characters: "#", "$", unbalanced brackets "{" or "}" Solution Do not use the following characters "#", "$", unbalanced brackets "{" or "}" in a link that is tracked when using a token as well. For example: www.google.com/ebook-download.html?ebook={{lead.ebook}}# This will not work and will either direct to a 404 page or redirect to fallback page. When hovering over the link you will see that it is not a normal tokenized link, it will contain something along the lines of: $mktEncrypt.encrypt($mkturl2)/<random characters> Root Cause When using tokens in the url of a tracked link, the email is processed and the tokens are substituted and populated with the correct information. The engine that assembles this information have some characters reserved for use such as #.

Issue When comparing the Engagement Score on the Engagement Dashboard, the scores do not match with the Email Insight Engagement Scores. Environment Engagement Program Email Insight Solution The Engagement Score from the Engagement Dashbaord will hold the most accurate information as this is direct information, rather than for example with RCA/RCE and Email insights where the data source is different. If you want to see Engagement Score over a period of time more accurately, use the Engagement Stream performance report: Engagement Stream Performance Report | Adobe Marketo Root Cause The Engagement Score on the Engagement Dashbaord only calculates the last 3 casest, it is also important to remember that the engagement score only includes emails that were cast more than 72 hours ago. As per this documentation: The Engagement Dashboard | Adobe Marketo In comparison, the Email Insight Engagement Score is calculated over a period of time that is set by the user but the data can still be mismatching, this is due to the fact that the data source is not the same from the Engagement Dashboard.

Issue Emails cannot be delivered from the Marketo instance and the following Soft Bounce code was recorded in the record's activity log. 554 5.4.7 [internal] (last transfail: 435 5.7.8 Authentication credentials invalid) Environment Dedicated IP Address SMTP Relay credential invalid Soft Bounce Code: 554 5.4.7 [internal] (last transfail: 435 5.7.8 Authentication credentials invalid) Cannot send email Email Delivered not recorded in activity log Solution Provide Marketo Support with the updated credentials so Support can create an internal request to get the update the credentials on Marketo's end. The process can take up to three (3) business days to complete. Note: Avoid using special characters in the password such as quotation mark (") as it can alter the configuration. Root Cause The credentials for the SMTP Relay has been changed and no longer match what is stored in Marketo. In most cases it is the password as it need to be change on an annual basis.

Issue When editing the expiration date for a user in Admin by completely removing the expiration date set to null and clicking save. The change is not saved, and the expiration date remain. Environment Expired Date for user Expiration Date Changing the expire date to never in Admin Solution There are two options: 1. Change the expiration date to a date in the future. 2. Delete the user in Admin and recreate the user again and set the expiration to never. *Please note that if option 2 is selected, the history of the user is will be lost and this cannot be retrieved. Root Cause This is a design limitation as it is expected for the user with an expiration date to be deleted from the Marketo Instance after the expiration date has been reached.

Issue When changing Program Status in Admin > Tags > Channel for "Event" result in this error, "Failed: no more information". Environment Changing Program Status Failed: no more information Solution "System mapping for Registered, Waitlisted, and Attended statuses is required." Therefore, ensure the status is mapped to Registered, Waitlisted, and Attended. Root Cause One or more of these statuses "Registered, Waitlisted, and/or Attended" were not mapped as required.

Issue The format of the landing page is distorted in comparison to the version displayed in the landing page preview. Environment SSL Certificates Landing Page Domain Landing Page format is different from preview Landing Page contain unsecure content Landing page template has http instead of https Solution Ensure all the links used in HTML code used in the landing page template is referencing "HTTPS" and not "HTTP". You can follow the steps outlined in the document below on how to edit landing page template. Link: https://experienceleague.adobe.com/docs/marketo/using/product-docs/demand-generation/landing-pages/landing-page-templates/edit-a-marketo-landing-page-template.html **NOTE: If the landing pages is approved, a draft version of the landing page is created for any landing pages which is using the landing page template. You can mass approve those landing pages via following steps outlined in the document below. Link: https://experienceleague.adobe.com/docs/marketo/using/product-docs/demand-generation/landing-pages/landing-page-actions/approve-multiple-landing-pages-at-once.html?lang=en Root Cause Once you secure your Marketo landing pages to be served over "HTTPS", you should have not links referencing "HTTP" (unsecured) assets or pages.

Issue When adding new IP Address to the IP Restrictions list on Admin > Login Settings > IP Restrictions, you receive this error message: "Your current IP address (XXX.XXX.XXX.XXX) cannot be blocked." Environment Admin IP Restrictions Login Solution Ensure that you have Admin Access to the Marketo instance and that you have logged into the Marketo instance via one of the IP Addresses listed on the IP Restrictions list. Root Cause User logging into the instance with an IP Address not on the IP Restrictions list.

Issue What type of HTTP Redirect Rules does Marketo use when you setup a redirect rule in Admin > Landing Pages? Solution Internal Pages such as landing pages hosted on Marketo will use a HTTP 301 Redirect External pages & non landing page URL's (when using "non-Marketo landing page") used in the redirect rule will utilize a HTTP 302 Redirect: Branding links do not use an HTTP Redirect and use a script-based redirect on the Branded links page. Example: Email branding link - http://go.mybranddomain.com/ABCDEFIlB0ETg0X063WLL1 is a Marketo hosted page that utilizes a script to redirect & point to http://www.thetargeturlinanemail.com

Included in this article Overview Sync Filters for Existing SFDC Integrations Sync Filters for New SFDC Integrations Overview It is often necessary to prevent specific leads from syncing between Marketo and SFDC. There are a few different ways this can be done, such as sharing rules on the SFDC side, but the most effective way is through a Marketo Custom Sync Filter. A Custom Sync Filter uses a custom field to mark each lead record to indicate whether that lead is allowed to sync between Marketo and SFDC. Here’s how to get it set up! Sync Filters for Existing SFDC Integrations If you already have an SFDC integration in place but want to stop some already-synced leads from continuing to sync, this section will show you how to make that change. 1. Create a new custom field in Salesforce. The Marketo bi-directional sync will automatically identify the new custom field and map it between Marketo and Salesforce. The best field type to use is a Checkbox field within Salesforce and the field will need to be created on the Salesforce Object that needs to be filtered (i.e. Lead, Contact, or both). Once the field has been created in Marketo by the bi-directional sync, it will be listed under Admin > Field Management. Note: A Custom Sync Filter field can also be created on the Account object to dictate whether an account is allowed to sync. This sync filter will be applied independently from the Lead/Contact sync filter. 2. Update the records in Salesforce with the corresponding value you need to indicate whether the record should sync or not. Sync filters can be set up in two ways—a True/Checked value can indicate that a record is allowed to sync, or a True/Checked value could indicate that a record is not allowed to sync. This choice is up to you. 3. The Custom Sync Filter can now be implemented. Contact Marketo Support and request a Custom Sync Filter be activated. Be sure you include the custom field name, which configuration you need (checked=sync vs checked=don’t sync), and all records have been populated with the correct values. Once it has been applied, you’re all done! Sync Filters for New SFDC Integrations If you are setting up a new SFDC integration with Marketo, you can set up the sync filter as part of the integration process. This will let you designate which leads and contacts are ever allowed to sync, but this must be done in the middle of the initial SFDC sync process. 1. Create a new custom field in SFDC. The best field type to use is a Checkbox field, and you’ll need to set it up with the same name on both the Lead and Contact objects. Note: A Custom Sync Filter field can also be created on the Account before the initial sync, and it will be applied in the same way. 2. Update the records in Salesforce with the corresponding value you need to indicate whether the record should sync or not. Sync filters can be set up in two ways—a True/Checked value can indicate that a record is allowed to sync, or a True/Checked value could indicate that a record is not allowed to sync. This choice is up to you. 3. Begin your Salesforce Sync Setup but do not finish it. There are two sets of Salesforce Sync installations, one for Enterprise/Unlimited Edition and the other for Professional Edition. For both Enterprise/Unlimited and Professional Edition versions, three documents correspond to the three different steps: “Step 1 of 3”, “Step 2 of 3,” and “Step 3 of 3”. For both versions, complete all steps of “Step 1 of 3” and “Step 2 of 3”. When you get to “Step 3 of 3”, you will only do the first half of the steps and then stop. Complete the sections “Retrieve Sync User Security Token” and “Set Sync User Credentials,” and then stop there. Do not proceed to start the sync. 4. This is when the sync filter needs to be implemented. Contact Marketo Support and request a Custom Sync Filter be activated. Be sure to include the custom field name, which configuration you need (checked=sync vs checked=don’t sync), and note that all records have been populated with the correct values. Once it has been applied and the Marketo Support case is resolved, you’re done and can start your initial SDFC sync!

Issue Your Salesforce sync cycle is taking longer than usual. How long is too long? Solution By default, Marketo starts each Salesforce sync cycle five minutes after the previous cycle completes. Each sync cycle may take a couple of minutes or a couple of hours, depending on how much data needs to be written across. If you notice your sync cycles seem to be taking longer than usual, here are some things to check. Have you done a large update recently? This can create a backlog that can take time to work through. Have you added new fields to any of your synced Salesforce objects? The more fields on the object, the more data needs to be written across, extending the sync cycle. If you would like to streamline your Salesforce sync, do an audit in Salesforce of fields visible to the Marketo Sync User. If there are any fields that are not used in Marketo, remove visibility to them so Marketo does not waste time syncing them.

What is a Blocklist? Can I Still Send My Emails, or Are You Blocking Me from Sending? What Is a Spamtrap and Why Do They Matter? Can You Give Me the Spam Trap Address That Triggered the Blocklist So I Can Remove It from My Database? Can You Give Me More Information regarding the Blocklist Issue? What Is the Quarantined IP Range? I Sent This Email Campaign a While Ago. Why Am I Only Getting Notification of the Blocklist Issue Now, and Am I Still Blocklisted? The Blocklist Notification Went to the Wrong Email Address. Why Was It Sent to That Address? Which blocklists should I be concerned about? - Top Blocklists – What You Need to Know How do blocklist issues get resolved? What steps do I need to take to resolve the blacklist issue? - Blocklist Remediation

Issue Lead conversion/qualification through workflows in Microsoft Dynamics CRM resulting to duplicates (i.e. Lead and Contact) in Marketo Environment Microsoft Dynamics CRM Lead conversion Sync Solution While lead qualification through workflows is currently not supported, one approach that we saw implemented by a customer that did not result in duplicates is by redeveloping the lead qualification workflow using the msdyncrmWorkflowTools (1.0.54.0): QualifyLead step. Dynamics-365-Workflow-Tools/Qualify Lead.md at master · demianrasko/Dynamics-365-Workflow-Tools This was verified to result in no duplicates as the workflow writes the "Create [Qualify Lead]' operation type to the Marketo Log which is like the standard qualify button. Should there be any further assistance needed in developing the lead conversion workflow, it's recommended to engage with our Professional Services / Consulting team Root Cause Marketo's integration with Microsoft Dynamics CRM currently does not support custom qualify workflows.

Image: Step Flow for Predictive Content for Web and Email What is Auto Content Discovery? This post explains the first part of the flow image above: discovering, mapping, and tracking your content assets. Content Discovery is used in the Predictive Content app to auto-discover all the content assets (videos, pdfs, blog posts, press releases, white papers, etc.) on a website/domain. Once discovered, you can see how your content is performing and decide which pieces of content should be prepared, approved, and enabled for the Predictive Content outcomes on web (either in the recommendation bar or rich media) and email. Setting up Predictive Content and Content Discovery See Set Up Docs: http://docs.marketo.com/display/public/DOCS/Getting+Started+with+Predictive+Content Steps RTP Javascript tag is installed on all your web pages (Note: RTP is now called Web Personalization) Set Asset Discovery to On Asset Discovery auto-discovers extensions (PDFs, PPT, MP4, OFF, WEBM) and a click/view on embedded videos (Youtube, Vimeo, Wistia) Create URL Patterns Setting URL patterns auto-discovers content when a web visitor clicks on the HTML web page relevant to the content pattern. The URL syntax pattern determines your ability to use this feature optimally (e.g., to create a pattern for press releases, your press releases should all be stored on a page identified as www.yoursite.com/press-releases/*). How is content auto-discovered? The content discovery technology uses an event listener that runs on every web page (where the RTP Javascript tag is installed) and waits for a web visitor to click on a URL link or arrive directly on that web page in a browser. If that link includes an extension (PDF, ppt, embedded video) or matches the URL pattern defined, then it will be discovered and added to the All Content page in the Predictive Content app. Only content pieces that a web visitor interacted with (clicked on or viewed) once the RTP Javascript tag has been installed are discovered via Content Discovery. If the content is already discovered, it will add to the tracking and views of those discovered pieces. You can also manually add new content to be listed and tracked in the All Content page. Image: All Content Page in the Predictive Content app displaying and tracking all discovered content What data is discovered? Visitor Data (Used for Analytics + Predictive Algorithm) Pages Viewed - number of page views by the user in the session Visit Count for Web Visitor Last Content URL Seen Last 5 Content Assets clicked via Predictive Content that this visitor has seen in the last 90 days Last Web Campaigns Seen - 10 last campaigns per session (within the last 5 sessions) Inferred Organization Inferred, Industry, Size, Revenue Inferred Country, State, City Search Term Content Data Extensions Video (Youtube, Vimeo, Wistia) Video Name Video URL Video Image URL PDF PDF Name PDF URL URL Patterns (HTML pages) Found via metadata of the HTML page Content Name Content URL Content Image URL Content Description What data is auto-populated during the auto-discovery phase? Based on the content data we discover, the aim is to populate as much of the Predictive Content as possible, making it quicker, easier and involves less prep work for you. However, you still need to review the discovered content and then approve and enable it for the Predictive Source (Email, Rich Media, Recommendation Bar). Assuming we discover an HTML page defined in URL patterns, this HTML content piece will be populated in the following fields in Predictive Content: Predictive Content Fields Auto-Populated Value Notes Content Name (Content Name) Unique Value Content URL (Content URL) The URL is consistent for all sources (email, bar, rich media) Categories Video OR Category Name from URL Pattern If Video is discovered, the category is populated as Video. Category populated from defined URL Pattern. e.g., Marketo.com/blog = Blog all discovered content based on this URL would receive Blog as a category Category is consistent for all sources (email, bar, rich media) Content Title (Content Name) Email Title (Content Name) Email URL (Content URL) Email Image URL (Content Image URL) Email Button Label Read More Not Auto-populated. Default is "Read More." Rich Media Title (Content Name) Rich Media URL (Content URL) Rich Media Image URL (Content Image URL) Rich Media Description (Content Description) Bar Title (Content Name) Bar URL (Content URL) Image: Example of Populating Metadata for HTML content into Predictive Content

Summary You have set up a campaign or campaigns in the Email Deliverability Tool (250ok), but there is no engagement metric showing Total opens and Unique opens, which should be available in the ‘Engagement Overview’ in the Email Deliverability tool. You would need to ensure that you have configured the necessary setup for the tracking to work in the Email Deliverability tool. Issue Campaigns created in the Email Deliverability tool (250ok) doesn’t show any engagement overview metric such as total opens and unique opens. Environment Email Deliverability tool (Production/Sandbox) Solution You would need to implement the necessary setup for the metric to show in the Engagement Overview in the Email Deliverability tool (250ok) Follow the steps below to ensure you have configured the setup for campaign tracking. 1. Ensure your DNS CNAME is configured. (All that is required is creating a CNAME DNS entry on this domain that points to 250analytics.com) For more information, you can refer to this external documentation: https://www.validity.com/knowledge-base/what-are-custom-domains-in-250ok-analytics/ 2. Insert the correct tracking pixel code retrieved from the Email Deliverability tool. 3. Always utilizing the ‘c=‘ tag in your tracking code for your campaigns to ensure the tracking is measured correctly in the Email Deliverability tool. (Obviously, the CNAME above is essential to have it set up correctly). You can follow a guide on how to implement the ‘c=‘ tag and retrieve the tracking pixel is here: https://help.returnpath.com/hc/en-us/articles/360046308092-How-Do-I-Add-My-250ok-Tracking-Pixel- Once you have all these configuration settings, you can start tracking your campaigns which are sent via Marketo in the Email Deliverability > Engagement Overview. Root Cause Mis-configuration or no configuration made causing the campaign tracking does not work.

Issue Per our developer page: https://developers.marketo.com/rest-api/assets/programs/#update, it is possible to update tags on your existing program When updating a program tag within an existing program, you may encounter an error below given the tag and its values are correct. {"code": "709","message": "Required tags are mandatory"}]} Environment Any API clients when performing the Web Service API Solution The workaround is to have the tag updated via the UI. Root Cause "Updating tags is a destructive operation." Any attempt to update the tags of a program must include valid values for all of the required tags for a program. Unless the 'specific' tag type you are working on is the only required tag type in the instance, then that is possible to update it using the API. Otherwise, you'll encounter the error above as it is a system behaviour.

Issue Initial MS Dynamics sync gives the error 'is missing prvReadSdkMessageProcessingStep privilege' Environment MS Dynamics CRM integration Solution Issue Resolution These permissions, found within Security Role, require a Microsoft Dynamics Admin to set and change., Navigate to Settings > System > Security and select Security Roles icon. Click on the Marketo Sync User to bring up the individual access level for each individual entity. For the sync to work the individual privileges are as follows: Under 'Core Records': Under 'Customisation': Under 'Custom Entities': Any role with Marketo needs to have all permissions. More information on Managing Users and Security Roles can be found on the Microsoft Dynamics Site: https://docs.microsoft.com/en-us/dynamics365/customer-engagement/marketing/manage-users Root Cause The error indicates the Marketo Sync User in Dynamics lacks some of the required permissions for the sync.

Issue The Source Campaign field in Microsoft Dynamics is not getting updated when the field is updated in Marketo. The sync from Microsoft Dynamics to Marketo will be working fine. Environment Native integration with Microsoft Dynamics Campaign Sync not Enabled Solution To sync Campaign Source from Marketo to Dynamics, the option 'Campaign Sync' needs to be enabled as per this documentation: Enable Campaign Sync | Adobe Marketo Root Cause If the Campaign Sync is not enabled we will not be syncing over the value of the field to Microsoft Dynamics as it is part of the Campaign Sync.

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Top Blocklists - What You Need to Know

Marketo Field Limits by Field Type

SFDC Sync Error “LimitException: Apex CPU Time Limit Exceeded”

Get Activity Types via API returns a character wrapped in brackets for a Marketo Custom Object field named ID

Links in emails not opening correctly when it contains a token and special character #

Why is my Engagement Score not matching with the Engagement Score in Email Insights?

Soft Bounce Details: 435 5.7.8 Authentication credentials invalid.

Changing the expiration for a user to never

Failed: no more information

Marketo landing page format is different from preview

Restrict Marketo Logins Based on IP Error

How Do Marketo Redirect Rules Work?

Restrict records syncing to Marketo from Salesforce using Custom Sync Filter

Salesforce Sync Cycles Taking Longer than Usual

Blocklists: Frequently Asked Questions

Duplicate leads after lead conversion in Microsoft Dynamics CRM

How Auto Content Discovery Works in Predictive Content

Email Deliverability Tool - Campaigns Not Being Tracked

API Error 709 When Updating Tags of an Existing Marketo Program

MS Dynamics Initial Sync Gives Privilege Error

Source Campaign field is not updating in Dynamics from Marketo