Knowledgebase

Featured article

Included in this article Overview Data you’ll get from Email Bounces Bounce Categories Hard Bounces Soft Bounces Bounce Details Building the Directory 1. Create 6 custom fields 2. Create a Program to house everything 3. Create a Static List 4. Create two Smart Campaigns Smart Campaign One - Logging Email Bounces with Bounce Details Smart Campaign Two - Remove Leads From the List After Successful Deliveries 5. Create Custom List View Showing Bounce Details Overview Bounce activities carry details for why the email was bounced, but it’s housed within the activity log entry, not in a field on the lead record, so it’s difficult to export that data. This article will show you how to extract that information to create a directory of leads bouncing emails and how to make the list automatically update. This will also create counters for bounces and successful re-deliveries after bounces happen. Data you’ll get from Email Bounces Bounce Categories Email bounces come in different types depending on why the email was bounced; Hard Bounces or Soft Bounces. Hard Bounces Hard Bounces come in two types, Category 1 and Category 2. Category 1 bounces are emails that have been marked as spam by the recipient mail server. Many email servers monitor blacklists or spam traps, so after de-listing with them, leads that have had a Category 1 bounce previously may be able to receive emails again. Category 2 bounces occur due to an email address that is invalid or doesn’t exist. Soft Bounces Soft Bounces come in three different types, Categories 3, 4 or 9. Category 3 bounces are usually temporary, caused by full mailboxes, timeouts, or throttling. Any email with this designation has been retried for up to 24 hours (36 for AOL). Category 4 bounces are caused by technical problems, Transient Failures, Admin Failures, DNS Failures. Any email with this designation has been retried for up to 24 hours (36 for AOL). Category 9 bounces are unknown, undetermined or gibberish details. Any email with this designation has been retried for up to 24 hours (36 for AOL). Bounce Details When an email is bounced, the recipient mail server includes details of why it was bounced. These are created by the admin of the recipient mail server and vary greatly, but most will give some explanation that can give valuable information. Email Bounce Codes Building the Directory 1. Create 6 custom fields You’ll need 6 custom fields, two DateTime fields, two Score fields, and two String fields Name the DateTime fields “Bounce Date” and “Email Delivered After Bounce”. Name the Score fields “Email Bounces” and “Deliveries After Bounces” Name the String fields “Email Bounce Details” and “Email Bounce Category” Directions for creating Custom Fields can be found here: Create a Custom Field in Marketo 2. Create a Program to house everything Use a default program type and name it "Directory of Leads Bouncing Emails". Info on creating programs can be found here: Create a Program 3. Create a Static List This static list will be your actual directory that contains all of the leads that are currently bouncing emails. Name it "Active Bounce List". Info on creating a static list can be found here: Create a Static List 4. Create two Smart Campaigns These two Smart Campaigns are what will be used to add and remove leads from your active bounce list. Info on creating Smart Campaigns can be found here: Create a New Smart Campaign Smart Campaign One - Logging Email Bounces with Bounce Details Your first Smart Campaign will be used to listen for any email bounces that occur. The campaign will populate the “Bounce Date”, “Email Bounce Category” and “Email Bounce Details” fields. It will then add one point to the “Email Bounces” score field which can be used to count how many bounces have occurred per lead. Lastly, the campaign will add the lead to the static list which will be an active directory of leads who are bouncing emails. Campaign Smart List Use the two triggers of “Email Bounces” and “Email Bounces Soft” in the Smart List. Set both triggers to “is any” so that they will fire whenever any email bounces for any reason. Campaign Flow The Flow of the campaign will have 5 flow steps. The flow will use a System Token and some Trigger Tokens, which can be used to pull details out of the action that activated the trigger. In this case, the Trigger Tokens will be pulling out the details on why the emails were bounced. That info is in the bounce message and is logged in the lead's activity log. Normally you'd have to comb through the activity log one at a time to find these details for each individual lead. This method, however, will pull the details out automatically for all leads. Flow Step 1: Change Data Value Attribute: “Bounce Date” New Value: {{system.dateTime}} Flow Step 2: Change Data Value. Attribute: “Email Bounce Category” New Value: {{trigger.category}} Flow Step 3: Change Data Value Attribute: “Email Bounce Details” New Value: {{trigger.details}} Flow Step 4: Change Score Score Name: “Email Bounces” Change: +1 Flow Step 5: Add to List List Name: “Active Bounce List” Smart Campaign Two - Remove Leads From the List After Successful Deliveries Campaign Smart List The Smart List of the campaign will need a trigger for “Email is Delivered” set to “is any” and also a filter of “Member of List” looking just for leads that belong to your Static List. This way, the campaign will only apply to leads who have had an email bounce but have then had an email successfully delivered afterwards. Campaign Flow The Flow of the campaign will have 3 flow steps to do the following; log when the email was delivered, add a point to the "Deliveries After Bounce" Score Field, and remove the lead from the "Active Bounce List". Flow Step 1: Change Data Value Attribute: “Email Delivered After Bounce” New Value: {{system.dateTime}} Flow Step 2: Change Score Score Name: “Deliveries After Bounces” Change: +1 Flow Step 3: Remove from List List Name: Operational.Active Bounce List 5. Create Custom List View Showing Bounce Details The custom fields you’ve created for email bounce information won’t show automatically in the view of your list. You can create a new view of the list to show just this information so that when it is exported it will give you only the email bounce information you need. Once the list has the necessary details, it can be exported with those columns included so that you can work with it. You can identify emerging trends and issues with your deliverability by looking for common themes among the bounce details. Directions for creating Custom Views can be found here

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?

