Knowledgebase

Sort by:
  When a customer triggers a blocklisting on Marketo's shared IP range that customer is moved to a set of IPs we call the quarantined IP range.  We do this to protect the health of our shared network and ensure the best deliverability possible for all of our customers on that network.   If you have received a Blocklist Notification from Marketo reporting that you have triggered a blocklisting your Marketo account is now in the quarantined IP range.   While you are in the quarantined range it is possible that you may experience a slight decrease in your deliverability rates. The reason for this is that you are now sending from a range made up of senders that have also caused other blocklist issues. All customers have received a notice of the listing and are in the process of repairing their database.   There are two ways to be removed from the quarantined IP range: Follow the steps outlined in our Blocklist Remediation article.  Be sure to fill out the form referenced in the email alert to indicate that you have taken steps to mitigate the issue. Demonstrate clean sending behavior for 3 months. We remove senders from the quarantined IP range if they have not triggered any new listings in 3 months.   To ensure your best deliverability rates blocklist issues should be addressed right away to prevent further damage to your sending reputation.   Furthermore, if no action is taken to improve list hygiene the issue will likely recur. Marketo's Delivery and Compliance Team strongly recommend following the Blocklist Remediation steps.   Additional Resources: Blocklist Deep Dive    
View full article
  There are thousands of blocklists out there and all of them operate a little differently and all have varying levels of reputation.  There are only a dozen blocklists that really can impact delivery.   The blocklist that requires the most work from you when you request delisting is Spamhaus. Spamhaus is a trustworthy blocklist and if you are listed at Spamhaus you have made a mistake that will need to be directly addressed before the listing can be removed.   SpamCop is considered a tier I blocklist for B2B marketers but a tier II for B2C marketers.  Marketo responds to all SpamCop listings; researching to identify the source so we can work with the customer to educate on best practices and prevent future listings.    Some blocklists require that you pay a fee to be delisted. These blocklists are not favored in the email community because they use this tactic. For the most part, Marketo advises our customers not to mind alerts of being listed on a pay-to-delist blocklist.  These blocklists tend to have minimal impact to your deliverability.   For the most part blocklists are dynamic and resolve themselves in around 24 hours if the issue resolves. If the problematic sending continues, the blocklist will continue to keep you listed until the offending sending pattern stops.    If you are blocklisted, your main concern at that point should be making sure it doesn't happen again. For steps on how to identify the problematic data source and improve your list hygiene in an effort to avoid blocklist issues, see our article on blocklists that matter.The article highlight those that have the potential to be the most impactful, as well as those to be largely ignored . Because blocklists are dynamic and constantly evolving, their relevancy is also subject to change within the Marketo sender ecosystem. Some had notable impact at one time but no longer are.  Therefore always make sure to check if the current blocklist(s) of concern is a reputable and relevant to the sender region and ecosystem, and become familiar with those that matter the most.  
