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 Issue Description Windows Outlook users who use the Marketo Sales Connect plugin might have noticed that emails don't send as fast as they usually do. Unfortunately it takes a little longer than usual on this particular platform due to a recent MSC plugin update. We are working on a long-term fix for this subset of customers, but in the meantime you can use the following workarounds: Solution Issue Resolution If you switch Outlook to, "Online Mode" (as opposed to Cached Exchange Mode) this will decrease the total sending time. You can follow this document in order to turn off Cached Exchange Mode. If you would like to learn more about the differences between Online Mode and Cached Exchange Mode, you can read more here. Alternatively, you can also use the Web version or Mac version of Outlook to address this issue. Who This Solution Applies To Windows Outlook users who utilize the Marketo Sales Connect plugin.

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

If no data is being sent from RTP to Google Analytics, make sure that the segment in question is linked to GA Go to the Segments page Edit the segment in question Make sure Send segment to web analytics is checked on Without this field checked, no data will be sent from RTP to GA regarding that segment. To validate that RTP is sending data to your GA account, first log in to your GA account, and make sure the segment data is being populated in GA. Navigate to Reporting > Behavior > Events > Top Events > Segments (Event Category) > Event Actions If you find that some, but not all, of the data is being transferred from RTP to GA, visit this article to learn why there might be discrepancies.