If your company moves to a new location, follow these steps to change the mailing address in your email templates located in the footer. 1. Find the email template that you want to update your company mailing address. We're using the Rounded Corners email template for this example. 2. Click Edit Draft. The email template shows in the preview window. 3. Click HTML Source. 4. Scroll to where your current mailing address is located (usually at the bottom) and update the information. 5 Click Preview to view your changes. Validate your changes. 6. Click Save and Close. 7. Approve your draft. 8. Click Emails from the tree on the left side of your screen. 9. Any emails that use the updated template will need to be re-approved. 10. You can approve the affected emails in this view (shown in the screen shot above) by highlighting the email(s) and choosing Email Actions > Approve Draft.

Included in this article Overview Your Premier Support entitlement has been enhanced with a Premier Success Team. Now, your Named Support Engineer is part of a 5-member Premier Success Team whose members work in concert to provide a full range of complementary skills. All your Premier support features remain intact (Mentoring Sessions, Accelerated SLAs, etc), but now your Named Support Engineer will be backed by a focused team of Premier Support Engineers to deliver world-class support tailored to meet the needs of your account. Benefits Each team is led by two Lead Support Engineers, and aided by three Premier Support Engineers. With a larger team, your engineers can specialize in specific knowledge areas, and we can connect you with our most senior engineers for your half-yearly instance reviews and mentor sessions. This will help to increase case resolution speed, decrease escalations, and elevate your overall support experience. Your Team Adam Boschma, Senior Technical Support Engineer - Captain Adam has over seven years of customer service and technical support experience, with four years of team management experience. He has been with Marketo for 2 years working as an escalation authority for almost all aspects of the Marketo Platform. Adam enjoys constantly learning, expanding his skills and digging into complex issues. Outside of work, he enjoys everything that the Pacific Northwest has to offer. Everything from the hiking, camping and of course the amazing foods and local craft beer. Nathan Hendrickson, Senior Technical Support Engineer - Captain Nathan is a Marketo Certified Expert and excels in Marketing Activities, Deliverability, and Salesforce integrations. Working through complex configurations and sensitive situations excites him, and he enjoys getting elbow deep to root out issues. During his free time Nathan likes to play video games, go star gazing (as much as you can in Portland), and spend time with friends and family. April Parks, Associate Technical Support Engineer - Specialist Robert Combs, Technical Support Engineer - Specialist Wyatt Hinck, Technical Support Engineer - Specialist

My Salesforce activities are not showing up in Marketo and when I go to the Admin section I see the following sync error: soqlBatchQuery failed - INVALID_FIELD: CreatedDate, Description, Id, IsAllDayEvent, IsDeleted, OwnerId ^ ERROR at Row:1:Column:70 No such column 'IsAllDayEvent' on entity 'Event'. If you are attempting to use a custom field, be sure to append the '__c' after the custom field name. Please reference your WSDL or the describe call for the appropriate names. This is due to lack of permissions for the Marketo Sync User on the Salesforce side. Please have your Salesforce Administrator log into your instance of Salesforce and carry out the following steps: Log into Salesforce with Admin rights Click on your name drop-down and click on Setup In the left hand column, under App Setup, click on Customize Then click on Activities and then Event Fields Click on the All Day Event Field Label then "Set Field-Level Security" Here make sure to check the box under the Visible column for the Profile that the Marketo Sync User is associated to Click Save Once the above changes have been made on next sync we will begin pulling your Salesforce activities and once the next sync is over, the error message in the Marketo Admin section should go away.

