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?

Summary The customer wants to know if a nurture email was not sent to a recipient due to communication limit, then will it be sent in the next cast, or that email will not be sent again? Issue Individual(s) were supposed to get an email from a Nurture (Engagement) Program cast but failed to receive the email due to hitting the communication limits set in the instance. Do you need to manually send the email to the individual(s) via a separate Smart Campaign or will it be sent, automatically, on the subsequent cast for the Nurture Program? Environment Marketing Activities Nurture Programs Engagement Programs Admin Communication Limits Solution You don't need to act on these scenarios as the individual(s) impacted by the Communication Limits will be sent the applicable email in the next cast for the Nurture Program. The only reason that the individual wouldn't be sent the email in the subsequent cast for the Nurture Program would be if the person would hit their Comm Limit again. Should that happen, you might want to review your Communication Limits settings or review the individual(s) impacted and see why they keep hitting the Comm Limits. Reference: How Do Communication Limits Work? - Marketing Nation (marketo.com) Root Cause Communication Limits being hit during Nurture Program cast execution

Issue You have a Batch Campaign or Email Program setup where the amount of people qualified is more than what's listed under the Smart Campaign Person Restrictions limit (for more context, see Enabling Person Restrictions for Smart Campaigns). Within that same program or campaign, you calculate that between the number of qualified people reduced by how many are blocked from processing puts the total count of records below the Person Restrictions for the instance. Would the campaign or email program still execute and process the appropriate leads that aren't blocked or does Marketo solely look at qualified members to determine if that's more than allowed based on Person Restrictions? Environment Admin Marketing Activities Marketo Scheduling Solution Yes, the campaign will still run as expected. Both Email Programs and Smart Campaigns effectively disqualify non-marketable people before processing records towards the Campaign Processing limit. Example: Your instance is setup to limit campaigns from processing more than 500k records in a given Smart Campaign. If you have 600k qualified for your Smart List (Audience) but 200k of the records are blocked, the campaign will still run as only 400k marketable people qualify to actually get processed through the campaign. Blocked records don't get processed through the campaign execution and, therefore, don't add or contribute to campaign processing limits.

Issue Field values updated in Marketo do not sync to SFDC when the record exists as a Contact. Environment Marketo - CRM Native contact Sync Solution The issue is caused by the interaction of the Block Field Updates with the conflict resolution rules for Contacts described here. The Block Field Updates will prevent Marketo from writing values from Salesforce into Marketo, but it does not prevent the sync from attempting to sync those values. If a field has Block Field Updates enabled to prevent updates from SFDC and that fields gets updated in both Marketo and Salesforce at the same time, Marketo will attempt to use our conflict resolutions rules to allow the update from SFDC to override the Marketo updated. The Block Field Update prevents this from occurring which leaves the records stuck unable to update the value in either system. To resolve the issue for the specific records, the Block Field Updates setting must be removed for the specific values to allow the values from Salesforce to sync down. Then the feature can be re-enabled. To prevent recurrences of the issue in the future, Users and processes in Salesforce must be prevented from editing those values to prevent a conflict from occurring.

Summary Marketo Form Does Not Appear on a Landing Page Issue Marketo Form embedded on a Landing Page and the Form does not load. Environment Marketo Solution If you are able to reproduce the behavior in a Private Browsing window using Firefox, then issue is most likely caused by the embed being used. Examine the embed code on the page and ensure that the Form is loading using your instance's Landing Page Domain. For example you may see your embed code formatted as <script src="//app-sj01.marketo.com/js/forms2/js/forms2.min.js"></script> <form id="mktoForm_1"></form> <script>MktoForms2.loadForm("//app-sj01.marketo.com", "123-ABC-456", 1);</script> It instead it should look like <script src="//123-ABC-456.mktoweb.com/js/forms2/js/forms2.min.js"></script> <form id="mktoForm_1"></form> <script>MktoForms2.loadForm("//123-ABC-456.mktoweb.com", "123-ABC-456", 1);</script> Once the embed code has been updated, load the page again and the Form should now appear. Root Cause Firefox released a privacy update that blocks loading of certain elements directly from the marketo.com domain. This prevents Marketo Forms from loading when they point to a source of marketo.com. Updated the embed code to use your Landing Page Domain allows the form to load correctly.

Summary Adding Webinars from Additional Users Issue After setting up the Marketo/Zoom integration and attempting to connect a Webinar to an Event Program, you may see the message "This Account has no Webinars" or certain webinars may be missing as an option. Environment Zoom/Marketo Solution When setting up the Marketo/Zoom integration an Admin user must be connected to the Launchpoint integration. By default, only webinars created directly by this Zoom user will appear as options. If other users have shared webinars with this admin, additional steps must be taken to make them visible in Marketo. In this article you will find the steps to add additional Zoom users to the Marketo integration configuration. Once those users have been added, webinars they own will be available as options in Marketo. Webinars owned by users not added with the instructions above will not be available in Marketo.