概要弊社サンノゼデータセンターの一部のお客様環境におきまして、日本時間の2018年9月12日(水)よりメール送信が遅延または中断されるサービス障害が発生いたしました。サンノゼデータセンター以外のお客様環境には影響はありません。この障害は既に解消されており、現在ではメール送信は正常に機能しておりますこのメール送信遅延障害からの復旧作業中に送信されたメールの一部が消失し、配信されませんでした。この文書はサンノゼデータセンターのお客様にこの障害によって影響のあったキャンペーンを特定する方法を詳細にご案内するためのものです。お客様には多大なるご迷惑をおかけいたしましたことを深くお詫び申し上げます。私共は今回の障害が非常に重大な問題であると認識し、影響のあったキャンペーンの特定を支援させていただくと共に今後同様の問題の発生がないよう回避策を講じる所存です。影響このメール送信遅延障害の復旧作業の間にメール送信処理中に使用されるアクティブメッセージキューサービス (AMQ: Active Message Queue) の再初期化を行いました。このAMQのリスタート時にキューで待機していたメールが消失しました: トリガーキャンペーンによって送信され、AMQで待機していたメールは処理されないまま、消失しました。リスタート時もしくはその直前にバッチキャンペーンによって送信されたメールはリードのアクティビティとして「メールの送信」は記録されますが、「配信済みメール」が記録されない場合があります。現象は以下の2つのパターンとなります: 一部のバッチキャンペーンはすべての対象リードのメールが送信済みとなりますが、配信済みが0となります。この場合、メールは一切配信されません。それ以外のバッチキャンペーンではメールは送信済みで、かつ配信済みとなっているものとそうでない(配信済みが記録されない)ものが混在している状態となります。このように少しでも配信済みが記録されている場合はそのキャンペーンのメールはすべて正常に配信されています。障害発生日時メール送信の遅延が日本時間の2018年9月12日(水)の早朝(深夜帯)から発生し始めました。 AMQの再初期化によってメールが消失し、配信されなかった時間帯は以下の通りです: 2018年9月12日(水) 4:30AM - 5:00AM JST 2018年9月13日(木) 1:15AM - 1:50 AM JST 問題は2018年9月13日(木) 2:30AM JST 頃に解消しました。影響のあったキャンペーンの特定方法スマートリストスマートリストを使用して、メールが消失したかどうかを確認する方法が2種類あります。一つはトリガーキャンペーンを、もう一つはバッチキャンペーンを特定します。トリガーキャンペーンを特定 AMQが再初期化された際にトリガーキャンペーンによって送信され、AMQで待機していたメールは処理されないまま、消失しました。以下のスマートリストはトリガーキャンペーンによって送信されたけれども、配信されずに消失したメールの対象リードのリストを返します。スマートリストフィルタールール論理式: 全フィルターを使用フィルター #1: スマートキャンペーンのメンバーリード: [指定のリストに存在する] "<トリガーキャンペーン名>" フィルター #2: メールを送信済みメール: [指定の値と等しい] "<トリガーキャンペーンのメール名>" アクティビティ日: [指定の値と等しい] 2018/09/12 フィルター #3: メール未配信メール: [指定の値と等しい] "<トリガーキャンペーンのメール名>" アクティビティ日: [指定の値と等しい] 2018/09/12 フィルター #4: ソフトバウンスメールではないメール: [指定の値と等しい] "<トリガーキャンペーンのメール名>" アクティビティ日: [指定の値と等しい] 2018/09/12 フィルター #5: バウンスメールではないメール: [指定の値と等しい] "<トリガーキャンペーンのメール名>" アクティビティ日: [指定の値と等しい] 2018/09/12 完成しますと、以下のようなスマートリストとなります (英語版UI) : バッチキャンペーンを特定 AMQのリスタート時もしくはその直前にバッチキャンペーンによって送信されたメールはリードのアクティビティとして「メールの送信」は記録されますが、「配信済みメール」は記録されない場合があります。現象は以下の2つのパターンとなります: 一部のバッチキャンペーンはすべての対象リードのメールが送信済みとなりますが、配信済みが0となります。この場合、メールは一切配信されません。それ以外のバッチキャンペーンではメールは送信済みで、かつ配信済みとなっているものとそうでない(配信済みが記録されない)ものが混在している状態となります。このように少しでも配信済みが記録されている場合はそのキャンペーンのメールはすべて正常に配信されています。以下のスマートリストにて特定のバッチキャンペーンに対して本障害の影響があったかどうかを確認できます: スマートリストフィルタールール論理式: 詳細フィルターを使用 [1 and 2 and (3 or 4 or 5)] フィルター #1: スマートキャンペーンのメンバーリード: [指定のリストに存在する] "<バッチキャンペーン名>" フィルター #2: メールを送信済みメール: [指定の値と等しい] "<バッチキャンペーンのメール名>" アクティビティ日: [指定の値と等しい] 2018/09/12 フィルター #3: メール配信済みメール: [指定の値と等しい] "<バッチキャンペーンのメール名>" アクティビティ日: [指定の値と等しい] 2018/09/12 フィルター #4: ソフトバウンスメールメール: [指定の値と等しい] "<トリガーキャンペーンのメール名>" アクティビティ日: [指定の値と等しい] 2018/09/12 フィルター #5: バウンスメールメール: [指定の値と等しい] "<トリガーキャンペーンのメール名>" アクティビティ日: [指定の値と等しい] 2018/09/12 完成しますと、以下のようなスマートリストとなります (英語版UI) : キャンペーンのメール送信結果の確認スマートキャンペーンのサマリーページにそのキャンペーンによって送付されたメールの結果が確認できる「メール」タブがあります。影響のあったキャンペーンを特定するには、障害が発生した日付で配信済み、ハード・ソフトバウンスが0、送信済みと保留中の数が等しいかどうかをご確認ください。以下は一例です: もし、すべての送信メールが保留中の状態である場合、本障害に当たっていると判断できます。現時点でもこの状態の場合はこれらの保留中のメールが配信されることはありません。メールの効果レポートメールの効果レポートで送信したメールにどのような効果があったか確認できます。キャンペーンに影響があったかどうかを確認するには特定の日付、特定のメールのメールの効果レポートをご確認ください。スマートキャンペーンサマリーのメールタブの時と同様に、障害が発生した日付で送信済みと保留中のメールの数が同じ場合、本障害に当たっていると判断できます。支援が必要な場合もしこの障害の影響があったかどうかを確認するために弊社からの更なる支援が必要な場合はMarketoカスタマサポートsupport.marketo.com までご連絡ください。