Issue When an A/B test is in scheduled state and you would want to cancel it. On clicking "Unapprove Program", an error message shows up saying 'Cannot unapprove program -<program name> - is in use'. Solution Within the program, go to the trigger campaign which references these assets in their smart list, for example 1. 'Program_1.Email_Asset_1' used in 'Open Emails' trigger step in smart list 2. 'Program_1.Email_Asset_1' used in 'Clicks Link in Email' trigger step in smart list Remove asset references above within the smart list of the campaign, navigate to program and click "Unapprove Program". Root Cause This is due to the program asset being used in trigger campaigns within the program. Environment Marketing Activities A/B Test

Issue You want to know the expected behavior if an email is sent to a lead from a Smart Campaign and then you add that exact same email (with the same email asset ID) to an Engagement Program nurture stream the lead is in. Solution The email will not be sent through the nurture stream, because an Engagement Program will not send the same exact same email to a lead twice, regardless of how it was originally sent. However, Marketo will send a cloned version of that email, since the email asset IDs are different.

Issue A lead/person completes an action that should trigger a Smart Campaign located in a Workspace, but the campaign does not trigger. Solution If you have Workspaces and Partitions set up on your instance, some leads may not be available to some campaigns, due to workspace and partition restrictions. When a workspace only has access to certain lead partitions, leads in other partitions are unable to trigger campaigns in that workspace. So if Workspace 1 has access to Partitions A and B, leads in Partition C cannot be included in any campaigns for Workspace 1. To resolve this issue, you would need to change the restrictions that are preventing the leads from being able to trigger campaigns in a particular workspace. These can be changed by going to Admin > Workspaces & Partitions > Edit Workspace (with the appropriate workspace selected). Whether it makes sense to make this change should be reviewed first. Often workspaces are setup to be specific to regions, so check whether it makes sense from a business point of view for leads in a partition to qualify for campaigns in a certain workspace. It may not be desired, and instead it should be checked whether the lead should be in fact in a different partition. Who This Solution Applies To Customers who have Workspaces & Partitions set up in their instance.

Issue Issue Description You try to merge two records in Marketo and a System Error appears ‘Failed to merge leads [Lead ID]' Solution Issue Resolution One of the reasons why the merge fails is the leads are part of a different account in SFDC. Even though it looks like they belong to the same account, you need to verify their account ID in SalesForce to see if they match. Another possible reason is due to lack of permissions on SFDC.

Using the Marketo SOAP API, you can check whether or not your website visitors have filled out a form and present them content accordingly. The following code below is unsupported and is intended to help you develop your own solution. In the resources section of the Marketo website, we use this method for our premium content. For leads who have already registered, their links go directly to the resource. Leads who haven't registered are given links to a landing page. In both cases, the link appears the same. Behind the scenes, a cookie is used to store whether or not this lead has registered: If the user has the premium registration cookie, the premium links are shown. If the user does not have that cookie, the lead's record is retrieved via the SOAP API. Based on the lead's record: If the lead has a valid email address, the premium content links are shown and the premium registration cookie is set. If not, the premium content links are not shown. Instead, they take leads to a landing page to fill out a form. First, you'll need to develop a SOAP API connection to Marketo. The attached ZIP file has a sample connection PHP file. You'll need to make the following changes in this file: ... $this->access_key = 'Your API Access Key Goes Here'; $this->secret_key = 'Your Secret API Key Goes Here'; // // The endpoint is in the "SOAP API Setup" page in the Marketo Admin section // ex. $soap_end_point = 'https://xx-1.marketo.com/soap/mktows/'; // $soap_end_point = 'Your SOAP API End Point URL Goes Here'; // // Errors are sent to this email address. Your web server // must be configured to send email for this to work correctly. // // ex. $this->error_email_address = 'example@example.com'; // $this->error_email_address = 'Put your debug email address here'; ... After creating your SOAP API connection, the next step is to implement the logic that determines which content to show if the user is logged in or not. The get_premium_url_status() function returns true if the lead has the premium cookie or if they've filled out a form. Otherwise, it returns false. You can use that result to determine what content the lead should see. The attached ZIP file has a PHP file that contains an example of this check.

Issue In the activity log, you see that a lead has been added to a Marketo Custom Object, but in the Custom Object tab there is no data. Solution The reason why that it appears as the custom object data is missing for a lead is because the custom object data becomes disassociated to the lead and associated to another lead when the custom object data is pushed into Marketo. When the custom object data is pushed to Marketo intended for lead A with the same dedupe field value of an existing custom object record associated to lead B, it disassociates it from the lead B and associates it with lead A. Therefore, when looking at lead B that has had an 'Add to Custom Object' activity, but does not have the Custom Object data visible in the Custom Objects tab, it is because the custom object data was associated to another lead. For example: On Lead A, custom object data is added on x time with the dedupe field value 'test' --> custom object data is associated to this lead and is visible in the Custom Object tab On Lead B, custom object data is added on y time with the same dedupe field value 'test' --> existing custom object data that was created in previous step is now associated to this lead, becomes visible in the Custom Object tab Since the custom object data is moved to this lead, it is no longer visible in the custom object tab for Lead A.