View full article
*Updated in September 2024     Leads can be auto unsubscribed due to default Feedback Loop setup with the ISPs listed on this page. You can use the following filters to find leads that have clicked the SPAM button in your emails:       Filter 1: Data Value Changed Attribute: Unsubscribe New Value: True Reason: Contains, complaint   (Optional to Specify what Email Domain)   Filter 2: Email Address Email Address: Contains, @domain.
View full article
Issue Email bounces with Error: 550 Rejected by header based Anti-Spoofing policy Solution This error can happen if: DKIM/SPF configuration is incomplete for the from domain in the sending email address. https://experienceleague.adobe.com/docs/marketo/using/getting-started-with-marketo/setup/configure-protocols-for-marketo.html?lang=en
View full article
If you have submitted a support case and you feel that the case was improperly handled or that the solution being offered does not meet the communicated Marketo support expectations, then we would welcome the opportunity to look deeper at your specific support engagement and work with you on delivering a better resolution. Caution: If the item you're looking to escalate is related to a Production Down incident, please call the support line for your region to receive immediate assistance. Support Manager escalations are only handled during normal business hours. The phone numbers for each region are listed below, follow the prompts for P1: Americas: +1.877.270.6586, Direct: +1.650.376.2303 Europe, Middle East, & Africa: +353 (0)1 242 3030,  UK: 0800 151 3030 Asia Pacific: +61 2 8031 8188 Japan: +81.03.4233.9014 How to Escalate: Step 1. Navigate to the "Case Management" area of the support portal either by mousing over the Support tab and selecting "Case Management" or clicking the Support tab and click on the “My Case Management” button. NOTE: You will need an open or recently closed case in order to escalate to support leadership. This is a article attached image   Step 2. From here you will need to click on either an open or a recently closed* case:   This is a article attached image   *Support Cases that have been closed for longer than 10 days are no longer eligible to be re-opened and we ask that you open a new support ticket for your current issue prior to escalating to a Support Manager. We ask that you have an open support ticket for a Support Manager to be able to address specific issues. Step 3. After selecting a case, click on the Escalate to Manager button:   This is a article attached image     Step 4. A pop up will display and you will need to the purpose for the escalation and click on the “Escalate” button.   This is a article attached image   Once your support escalation case has been submitted a Marketo Support Leader will contact you within 1 business day of your support region's support hours to address the issue.
View full article
Issue Emails with valid email address get soft bounced with this error:  Local address contains control or whitespace. Solution This error means that the email has a space somewhere in the the From email address or there was a comma or extra character in the From line.  If you do not see a space inside the email address, check the end of the address to see if a space somehow got added at the end. The email send did not occur due to the error with the address. The emails will need to be resent once after the associated address is corrected with white spaces or extra characters. Also, there is the possibility that email address "text" contains Paragraph marks or hidden formatting symbols (https://www.computerhope.com/jargon/f/formmark.htm) and instance users will required to have it reviewed and changed.        
View full article
An email being filtered to a quarantine or bulk mail folder happens after the recipient mail server has accepted message.  Once an email has been accepted by a mail server, it is impossible to tell where it went or what happened to it.  Note that this is true of any mail sent by any system on the Internet.   Every mail server has configurable filters that determine how received mail will be handled.  The mail server administrator should be able to adjust those filters to ensure delivery of emails based on their business standards, or there may even be end-user-configurable controls that can accomplish the same thing.   If test mailings you are sending to yourself or your colleagues are being filtered to a quarantine or bulk mail folder, you should consider asking your email administrator to whitelist Marketo’s IP ranges.  They can be found here.   You can also improve your deliverability in general by setting up SPF and DKIM records, and branding your tracking links.
View full article
Issue Clearing cache and cookies in your browser will fix a number of different problems related to page display, browser errors, and login issues.     Solution Here are links to the support articles on how to clear cache and cookies for the most commonly used browsers. Chrome Clear cache and cookies - Computer - Google Account Help   FireFox How to clear the Firefox cache | Firefox Help   Internet Explorer https://support.microsoft.com/en-us/help/278835/how-to-delete-cookie-files-in-internet-explorer   Microsoft Edge Microsoft Edge, browsing data, and privacy – Microsoft privacy    
View full article
  Syntax Recommendations Common Look Up mechanisms Common Modifiers Too Many Mechanisms Character String Too Long Null Records in the SPF Record Repetitive Records in the SPF Record - Void Lookups Validation Tools Syntax Recommendations Common Look Up mechanisms a: mx: include: ip4: ip6: exists: ptr: all Common Modifiers redirect= exp=   An A Record must ALWAYS contain IP address (map host to IP) CNAME (Alias) must contain hostnames. No IPs here NS an MX records must contain host names. No IPs allowed. MX records (for mail servers)  should contain hostnames NOT IPs. Too Many Mechanisms Section 10.1, "Processing Limits" of the SPF RFC 4408 specifies the following in regards to DNS lookups: SPF implementations MUST limit the number of mechanisms and modifiers that do DNS lookups to at most 10 per SPF check, including any lookups caused by the use of the "include" mechanism or the "redirect" modifier.  If this number is exceeded during a check, a PermError MUST be returned.  The "include", "a", "mx", "ptr", and "exists" mechanisms as well as the "redirect" modifier do count against this limit.  The "all", "ip4", and "ip6" mechanisms do not require DNS lookups and therefore do not count against this limit. The "exp" modifier does not count against this limit because the DNS lookup to fetch the explanation string occurs after the SPF record has been evaluated. This limit is in place to prevent SPF lookups from being a useful avenue for Denial of Service attacks. Using an example SPF record as an example to illustrate, this record was breaking with 12 look-ups: example.com text = "v=spf1 include:_spf-a.example.com include:_spf-b.example.com include:_spf-c.example.com include:_spf-ssg-a.example.com include:spf-a.anotherexample.com ip4:131.107.115.215 ip4:131.107.115.214 ip4:205.248.106.64 ip4:205.248.106.30 ip4:205.248.106.32 ~all" [ 5 mechanisms] _spf-a.example.com  text = "v=spf1 ip4:216.99.5.67 ip4:216.99.5.68 ip4:202.177.148.100 ip4:203.122.32.250 ip4:202.177.148.110 ip4:213.199.128.139 ip4:213.199.128.145 ip4:207.46.50.72 ip4:207.46.50.82 a:mh.example.m0.net ~all"  [ +1 = 6 mechanisms] mh.example.m0.net a = 209.11.164.116 _spf-b.example.com text = "v=spf1 include:spf.messaging.example.com ip4:207.46.22.35 ip4:207.46.22.98 ip4:207.46.22.101 ip4:131.107.1.27 ip4:131.107.1.17 ip4:131.107.65.22 ip4:131.107.65.131 ip4:131.107.1.101 ip4:131.107.1.102 ip4:217.77.141.52 ip4:217.77.141.59 ~all" [+1 = 7 mechanisms] spf.messaging.example.com text = "v=spf1 include:spfa.anotherexample.com include:spfb.anotherexaple.com include:spfc.anotherexample.com -all"  [+3 = 10 mechanisms] spfa.anotherexample.com  text = "v=spf1 ip4:157.55.116.128/26 ip4:157.55.133.0/24 ip4:157.55.158.0/23 ip4:157.55.234.0/24 ip4:157.56.112.0/24 ip4:157.56.116.0/25 ip4:157.56.120.0/25 ip4:207.46.100.0/24 ip4:207.46.108.0/25 ip4:207.46.163.0/24 ip4:134.170.140.0/24 ip4:157.56.110.0/23 -all" [+0 = 10 mechanisms] spfb.anotherexample.com  text = "v=spf1 ip4:207.46.51.64/26 ip4:213.199.154.0/24 ip4:213.199.180.128/26 ip4:216.32.180.0/23 ip4:64.4.22.64/26 ip4:65.55.83.128/27 ip4:65.55.169.0/24 ip4:65.55.88.0/24 ip4:94.245.120.64/26 ip4:131.107.0.0/16 ip4:157.56.73.0/24 ip4:134.170.132.0/24 -all" [+0 = 10 mechanisms] spfc.anotherexample.com  text = "v=spf1 ip4:207.46.101.128/26 ip6:2a01:111:f400:7c00::/54 ip6:2a01:111:f400:fc00::/54 ip4:157.56.87.192/26 ip4:157.55.40.32/27 ip4:157.56.123.0/27 ip4:157.56.91.0/27 ip4:157.55.206.0/24 ip4:157.55.207.0/24 ip4:157.56.206.0/23 ip4:157.56.208.0/22 -all" [ +0 = 10 mechanisms] _spf-c.example.com  text = "v=spf1 ip4:203.32.4.25 ip4:213.199.138.181 ip4:213.199.138.191 ip4:207.46.52.71 ip4:207.46.52.79 ip4:131.107.1.18 ip4:131.107.1.19 ip4:131.107.1.20 ip4:131.107.1.48 ip4:131.107.1.56 ip4:86.61.88.25 ip4:131.107.1.44 ip4:131.107.1.37 ~all" [+0 = 10 mechanisms] _spf-ssg-a.example.com  text = "v=spf1 include:_spf-ssg-b.example.com include:_spf-ssg-c.example.com ~all"  [+2 = 12 mechanisms] _spf-ssg-b.example.com  text = "v=spf1 ip4:207.68.169.173/30 ip4:207.68.176.1/26 ip4:207.46.132.129/27 ip4:207.68.176.97/27 ip4:65.55.238.129/26 ip4:207.46.222.193/26 ip4:207.46.116.135/29 ip4:65.55.178.129/27 ip4:213.199.161.129/27 ip4:65.55.33.70/28 ~all"  [+0 = 12 mechanisms] _spf-ssg-c.example.com text = "v=spf1 ip4:65.54.121.123/29 ip4:65.55.81.53/28 ip4:65.55.234.192/26 ip4:207.46.200.0/27 ip4:65.55.52.224/27 ip4:94.245.112.10/31 ip4:94.245.112.0/27 ip4:111.221.26.0/27 ip4:207.46.50.221/26 ip4:207.46.50.224 ~all" [+0 = 12 mechanisms] spf-a.secondexample.com  text = "v=spf1 ip4:157.55.0.192/26 ip4:157.55.1.128/26 ip4:157.55.2.0/25 ip4:65.54.190.0/24 ip4:65.54.51.64/26 ip4:65.54.61.64/26 ip4:65.55.111.0/24 ip4:65.55.116.0/25 ip4:65.55.34.0/24 ip4:65.55.90.0/24 ip4:65.54.241.0/24 ip4:207.46.117.0/24 ~all" [+0 = 12 mechanisms] Character String Too Long 255 character limitation in a single string https://kb.isc.org/article/AA-00356/0/Can-I-have-a-TXT-or-SPF-record-longer-than-255-characters.html http://www.string-functions.com/length.aspx You may have more than 255 characters of data in a TXT or SPF record, but not more than 255 characters in a single string. If you attempt to create an SPF or TXT record with a long string (>255 characters) in it, BIND will give an error (e.g. "invalid rdata format: ran out of space".)  Strings in SPF and TXT records should be no longer than 255 characters.  However to get around this limitation, per RFC 4408 a TXT or SPF record is allowed to contain multiple strings, which should be concatenated together by the reading application.  In the case of use for SPF (using either TXT or SPF RRs) the strings are concatenated together without spaces as described below.  Reassembly by other applications of multiple strings stored in TXT records might work differently. 3.1.3. Multiple Strings in a Single DNS record As defined in [RFC1035] sections 3.3.14 and 3.3, a single text DNS record (either TXT or SPF RR types) can be composed of more than one string. If a published record contains multiple strings, then the record MUST be treated as if those strings are concatenated together without adding spaces. For example: IN TXT "v=spf1 .... first" "second string..." MUST be treated as equivalent to IN TXT "v=spf1 .... firstsecond string..." SPF or TXT records containing multiple strings are useful in constructing records that would exceed the 255-byte maximum length of a string within a single TXT or SPF RR record. EXAMPLE text = "v=spf1 ip4:199.15.212.0/22 ip4:72.3.185.0/24 ip4:72.32.154.0/24 ip4:72.32.217.0/24 ip4:72.32.243.0/24 ip4:94.236.119.0/26  ip4:37.188.97.188/32 ip4:185.28.196.0/22 ~all“ text = "v=spf1 ip4:199.15.212.0/22“ " ip4:72.3.185.0/24 ip4:72.32.154.0/24 ip4:72.32.217.0/24" " ip4:72.32.243.0/24 ip4:94.236.119.0/26" " ip4:37.188.97.188/32 ip4:185.28.196.0/22 ~all" Null Records in the SPF Record A record that is NULL or that does not exist will break an SPF record.  Syntax within the record is very important, if there are extra spaces between mechanisms it will count as NULL. EXAMPLE text = "v=spf1 ip4:199.15.212.0/22“ <- accurate text = "v=spf1 ip4: 199.15.212.0/22“ <- NULL (NOTE the space between IP4: and the IP) Repetitive Records in the SPF Record - Void Lookups If there are too many repetitive mechanisms in the SPF record, including records that cascade (for example when using "include:") the record will break. There is a MAX of 2 void look ups in an SPF record.  More than that and the record will break.  This prevents SPF records from being used in Denial of Service style attacks. Validation Tools SPF checker, syntax validator and SPF tester http://www.kitterman.com/spf/validate.html SPF checker http://vamsoft.com/support/tools/spf-policy-tester SPF validator http://vamsoft.com/support/tools/spf-syntax-validator CIDR Calculator http://www.subnet-calculator.com/cidr.php Nslookup http://network-tools.com/nslook/ SPF creation wizard http://www.microsoft.com/mscorp/safety/content/technologies/senderid/wizard/ Common SPF errors http://www.openspf.org/FAQ/Common_mistakes SPF syntax definitions http://www.openspf.org/SPF_Record_Syntax
View full article
Adobe Marketo offers a number of ways to contact Marketo Support directly for assistance from our different support regions. Further details about your Adobe Success Plan can be found HERE. Note: If your Marketo Instance and Users have been migrated to Admin Console, refer to this Admin Console Overview page for managing the Adobe entitlements across your organization and to engage Marketo Support.   Marketo Support Portal (https://support.marketo.com)   The Marketo Support Portal features a web form to submit support cases to Marketo Support. The form provides Authorized Support contacts the ability to provide details on the support issue that allows Marketo Support to efficiently and effectively assign your case to the best suited available support engineer. We encourage you to leverage our Best Practices when submitting your case to Marketo Support.   Support Services – Regions, Hours, and Languages Authorized Support contacts can engage Marketo Support by calling one of our Adobe Enterprise Phone Numbers for your region. Live Telephone and Online Technical Support Priority 1 incidents: 24x7x365 via phone or online support case Priority 2-4 incidents: Support available during regional business hours via chat or online support case. Regional Business Hours Applicable regional business hours are based on the billing address in the Sales Order or purchasing documents. If Adobe is contacted for support by someone other than the designated Named Support Contacts, Adobe may request that that the support case be resubmitted by a Named Support Contact. Languages Japanese language support is available during Japanese regional business hours, excluding holidays or Adobe days off. Japanese support is not available for Adobe Commerce. With the above exception, all Support will only be provided in English. Support Access Customer will grant Adobe Support access to applicable customer systems via remote support tools controlled by Adobe for the purpose of troubleshooting and support services. Regional Business Hours for Support Applicable regional business hours are based on the billing address in the Sales Order or purchasing documents.   Americas Europe, Middle East & Africa Asia Pacific Japan 6 am – 5:30 pm 9 am – 5 pm 9 am – 5 pm 9 am – 5 pm  
View full article
Abuse Report An abuse report is when an email recipient forwards a complaint directly to abuse@marketo.com.  Marketo’s Privacy and Compliance Team processes all complaints to these addresses and will unsubscribe the complainer when possible.   Feedback Loop Complaint A feedback loop complaint is when an ISP forwards the complaints that originate from their users.  For example, when someone clicks the SPAM or JUNK button in their email client. ISPs that offer FBLs expect that subscribers like Marketo will mark the complainer as unsubscribed in the original database.  Marketo does process FBL complaints and marks the email address as unsubscribed.   Additional Information: Feedback Loops (FBL) Abuse Report Deep Dive Finding Leads that are Auto Unsubscribed for Email Spam Complaints / Feedback Loop (FBL)    
View full article
From the Marketo Email Use Policy: "...You may not send any Unsolicited Email by use or means of the Marketo Service. "Unsolicited Email" is defined as email sent to persons other than: persons with whom you have an existing business relationship, OR (ii) persons who have consented to the receipt of such email, including publishing or providing their email address in a manner from which consent to receive email of the type transmitted may be reasonably implied." The full text of the policy is here: https://documents.marketo.com/legal/use-policy/ An abuse report is a report that an individual sends to abuse@marketo.com alleging that a Marketo customer sent unsolicited email. There are a number of reasons why someone might report abuse. Here are a few common reasons people report abuse to us: The person forgot they opted-in to the mailing The person received genuinely unsolicited email The person opted in, but the branding in the email was different than the branding on the opt in form so it was not clear the email they received was connected to their opt-in experience Someone signed up for your list with the wrong address, and the person who actually received your email felt it was abusive   For additional reference - Abuse Report Deep Dive  
View full article
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
View full article
If you sent an email from the Lead Database (as a Single Flow Action), as part of a campaign, or as a test email but didn't receive it, here are some tips.   Check the "From:" address   When sending a test message, make sure to check the "From:" address setting on your message. To do this, go to the Email Settings tab of the email editor. In the "From:" field, make sure that you either have a single valid email address, or a valid email address as the default, if you are using a token.   Many people want to send their messages from the lead owner. When you use the send test feature, the email address you are sending to doesn't have a full lead record, and so it doesn't have a lead owner. Since Marketo cannot send an email with no "From:" address, test messages without a valid email address in the "From:" field will not send.   Send as a Lead   If you have verified that the email had a valid From: address and you still aren't getting it, make sure to create yourself as a lead and send using a flow action.   See if the mail was sent   If you sent the email as part of a campaign or Single Flow Action, check the campaign's Results tab or your lead detail page to see if that mail was already sent to you. If it hasn't been sent yet, try waiting a little while longer.   Check your Junk Mail   In your email client, check your Junk Mail or Spam folder to see if the mail landed there. If it did, you should change the content of your email.   Check your corporate spam filter   Your corporate mail server may have blocked emails from Marketo; you should contact your IT department to see if this is the case. Please see our instructions for whitelisting Marketo's email servers: Add Marketo to Your Corporate Email Whitelist   Try sending to a different recipient   If you sent the original mail to your corporate account, try sending to a personal account on Yahoo or Gmail. If you sent it to a personal account, try your corporate mail account.    Use Marketo's Email Deliverability product   The Email Deliverability PowerPack, with Design Informant and Inbox Informant, can warn you when your mail is being rejected because of its content and help you identify junk mail pitfalls. Also, using Domain Keys and SPF improve the chances of your email landing in your leads' inboxes.   Contact Marketo   If you still can't figure out what happened contact Marketo to see if we can help.
View full article
When using Marketo it is not a requirement to set up DNS text records for SPF and DKIM.  However, Marketo recommends setting up SPF and DKIM because it improves the deliverability of your mailings.  Configuring and implementing one or both of these records is a way to verify that the server sending your mail is authorized to do so.   If a recipient domain is configured to check for SPF and/or DKIM and those DNS records are available and your mail passes the SPF/DKIM check, it further reinforces its good reputation.  Not implementing SPF/DKIM records does not add to or subtract from its reputation, it’s just not there.   Please note, not all domains check for SPF/DKIM and if this is the case, again, the presence of these records does not add or subtract from your mail’s deliverability. There is no negative effect to setting up these records, and it can improve your deliverability.  It is for these reasons that Marketo recommends setting up these DNS records and configuring their use in your instance of Marketo.   For more information on how to set up and configure SPF/DKIM, please read our KB article here.
View full article
Issue Users for your Marketo instance are unable to log into the instance. Solution Check your landing page URLs and email links. If these are also unavailable, your Marketo instance may have been shut off. Marketo Support can confirm whether your instance has been deactivated, but are not able to reactivate it.  In this situation, please contact your Marketo Account Representative to discuss the status of the instance and regaining access.        
View full article
Issue Issue Description You enabled a field for email CC and it is working for some email CC recipients, but some records on the CC are not receiving the email.   Solution Issue Resolution If any of the CC email addresses are known leads in your Marketo database and marked as unsubscribed they will not receive the email, even if the email is marked as operational.  
View full article
Any emails being sent as part of 'Forward to Friend' will create that user as a new lead (provided that the lead does not already exist in Marketo). When leads are created in Marketo via the 'Forward to Friend' feature, Marketo automatically unsubscribes the lead records in order to protect our global customers from anti-spam laws. This is because a lead being sent a forwarded email doesn't qualify as opting in to a mailing list and also prevents them from getting any other emails by accident.    
View full article
Issue How to re-subscribe records who are already unsubscribed.     Solution Once the person is willing to resubscribe to receive your emails, either of the following can be done: Smart Campaign: Change Data Value of "unsubscribed" to false.You can either use a Smart Campaign to execute this flow or can just go with single flow action ( select the lead, Person actions > Marketing > Change Data value; Attribute: Unsubscribed, New Value: False.) You can manually change unsubscribe from True to False. To do this, go to Lead database, click on the lead ( whom you need to unsubscribe), go to lead Info tab, look for unsubscribe field , remove the tick or check off the unsubscribe field checkbox.        
View full article
Issue You see that a lead has an unusually high amount of Clicked Link activity for a particular email after delivery.     Solution There can be a couple reasons for this.  If you see that all links in the email are being clicked immediately upon delivery, it is likely that the lead's email security software is link-testing to guard against phishing or malicious links.  However, if you see an unusually large number of link clicks over the course of a day or two, it may be that the lead forwarded the email to other people who clicked on the links.  Since the tracking links are specific to the lead who was sent the original email, if the email is forwarded to other people, their clicks will be recorded under the initial lead's activity history. Marketo does not have a way to confirm this is the case, but if you open the Click Link activities in the leads Activity Log and look at the details, you may see the User Agent (which indicates the operating system and client software used to display the email) is different for each click.  If you see a variety of different user agents in the details, it is likely the email is being opened and clicked by different people who were forwarded the email.
View full article