Marketo now fully supports responsive landing pages, we call the new style a "Guided Landing Page". A Guided Landing Page is one that is capable of dynamically resizing itself for different window sizes and devices. If you’ve used the Marketo interface to set up an Email Template and an Email, the basic concept of setting up a responsive template and landing page will feel pretty familiar. First you have to define a template that contains the editable areas of the landing page, once that is completed you use that template to build the landing page. Unlike the Email editor however, constructing and altering a responsive landing page template will require a minor amount of HTML knowledge. If you are not comfortable in HTML and do not have an HTML developer available to assist you, Marketo’s services team can help! You can reach them at services@marketo.com To get started, first visit our Template Library for Guided Landing Page Templates located here: https://docs.marketo.com/display/public/DOCS/Guided+Landing+Page+Templates;jsessionid=5D71353C1CBF708DEC3DAB1588E78B4F Select the template you’d like to use, right click the link and select “Save Link As” to download the HTML code. Once the template is saved locally on your computer, go to where it’s saved and open it in the text editor of your choice. What you’ll see is a whole bunch of HTML: In your text editor, use CTRL-A to select all and CTRL-C to copy it to the clip-board. (On a Mac this is Command-A and Command-C) then log on to your Marketo instance. In your Marketo instance, go to the Design Studio and select “New Landing Page Template” In the New Landing Page Template window, assign your template a folder and a name, then make sure the editing mode is “Guided”. The “Free-form” mode is for the non-responsive templates that we had before. Click “Create”! Now we’re ready to replace the sample template code with the code you downloaded from the Template Library. CTRL-A (Command-A on a Mac) will select the starter code and CTRL-V (Command-V) will paste the template code right over the top of the existing code. The template will save itself automatically when finished. Now that the template is ready to go, we’re ready to see it in action! Using a Marketo Guided Landing Page Template: Now that we have a template created, we’re ready to start using it. Close the template tab where the code is and go back to the Design Studio. Select the template you just created and approve it. Once the template is approved, you can use it to create a landing page. In the new landing page window, assign a folder and a name and select the template you just created. Click “Create”! You can always identify which templates are responsive and which are not by looking for a little window icon on the right hand side. If the window icon is present then that template was created using the new Guided editor and is fully responsive. If the window is not present, then that template was created using the old editor and it’s NOT responsive. You cannot automatically convert an old non-responsive template to a new one. Congratulations! Your new responsive template is ready to use! Please see our documentation here on how to edit a Guided Landing Page: https://docs.marketo.com/pages/releaseview.action?pageId=7515306

Issue Issue Description If a page is not loading in your browser for Marketo, this can sometimes be due to network related issues. We can help troubleshoot by using a HAR file from the browser to see network traffic. Solution Issue Resolution Instructions to generate a HAR file broken down by browser version: Chrome In Chrome, go to the page within Marketo where you are experiencing trouble. At the top-right of your browser window, click the Chrome menu (⋮). Select Tools > Developer Tools. The Developer Tools window opens as a docked panel at the side or bottom of Chrome. Click the Network tab. Select Preserve log. You will see a red circle at the top left of the Network tab. This means the capture has started. If the circle is black, click the black circle to start recording activity in your browser. Refresh the page and reproduce the problem while the capture is running. After you successfully reproduce the issue, right click on any row of the activity pane in the Network and click Save as HAR with Content. Save the HAR file. Select the Console tab. Right-click anywhere in the console and select "Save as...". Name the log file Chrome-console.log. Send both files as shared links in a reply to your case. Firefox In Firefox, go to the page within Marketo where you are experiencing trouble. Click the Firefox menu (Three horizontal parallel lines) at the top-right of your browser window. Select Web Developer > Network. The Developer Tools window opens as a docked panel at the side or bottom of Firefox. Click the Network tab. Select Persist logs. After you successfully reproduce the issue, right-click any row and select Save all as HAR. Firefox typically takes a few seconds to prepare the download. A slight delay on this step is normal. Select the Console tab. Right-click any row and select Select all. Paste the content in a text file and name it console-log.txt. Send both files as shared links in a reply to your case. Safari In Safari, go to the page within Marketo where you are experiencing trouble. In the menu bar at the top, click Develop and select Show Web Inspector. Click Preserve Log. Click the Console tab and select Preserve Log. Go back to the Network tab. Refresh the page and reproduce the problem while the capture is running. Once you have reproduced the issue, select Export. Save the HAR file. Click the Console tab. Right-click any row and select Select all. Paste the content in a text file and name it console-log.txt. Send both files as shared links in a reply to your case. Internet Explorer 11 (IE 11) In Internet Explorer, go to the page within Marketo where you are experiencing trouble. Click the gear icon in the top right. Select F12 Developer Tools. Click the Network tab Clear the Clear entries on navigate option, which is selected by default. The icon looks like blue arrow with a red X. The green play button (Start Profiling Session), should be selected by default. This means the capture function is running. Refresh the the page and reproduce the problem while the capture function is running. Once you have reproduced the issue, click the Export as HAR icon. The icon looks like a floppy disk. Click the Console tab. Right-click any row and select Copy all. Paste the content in a text file and name it console-log.txt. Send both files as shared links in a reply to your case.