Issue Why don't some emails appear as an 'Email Filter' option in an Email/Email Link Performance Report? Filter Assets in an Email Report documentation Solution The reason why some emails do not appear as an 'Email Filter' option in an Email/Email Link Performance report is because the emails were used in an A/B test. Similar to the product behaviour illustrated below, when adding an A/B test, the selected email will not be directly selectable or appear as an Email Filter option in an Email/Email Link Performance report. "When adding an A/B test, the selected email will no longer be available for use in any other program." Add An A/B Test In order to report on the A/B test emails that do not appear in the Email Filter option, the parent program can be selected.

Note: Please ensure that you have access to an experienced Web developer. Marketo Technical Support is not set up to assist with troubleshooting code. The listOperation SOAP API call allows for the ability to interact with static lists (My Lists) in the Lead Database. The supported operations are adding a lead to list (ADDTOLIST), checking if a lead is a member of the list (ISMEMBEROFLIST), and removing a lead from a list (REMOVEFROMLIST) Note, there is no operation to create a new list (or delete) via the SOAP API. The list must be created beforehand in the Lead Database. In the examples, the list is named "Static List". Example 1 - Request: Adding multiple leads into the list <soapenv:Envelope xmlns:soapenv = "http://schemas.xmlsoap.org/soap/envelope/" xmlns:mkt = "marketo.com/mktows/"> <soapenv:Header> <mkt:AuthenticationHeader> <mktowsUserId>[User Id]</mktowsUserId> <requestSignature>[Signature]</requestSignature> <requestTimestamp>[yyyy-mm-ddThh:mm:ss-00:00]</requestTimestamp> </mkt:AuthenticationHeader> </soapenv:Header> <soapenv:Body> <mkt:paramsListOperation> <listOperation>ADDTOLIST</listOperation> <listKey> <keyType>MKTOLISTNAME</keyType> <keyValue>Static List</keyValue> </listKey> <listMemberList> <leadKey> <keyType>IDNUM</keyType> <keyValue>213</keyValue> </leadKey> <leadKey> <keyType>IDNUM</keyType> <keyValue>215</keyValue> </leadKey> </listMemberList> </mkt:paramsListOperation> </soapenv:Body> </soapenv:Envelope> Example 1 - Response: <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns1="marketo.com/mktows/"> <SOAP-ENV:Body> <ns1:successListOperation> <result> <success>true</success> <statusList xsi:nil="true"/> </result> </ns1:successListOperation> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Example 2 - Request: Check to see if leads are a part of list. One lead (Lead ID #213) is and the other (Lead ID #70) is not <soapenv:Envelope xmlns:soapenv = "http://schemas.xmlsoap.org/soap/envelope/" xmlns:mkt = "marketo.com/mktows/"> <soapenv:Header> <mkt:AuthenticationHeader> <mktowsUserId>[User Id]</mktowsUserId> <requestSignature>[Signature]</requestSignature> <requestTimestamp>[yyyy-mm-ddThh:mm:ss-00:00]</requestTimestamp> </mkt:AuthenticationHeader> </soapenv:Header> <soapenv:Body> <mkt:paramsListOperation> <listOperation>ISMEMBEROFLIST</listOperation> <listKey> <keyType>MKTOLISTNAME</keyType> <keyValue>Static List</keyValue> </listKey> <listMemberList> <leadKey> <keyType>IDNUM</keyType> <keyValue>213</keyValue> </leadKey> <leadKey> <keyType>IDNUM</keyType> <keyValue>70</keyValue> </leadKey> </listMemberList> </mkt:paramsListOperation> </soapenv:Body> </soapenv:Envelope> Example 2 - Response: <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="marketo.com/mktows/"> <SOAP-ENV:Body> <ns1:successListOperation> <result> <success>false</success> <statusList> <leadStatus> <leadKey> <keyType>IDNUM</keyType> <keyValue>213</keyValue> </leadKey> <status>true</status> </leadStatus> <leadStatus> <leadKey> <keyType>IDNUM</keyType> <keyValue>70</keyValue> </leadKey> <status>false</status> </leadStatus> </statusList> </result> </ns1:successListOperation> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Example 3 - Request: Similar to Example 2, but all leads are valid <soapenv:Envelope xmlns:soapenv = "http://schemas.xmlsoap.org/soap/envelope/" xmlns:mkt = "marketo.com/mktows/"> <soapenv:Header> <mkt:AuthenticationHeader> <mktowsUserId>[User Id]</mktowsUserId> <requestSignature>[Signature]</requestSignature> <requestTimestamp>[yyyy-mm-ddThh:mm:ss-00:00]</requestTimestamp> </mkt:AuthenticationHeader> </soapenv:Header> <soapenv:Body> <mkt:paramsListOperation> <listOperation>ISMEMBEROFLIST</listOperation> <listKey> <keyType>MKTOLISTNAME</keyType> <keyValue>Static List</keyValue> </listKey> <listMemberList> <leadKey> <keyType>IDNUM</keyType> <keyValue>213</keyValue> </leadKey> <leadKey> <keyType>IDNUM</keyType> <keyValue>215</keyValue> </leadKey> </listMemberList> </mkt:paramsListOperation> </soapenv:Body> </soapenv:Envelope> Example 3 - Response: <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns1="marketo.com/mktows/"> <SOAP-ENV:Body> <ns1:successListOperation> <result> <success>true</success> <statusList xsi:nil="true"/> </result> </ns1:successListOperation> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Example 4 - Request: Remove leads from the list. One lead (Lead ID #213) is a member of the list, the other (Lead ID #70) is not <soapenv:Envelope xmlns:soapenv = "http://schemas.xmlsoap.org/soap/envelope/" xmlns:mkt = "marketo.com/mktows/"> <soapenv:Header> <mkt:AuthenticationHeader> <mktowsUserId>[User Id]</mktowsUserId> <requestSignature>[Signature]</requestSignature> <requestTimestamp>[yyyy-mm-ddThh:mm:ss-00:00]</requestTimestamp> </mkt:AuthenticationHeader> </soapenv:Header> <soapenv:Body> <mkt:paramsListOperation> <listOperation>REMOVEFROMLIST</listOperation> <listKey> <keyType>MKTOLISTNAME</keyType> <keyValue>Static List</keyValue> </listKey> <listMemberList> <leadKey> <keyType>IDNUM</keyType> <keyValue>213</keyValue> </leadKey> <leadKey> <keyType>IDNUM</keyType> <keyValue>70</keyValue> </leadKey> </listMemberList> </mkt:paramsListOperation> </soapenv:Body> </soapenv:Envelope> Request 4 - Response: <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="marketo.com/mktows/"> <SOAP-ENV:Body> <ns1:successListOperation> <result> <success>false</success> <statusList> <leadStatus> <leadKey> <keyType>IDNUM</keyType> <keyValue>213</keyValue> </leadKey> <status>true</status> </leadStatus> <leadStatus> <leadKey> <keyType>IDNUM</keyType> <keyValue>70</keyValue> </leadKey> <status>false</status> </leadStatus> </statusList> </result> </ns1:successListOperation> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Example 5 - Request: Similar to Example 4, but all leads are valid <soapenv:Envelope xmlns:soapenv = "http://schemas.xmlsoap.org/soap/envelope/" xmlns:mkt = "marketo.com/mktows/"> <soapenv:Header> <mkt:AuthenticationHeader> <mktowsUserId>[User Id]</mktowsUserId> <requestSignature>[Signature]</requestSignature> <requestTimestamp>[yyyy-mm-ddThh:mm:ss-00:00]</requestTimestamp> </mkt:AuthenticationHeader> </soapenv:Header> <soapenv:Body> <mkt:paramsListOperation> <listOperation>REMOVEFROMLIST</listOperation> <listKey> <keyType>MKTOLISTNAME</keyType> <keyValue>Static List</keyValue> </listKey> <listMemberList> <leadKey> <keyType>IDNUM</keyType> <keyValue>213</keyValue> </leadKey> <leadKey> <keyType>IDNUM</keyType> <keyValue>215</keyValue> </leadKey> </listMemberList> </mkt:paramsListOperation> </soapenv:Body> </soapenv:Envelope> Example 5 - Response: <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns1="marketo.com/mktows/"> <SOAP-ENV:Body> <ns1:successListOperation> <result> <success>true</success> <statusList xsi:nil="true"/> </result> </ns1:successListOperation> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Related Learning Resources Marketo SOAP API Reference

No, unfortunately we are unable to tell you what the spam trap address is. We don’t even know it ourselves! Spam trap addresses are proprietary to the blacklists that own them. Anti-spam professionals use spam trap addresses to track unsolicited emails. If a spam trap is known by the offending sender, the sender could simply remove the spam trap address from their lists and never actually address the data problem that caused that spam trap address to be included in their lists to begin with. Instead of asking what the spam trap address is, try to identify the source of the trap address and eliminate bad data sources from your mailing lists. You should be able to identify the email campaign that caused the blacklist issue, so you should start with those lists. To narrow it down and identify the problematic data source, you should consider the following: Have you recently added any new leads or new lead sources? What is the source of these leads? Any purchased or appended email addresses should be removed, because these data sources are often the source of newly introduced spamtraps. In addition, using purchased or appended email addresses for mailing is a violation of Marketo’s Email Use and Anti-Spam Policy. Have you added any older leads that have not been mailed to recently? Some email providers will turn an email address into a spam trap after a year of inactivity. If you have a list of addresses that has not been mailed to in a year or more, this list should be removed. Does your system use any custom fields to indicate customer status, event attendance, recent contact with your sales team, or other forms of engagement? If so, take advantage of this and isolate the inactive or non-responsive segments of your database using all of the activity data you have available. Is there anything about this specific mailing that makes it different compared to your previous email campaigns? Did you send any other mail on the same day? If so, you should compare the recipient lists. Think you have narrowed in on the problem? Check out our guide to blacklist remediation to find out what to do with that bad list and complete the remediation program. Additional Resources: What is a spamtrap, or spam trap, and why does it matter? What is a blacklist? How does Marketo respond to blacklisting and spam notifications? Top blacklists - What you need to know Blacklist Remediation Successful Reconfirmation Blacklist Deep Dive Blacklist FAQ

Issue You are moving from the on-premise Dynamics solution to the online Dynamics and want to know what changes will be needed in Marketo to accommodate this. Solution Due to architectural differences between on-premise and online, a new instance will need to be provisioned so that the online version can be properly integrated. This is true even when the GUIDs remain the same between the two versions of Dynamics. Who This Solution Applies To Dynamics Users, Microsoft Dynamics CRM

Issue Issue Description Possible disadvantages of maintaining Engagement/Nurture Program emails in Design Studio. Solution Issue Resolution Housing all of your emails for email nurture content in Design Studio could cause the following issues: 1. Reporting: Reports can specify Emails in Design Studio, however they will show results for any send of the individual email and will not be constricted to the program they were sent from. 2. Asset re-use in Engagement Programs: When using an engagement program, an asset is scanned for its ID. If that asset has been previously sent to a record via any other send, the engagement program will skip that send for that record. This could become a problem when reusing email assets housed in design studio in different engagement programs. 3. My Tokens: my.tokens will not properly render as they are based on a program folder. The assets that reference them need to be in the folder as well. In my testing, assets in design studio do not have a frame of reference for mytokens. Emails will not populate mytokens if they are housed outside of the program that owns the tokens. With all of this noted, our recommendation is to utilize detailed templates in design studio and continue to clone your engagement programs and alter them as necessary. Although this presents some busy work in the short term, it pays off dividends in the long term when it comes to reporting, the use of my.tokens, and guaranteeing that records are sent the assets you are specifying in your programs.

At Marketo we take security seriously. As a part of an industry-wide initiative, Marketo is upgrading our web authentication and encryption to enhance our security protections. The rollout is scheduled to occur on December 12, 2015. Who will be affected? Only a small number of users will be affected, only those who have an integration to Marketo from a system that is over ten years old and hasn't been updated recently. See this list for more info on what systems and versions are supported. The following users will not be impacted: End users accessing Marketo.com through modern browsers (see list) Customers using integration partners such as Informatica, Dell Boomi, and Scribe. Customers using Launchpoint partners. Rollout schedule The following rollout schedule is planned: Service URL SHA-2 Rollout Date API access mktoapi.com Dec 12, 2015 API access mktoresp.com Dec 12, 2015 Part of MLM Application marketodesigner.com Dec 12, 2015 All other Marketo domains already use SHA2 certificates.

Issue Description After syncing a Dynamics Custom Entity to create it in Marketo, not all constraints appear as options when setting up filters for the custom entity in a Smart list. Issue Resolution When a custom entity is added after the initial sync, it may not end up with a direct relationship in the database. To resolve this, fully refresh everything to see if that helps re-establish the relationship using the following steps: Remove all the references from this entity (which you can see under Object Properties: Object Used By") Disable the custom entity Refresh schema and re-sync the custom entity Who This Solution Applies To Customers using MS Dynamics Custom Entities Is this article helpful ? YesNo

Summary Smart campaign utilizing the 'Fills Out Facebook Lead Ads Form' trigger does not generate any results for people created as a result of filling out a Facebook Lead Ads form. Issue Smart campaigns utilizing the 'Fills Out Facebook Lead Ads Form' Trigger does not trigger for people created as a result of filling out a Facebook Lead Ads form. Solution If you have Workspaces and Partitions set up on your instance, it is important to remember that people created in the database as a result of filling out Facebook Lead Ads form, will be automatically created in your Default partition per design. In a scenario where a trigger campaign is hosted under a workspace that does not have the appropriate visibility to your default partition - the person filling out the Facebook Lead Ad form would not be triggering the campaign. Solution Make sure your trigger campaign lives under workspace which has visibility over the default person partition. To check the workspace configuration go to Admin > Workspaces & Partitions and make sure your default partition is assigned to the workspace where your trigger campaign lives under. Root Cause New people which are being created in Marketo as a result of filling out a Facebook Lead Ads Form will be created by default in the Default lead partition. Environment Customers who have Workspaces and Partitions set up in their instance. Customers who have set up the Facebook Lead Ads integration and have utilized the 'Fills Out Facebook Lead Ads Form' Trigger

Issue: After changing your email template, your associated emails are now blank or the main template is showing. Why does this happen? This happens because the editor cannot associate the unique "mktedtable" divs from the template to the email. When creating a template, each section that can be changed will have a class of "mktEditable" and a unique "ID". <div class=”mktEditable” id=”1body”> your editable content</div> Solution: To fix your current emails, preview the current approved email and verify there is infact content. 1.discard draft 2.edit draft, it will still look blank until step 3 is complete 3.replace html with no changes, the html content should show again. 4.approve the email Don't change anything and click OK. Your orginal email content will be restored. Caution: This only works if you did not approve the email when it was blank. Note about the blank "template": When using the blank template in general, it means you intend to address your email at the main email level. Adding style to the blank template invalidates it as a blank template. The best practice would be to create a new template and add your custom code.

Issue Issue Description Even though the Success Path Analyzer and the RCE report may be looking at the same thing (e.g the conversions from one stage to another), the numbers in Success Path Analyzer and RCE Conversion Ratio will not match. Solution Issue Resolution Success Path Analyzer is telling you that records are flowing from one stage to another, for example a record moving from Cold List to MQL, the conversion rate will display the rate from this stage to the next stage. If you look at the RCE Conversion Ratio, this is not tracking just the conversion from the first stage on the Success Path Analyzer to the second but instead this tracks all the conversions from this stage to another (eg. Cold List to MQL, Cold List to Attempting). Thus resulting in a much higher conversion percentage as the RCE is not bound to the green path from the Success Path Analyzer. Who This Solution Applies To Customers using RCE, Customers using Success Path Analyzer

Issue Description You want to know if it's possible to have the same file in both the Default workspace and another workspace. Issue Resolution You cannot have the same file name in different worksapces. For example, if you have a folder in your Default workspace named "Test" and then you try to create another folder called "test" in different workspace, this will not work. The same thing will happen if you try to clone a program to a different workspace and you use the exact same file name. When you are creating new folders or cloning programs, you must use a unique name.

The Marketo system hosting your subscription is currently experiencing an unplanned service interruption affecting Trigger processing. When: Monday April 24 th, 2017 - Current Services affected: During the time of this incident, Trigger Processing is intermittently affected. Customers may experience periodic delays in Triggering events based on an activity. Login to the Marketo application, landing pages, and rest of the platform are not affected. Cause: This service interruption is due to stability issues in our infrastructure, which is utilized for Triggering events. We are actively engaged with our Vendor to stabilize the infrastructure and deliver a permanent resolution. We will provide the next update within 24 hours. A root Cause and/or remediation plan will be shared as soon as we have it from our Vendor. We want to assure you that we take these incidents very seriously, and we are taking steps to prevent similar situations going forward. If you have any questions about service interruption, please contact Marketo Support. Is this article helpful ? YesNo

Issue Issue Description You have a record with a "Change Data Value" activity, but that field doesn't have a value on the current record. There's also an anonymous lead merge (which can be identified by looking for a Merge Leads activity and seeing if "Anonymous Source" is True) on the record. Solution Issue Resolution Check the Change Data Value's "LeadId" field. If this matches the anonymous record's ID (identified from the Merge Leads activity in the "Merge Id" field), then the reason for the value not showing is because upon association of an anonymous lead to a known record, only the activities are merged -- not the values of any fields which may have been recorded as changed.

No, if you have received the blacklist notification, you are not blocked from sending mail. You can continue to mail while you work through the remediation steps. The only time we will ever block you from sending mail is if you trigger a listing at Spamhaus, the world’s most respected and widely used blacklist. If this happens, you will receive a call or email to let you know what’s going on and we will work with you to resolve the issue. This is a rare occurrence. Additional Resources: Can you give me the spam trap address that triggered the listing? What is a spamtrap, or spam trap, and why does it matter? What is a blacklist? How does Marketo respond to blacklisting and spam notifications? Top blacklists - What you need to know Blacklist Remediation Successful Reconfirmation

When Marketing Suspended is checked in a lead's record, it will prevent any email from being sent by Marketo including the emails sent from Marketo Sales Insight. Outlook emails however, are not sent via Marketo. They are sent by the mailserver to which the client is connected; ie Goolge mail servers or Microsoft Exchange Servers, and are not under Marketo's control. The Marketing Suspended check box is located on the Lead Info tab. Is this article helpful ? YesNo

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Top Blocklists - What You Need to Know

Outlook Marketo Sales Connect Users Experiencing Slow Email Sends on Windows

Error Approving Email - Token Key not found

Troubleshooting Web Personalization (RTP) - Segment Matches not Sent to Google Analytics

サンノゼデータセンターメールサービス遅延障害

Reporting on A/B Tests Emails in Email Reports

Example SOAP API Call - listOperation

Can You Give Me the Spam Trap Address That Triggered the Blacklist So I Can Remove It from My Database?

Moving from Dynamics On-Premise to Dynamics Online

Housing Email Nurture Content in Design Studio

Marketo Security Enhancements

Dynamics Custom Entities - Constraints do not appear for Smart Lists

Fills Out Facebook Lead Ads Form trigger campaign does not qualify people

Email is Blank after changing the email template

Delete Interesting Moment

Success Path Analyzer Conv % vs RCE Conversion Ratio (all types)

Same File Name in Different Workspaces

Marketo Service Interruption Update

Merged Lead Has "Change Data Value" Activity But No Value in Field

Can I Still Send My Emails, or Are You Blocking Me from Sending?

Will Marketo Sales Insight emails be sent if Marketing Suspended is set to True?