Issue Description When you invite a New User into a Marketo Instance, you are given the option to assign User Roles. What happens when you assign 2 or more Roles? How many Roles should be assigned? Issue Resolution When a user has 2 conflicting Roles assigned, Marketo will, more often than not, be more restrictive in its willingness to let the user perform the action if the other User Role does not have the permissions to do the action. Marketo Support often sees users assigned the Admin Role, as well as a Marketing User Role. The Admin Role has permission to do everything. Adding an additional Role can cause restrictive permission errors when that user is attempting to do something that the Marketing User Role does not have the ability to do. Example: A new User is assigned 2 User Roles each with different permissions. One User Role has the ability to approve email assets, and the other User Role does not have that permission. In that case, Marketo may restrict the User from being able to approve the email asset. There is not necessarily a limit to how many Roles can be assigned to a User. There is nothing prohibiting you from assigning multiple Roles to a new User. It is recommended that Users are invited with only one role assigned. The resolution could be to tailor User Roles for the specific person, or job position in mind.

Issue Issue Description After following the set up directions for a domain alias for a new landing page domain, the new domain redirects to a Marketo 404 page. The instance has SSL for Landing Pages. Solution Issue Resolution Contact Marketo Support and request that the new domain be added to your SSL certificate. If this has been done, they will be able to help you troubleshoot further. Who This Solution Applies To SSL for Landing Pages

New Lead with no email address and no Marketo cookie: If a new lead fills out a Marketo form. Their Marketo cookie is created, lead details (including the cookie) will be updated and the Lead-Database and RTP sync process will be initiated. They will then be known to RTP and eligible for 1:1 personalized RTP campaigns. This sync process may take a few minutes so personalization based on lead data will be available from the lead’s next visit. Lead with email address but no Marketo cookie: When a known lead with no cookie (e.g. a lead from a tradeshow or a list) receives a Marketo email campaign and clicks on a link in the email and arrives to the website, the RTP script runs and a new Marketo cookie is created for them. The creation of the cookie is also sent to the Lead-Database and initiates the RTP sync process for this lead. This sync process may take a few minutes so personalization based on lead data will be available from the lead’s next visit. Known Lead with email address and Marketo cookie: Any changes to the lead’s data will be synced between the Lead-Database and RTP within 5 minutes interval.

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 Issue Description Occasionally, one leads information may be shown when the form has pre-fill enabled. There are specific circumstances where this is possible, and it is most common during testing. These articles outline the scenarios: Why am I seeing someone else's information pre-filled in my form? Troubleshooting Pre-Fill Forms However, what if the information in the form is submitting to the original lead whose information was shown on the form? Solution Issue Resolution Since the information originally shown in the form was from a cookie, Marketo assumes this is a known record. If no email address is included on the form (this is a bad idea), the data entered into the form will be submitted to the original record shown because there is not an email address to deduplicate against. The solution is to ensure there is an email address on the form. This also prevents leads who are unknown from filling out the form and creating a record in your database with no email address.

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Top Blocklists - What You Need to Know

Changing mailing address information in an email template

Learn More About Your Success Teams, Team Charlie

Salesforce Activities Not Synching to Marketo and Show a Sync Error

Changing a Segment

'Cannot unapprove program -<program name> - is in use' error when trying to cancel a scheduled A/B test

Smart List Subscription “Download Report”

Behavior If the Same Email Is Sent Through a Smart Campaign and a Nurture Stream

Lead/Person Fails to Trigger Smart Campaign Located in a Specific Workspace

Merge Fails When Trying to Merge Salesforce-Synced Leads in Marketo

Webhook Calls and API Limit

Checking for User Registration Via SOAP API

Custom Object Data Missing for Lead

Marketo User with 2 or More User Roles

New Landing Page Domain Shows Marketo 404 Page

Unable to Create Subscription for Static List

How does the Known Leads Targeting work?

Restrict Marketo Logins Based on IP Error

Only One Form Is Pre-filling When Using Multiple Forms on a Marketo Landing Page

Snippet Reporting

Form Pre-Fill Writes One Lead's Info to Another Lead's Record