Issue When using the [mktorest.com/rest/asset/v1/emailTemplates.json] end-point to pull all Email templates, the COUNT is much less than what is shown in Marketo's Design Studio Global Search. Solution This is the expected behavior. When viewing the total count of Email templates in the Design Studio UI, it will count EACH shared template that is shared across other workspaces, counting the same template multiple times depending on how many workspaces it's shared to. However, when retrieving the Email Templates from the REST API, it will only return DISTINCT Email Template ID's from the originating shared workspace where the template resides. It will not return the templates from the shared workspaces. Root Cause REST API Expected Behavior

Issue You may notice this permission error "You do not have sufficient privileges to perform this action" when previewing an email even though the user role has permission to access the emails. Solution This can happen when the user role didn't have any access to the lead database as shown in the picture. This is a article attached image The user role needs the top-level access to the Lead Database(1 of 15). This is because the email previewer allows one to view the asset as if you were a specific lead, but if you can't see the leads, then the error will trigger. To fix this issue, you would need to provide the user role with top-level access to the lead database.

Issue When using the Merge Lead(s) REST API end-point and merging multiple leads, which field values would be copied to the winning record? In the below example, the winning lead record has a blank value for Job Title. When merging all 4 leads, which field value will get copied to the winning record from the list of losing records? This is a article attached image Solution The field values that will be injected to the winning lead record are directly impacted by the order of leadID's in the Lead array parameter of the call, where the FIRST leadID listed in the parameter array will be the winning value IF the field on the winning Lead record is blank. URL Example {{baseUrl}}/rest/v1/leads/4231/merge.json?leadIds=2232,1323,1455 RESULT Based on the above excel chart, LeadID 4231 (Winner) would have their Job Title field updated = 'electrician'. URL Example #2 {{baseUrl}}/rest/v1/leads/4231/merge.json?leadIds=1323,1455,2232 RESULT Based on the above excel chart, LeadID 4231 (Winner) would have their Job Title field updated = blank/empty. Root Cause This is the expected behavior when merging multiple leads via the REST API Merge Leads end-point.

Summary When renaming a field in a CRM Custom/Entity it does not reflect the change in the constraint of filters/triggers/ Issue I renamed a field in my CRM Custom Entity/Object (MSD/SFDC) and I refreshed the schema. I can see the field name change reflected in the CRM Custom Entity/Object, but when I look for the field in constraint for filter/trigger I only see the old name. Environment Smart List Solution The workaround is that the customer can create a new field on the SFDC side and copy all the values from the old field to the new one. Then, this field can be used in smartlist filters. Old field can be disabled after that. Root Cause We are not propagating field name changes from SDFC to Marketo.

Summary Learn how to troubleshoot the REST API Error: read ECONNRESET. Issue You are getting the following HTTP error when attempting to call the associated REST API. REST API Error: read ECONNRESET Cause This error might occur because of issues on the local network or HTTP client config. Here are some possible causes of this error. HTTP Client Configuration Issues: The error may occur due to incorrect, incomplete, or incompatible settings in your HTTP client. To align your HTTP client settings with the Marketo REST API requirements, you should review and update your HTTP client settings. Proxy Server or Configuration Problems: If you use a proxy server, its configuration may result in an HTTP error. Verify your proxy server settings and consult your network administrator for accurate configuration if necessary. Faulty Network Equipment: Issues with hardware such as switches and routers, particularly if they are malfunctioning or improperly configured, can cause the problem. You should investigate the status and settings of your networking devices to determine if this is the issue. Solution To resolve this issue: Review and adjust your HTTP client's configuration to match the Marketo REST API specifications. Check your proxy server settings and consult your network administrator if needed. Examine network equipment for faults or incorrect configurations.

Issue When using the GET Activities API with a specific list Id in the parameter, the response will get all the specified activities from other assets as well. This is the endpoint for this article. Solution Instead of using list Id (listId) as a parameter, change that to asset Ids (assetId) in the API call. The Asset ID (assetId) is the Id of the primary asset for an activity. Then, the response will narrow down the activities associated to the primary asset by looking up the Id during the call.

Issue Issue Description Velocity scripted tokens are not displaying the default value in the asset if the information required for the token is not in the database. Solution Issue Resolution Email Script tokens are not designed to work with the {{my.token:default=Some Value}} syntax, which is for simple tokens. Rather, you must output the default value within the code (using #if/#else, $display.alt or any other conditions) then include just {{my.token}} in the email. Examples can be found here: https://developers.marketo.com/email-scripting/

Summary New checkbox for query parameters available when adding new content or editing current content. Issue You were previously unable to specify query parameters for predictive content, and query parameters were not used when adding new content, editing current content, and reporting on URL clicks. Autodiscovery works by adding a new URL to the DB, and later on, clicking counts are accumulated against the newly found asset. The asset is determined based on the URL (and there, it previously didn't account for anything that followed the ? in the URL. The same was used as a validation when a user added new content. The rule to determine this part of the URL, minus the query parameters, was a requirement back then and was taken into account during design. Solution As you add predictive content from the predictive content page, you need to have the checkbox on this page to allow the user to decide whether they want to include/exclude the query parameters while adding it. The same thing should be followed for editing predictive content as well. Engineering built a nuanced approach that provided flexibility to include or exclude query patterns in determining a unique URL and added a feature to include query parameters when manually creating a piece of content. It should rightly identify the right asset to record clicks/views against as well.

Issue A lead skips the send email flow step, but processes through the other flow steps. In the results tab and in the lead activity log there is no mention of the email step. Example: Solution If your lead record is blocked from receiving emails, Marketo will not send an email to that lead. If an email is not sent, there will not be a record in the activity log for the lead record or in the results tab of the smart campaign, but the lead will still go through the other steps as normal.

Issue Lead was created but does not appear in the expected Workspace in the Lead Database. Solution Check if there are any assignment rules that the lead may have qualified for a lead partition associated to another Workspace (e.g. Workspace B) https://docs.marketo.com/display/public/DOCS/Assigning+Person+Partitions+with+Assignment+Rules Check the lead's activity log to see if the lead's partition was changed after it was created to another partition associated to another Workspace (i.e. single flow action or via a smart campaign)

Summary Learn how to resolve issues with uploading SVG files to Marketo. Issue You are not able to upload Scalable Vector Graphics (SVG) files to Marketo. You are encountering errors during the upload process or facing issues with improper display in browsers after uploading. Cause: The root cause behind such issues is often Marketo's security checks, which may reject certain properties of SVG files. This can lead to conflicts between what Marketo accepts and what browsers can display. Solution To address SVG files not being accepted or displayed correctly in Marketo, try the following steps: 1. Change File Extension to .xml: Instead of saving the file with a .svg extension, save it as a .xml file. This will change the server MIME type and allow it to be uploaded to Marketo. Example: If your file is named "example.svg," rename it to "example.xml" before uploading it to Marketo. 2. Remove Unwanted Properties: If the SVG file contains additional properties or namespaces causing rejection by Marketo, removing them can resolve the issue. For instance, the xlink namespace, if present at the top of the SVG file, may lead to rejection by Marketo. Exercise caution not to remove essential properties, as this could result in errors when attempting to display the file in a browser. Example: If your SVG file has the following line: xml xmlns:xlink="http://www.w3.org/1999/xlink" Remove this line from the SVG file's code using a text editor. When saving SVG files from applications like Adobe Illustrator, changing the file extension or manually editing the code may be challenging. However, using any file explorer, you can easily change the file extension to .xml. Code editing can be performed using a text editor to manually remove unwanted properties. Always back up the original SVG file before making any changes to prevent permanent data loss. By following these steps, you should be able to successfully upload SVG files to Marketo and ensure proper display in browsers.

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Top Blocklists - What You Need to Know

Nurture Program Email Blocked Due To Communication Limits

Smart Campaign Limits And Blocked Records

Block Field Updates not syncing marketo field values to SFDC

Lead cannot see unsubscribe form

Webinars Missing from Zoom Integration

Getting Started With Guided Landing Pages:

How to Generate a HAR File for Network Troubleshooting

Marketo Sales Insight is Disabled

Email Template Count Different in UI When Compared to REST API Count

Permission Error When Previewing Email

What Field Values Are Copied to Winning Records When Merging Multiple Records From REST API

When I rename a field in my CRM Custom Entity/Object why is the change not reflecting in the constraint of a filter/trigger?

Troubleshooting REST API Error: read ECONNRESET

What is the Exported (CSV) Report row limitation in RTP/Web Personalization?

Using API to get lead activities from specific asset

Email Script (Velocity) My.Tokens Not Displaying Default Values

Predictive Content Query Parameters

Lead Skips the Send Email Flow Step But Runs Through the Other Flow Steps

Newly Created Leads Not Available to Expected Workspaces

Troubleshooting SVG Upload and Display Issues in Marketo