Knowledgebase

Sort by:
Issue Description Changing your primary domain can be a bit of a daunting task if you don't know where to start, this guide will walk you through the steps you will need to take to use a new domain with your Marketo instance. Issue Resolution Create your new Landing Page CNAME and point that to your Marketo instance. If this new CNAME is going to be used as your primary domain, then the original Domain Name in Admin > Landing Pages will need to be changed to reflect your new domain.  The original domain should be added as a domain alias so any URLs referencing the original domain will continue to work.   https://docs.marketo.com/pages/releaseview.action?pageId=2360189   https://docs.marketo.com/display/public/DOCS/Add+Additional+Landing+Page+CNAMEs   Adding a new primary branding domain (CNAME) for emails is also recommended when changing domains. This will allow tracked links in emails to reference the new domain going forward. You'll want to leave the original branding domain (CNAME) active and listed so that tracked links in any previsouly sent emails will continue to work.   https://docs.marketo.com/display/public/DOCS/Add+an+Additional+Branding+Domain   If you plan on signing your emails with your new domain, setting up a new SPF/DKIM record is recommended to help keep your deliverability rates as high as possible.   https://docs.marketo.com/display/public/DOCS/Set+up+SPF+and+DKIM+for+your+Email+Deliverability   https://docs.marketo.com/display/public/DOCS/Set+up+a+Custom+DKIM+Signature
View full article
  Note: This document applies to the Marketo Secured Domains for Tracking Links product only.   Every link you include in your Marketo emails will have tracking code automatically appended when sent. For those in highly regulated industries, your company may require that you securely encrypt the Marketo tracking links. Remember that Marketo takes the URLs you place inside of emails and shortens them using the "Branded Tracking Link" domain (this is another CNAME you set up in Marketo under Admin--> Email). These tracking links are how Marketo enables you to track engagement with your emails.   Setting Up Secured Domains for Tracking Links instructions - Setting Up Secured Domains for Tracking Links   Do I need to secure my Tracking Links? If your company (likely IT) has implemented HSTS, you WILL need to secure your tracking links for your recipients' email->web page redirect to function correctly. Additional information on HSTS, including how to check if it's been implemented on your domain can be found here: SSL: The HSTS Policy and Your Marketo Subdomains.   HSTS is a web server directive companies may choose to enforce which forces all subsequent requests for resources on that domain to be loaded through HTTPS. This is most common for those in highly regulated industries, such as financial and healthcare institutions. Please note, enforcing HSTS does not also convert Marketo tracking links in emails to HTTPS - that must be done via Marketo Support.   Other Helpful FAQs What is Marketo Secured Domains for Tracking Links? This secures the tracking link domains (which is what makes the URLs appear as HTTPS instead of HTTP) by providing the SSL certificate for each unique domain. Please note tracking links are NOT the same as your SPF/DKIM domain, which is the domain from which your emails are sent., whereas this is the domain located within your emails that tracks click-throughs.   How many domains can I secure with the Secured Domains for Tracking Links? Technically, there is no limit to the number of tracking link domains a customer may have. The base Secured Domains offering included on all subscriptions covers the cost to secure your first tracking link domain; however, if you need more, you may simply add additional domains to your contract a la carte, so you only pay for what you need (in contrast to the previous bundled offering). Contact your Marketo Customer Success Manager for more information.   How is the Secured Domains for Tracking Links product different than the Secured Page Services, SSL for Tracking Links service? Unlike the legacy SSL-only service, Secured Domains not only generates and auto-renews all certificates needed for securing your domains, but provides an exponential layer to what 'secured' entails - it's not just an SSL certificate anymore. For a full explanation of Marketo's Secured Domains offering, and how it differs from just the SSL certificate, please see this Nation Post or check out this Marketo Blog Post about cyber-security and marketing.   What setup/configuration is required before securing my Marketo Tracking Links? You must configure (brand) your CNAMES for Email Tracking links. More information here: Brand Your Tracking Links   Can I secure my tracking links without securing my Marketo landing pages? Technically? Sure. But while secured tracking links have yet to be enforced by email clients, secured landing pages have been enforced by browsers since 2018, which is why we include both in our base bundle. The general public is far more likely to not stick around or enter personal data on an unsecured landing page than they are to not click an unsecured tracking link.   Do I need to provide a TLS/SSL Certificate? No. Secured Domains moves 100% of the SSL ownership to Marketo - all aspects of procuring, managing and renewing certificates is done automatically without human interaction. In fact, we only allow customer-provided certificates on an exception-only basis, OR if you require an Extended Validation (EV) type certificate.   What Certificate Authority issues the certificate(s) for the Marketo’s Secured Domains for Landing Pages product? The certificates are authored by DigiCert.   What type of certificate is provided? We produce a pack of two certificates; The primary certificate uses a P-256 key, is SHA-2/ECDSA signed, and will be presented to browsers that support elliptic curve cryptography (ECC). The secondary or fallback certificate uses an RSA 2048-bit key, is SHA-2/RSA signed, and will be presented to browsers that do not support ECC.   Will my domains be on a shared SSL certificate with other companies? As part of our Secured Domains products, each of your fully qualified domain names will get its own certificate. That means you will not be on a shared certificate with other companies.   Can I provide my own SSL certificate(s) to secure my domains? Not unless it's an Extended Validation (EV) type certificate. Marketo can only automatically renew the certificates we generate to secure your domains.   Are security headers applied to my tracking link domain? Security headers are applied to tracked links in emails that are sent to your leads. The tracking link domain itself (e.g. click.example.com) will not return all security headers. The subdomain itself does not host content and is not intended to be browsed. Marketo Support will not respond to security scans performed on the tracking link domain itself.
View full 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?
View full article
Issue You try to send a sample of an email and receive a notice that the send sample failed.     Solution There are two token-related reasons that Send Sample may fail: You may have an invalid value for a token in your email. If there is an incorrect token value, the send sample will not work. Example: If you have the token for first name written like this {{lead.FirstName:default=Hello}}, when you try to approve the email Marketo will let you know that the token value is incorrect. The correct token value is  {{lead.First Name:default=Hello}}. For this example if you change the token value to {{lead.First Name:default=Hello}}, Marketo will allow you to approve the email and it will allow you to do a send sample. You may have a token in the From or Reply-To line that is not populating with an email address Example: If you have a token in the Reply-To like this one, {{lead.Email Address:default=edit me}}, then the Send Sample using the default will have "edit me" in the Reply-To, which is not an email address.  Marketo cannot send an email without a Reply-To email address, so the Send Sample will fail.   If any of the above does not apply, run the following tests and provide the information to Marketo Support Clone the email in question and test to send as a sample Create a new email and test to send as a sample Send the email via a live campaign or a single flow step to a test lead
View full article
Issue How to confirm ZoomInfo integration is working with Marketo.   Solution First, follow the installation guide: help.zoominfo.com/18441-formcomplete/installation-guide#product-overview To check if its working: Go to Marketing Activities. Navigate to the folder and then click on the Smart Campaign that runs your Form Complete. From the Smart Campaign, click the top navigation menu item, “Results”. Find the most recent “Call Webhook” activity type and double click it. The Activity Details window will pop-up (check your pop-up blocker if it does not).   Inside this window will be what you need to diagnose most problems. The easiest way to know if it worked or did not is that the Response Code should read: 200. This means it was successful in terms of sending and receiving the response in a way that the API accepted it. Anything other than 200 you should lookup with a Google search and investigate. Finally, go to the Lead  Database, and in the quick find search for the unique contact record that submitted the form to find the record that went through the Form Complete Webhook. Double click the right record from the view and that person record will load up. From the top navigation click, “Info” and scroll down till you see the custom fields you created in Step 1 (above). You should see the fields populated if all of the steps were completed successfully.   Who This Solution Applies To Customers using the ZoomInfo Integration      
View full article
Required Profile Permissions for Marketo Synchronization API Enabled Manage Public Documents Manage Public Templates Edit HTML Templates Edit Events Edit Tasks Convert Leads Transfer Lead* Transfer Record* Enable Read/Create/Edit/Delete access on the following required Standard Object Permissions: Opportunities Contacts Leads Accounts Campaigns (if you choose to enable campaign sync) From the Profile Detail page, click Edit and complete the steps in this section.In the old profile layout the following should help: Enable the following Administrative Permissions: API Enabled Manage Public Documents Manage Public Templates Edit HTML Templates Transfer Record * Enable the following General User Permissions: Edit Events Edit Tasks Convert Leads Transfer Lead* Enable Read/Create/Edit/Delete access on the following required Standard Object Permissions: Opportunities Contacts Leads Accounts Campaigns (if you choose to enable campaign sync) Click Save to save your changes and return to the Profile Detail page. Enable Read access on any custom objects that you'd like to sync with Marketo. Marketo only supports syncing of custom objects associated with leads, contacts, and accounts. For merging leads, this profile needs Edit and delete access on the lead object and on all objects (standard and custom) that your Leads and Contacts use.   *Transfer Lead and Transfer Record are optional but may be required if you wish for Marketo to be able to change the owner of a record   You must add each field you want synced to Marketo to your page layout; all other fields will not be synced.  If you use other editions of Salesforce, Marketo will sync down all fields that the sync account has permission to access (whether or not they're in the page layout).    
View full article
What is Marketo’s Marketing Calendar? What are its benefits? What features does Marketing Calendar include? Is it free or do I need to pay for it? How do I get or buy Marketing Calendar? As of our August release: 1 week after our August release How do I know if Marketing Calendar has been turned on? What is the Program Schedule View? Will I need a services package to implement Marketing Calendar? Is this article helpful ? YesNo
View full article
Issue You want to understand how Company IDs work within Marketo and how you can interact with these IDs, particularly when dealing with the Person's Company Object. You want to know: The nature and standard of the Company ID in Marketo. Can the Company ID be checked or modified by users without CRM or API integration? If people belonging to the same company share the same Company ID. How to update the Company Object information via the API for multiple leads associated with the same company? Clarification on which field should be used as the basis for updating Company Object information. Solution Marketo manages Company IDs using two distinct identifiers: Company ID: This is a Marketo-specific identifier that is used to organize the link between companies and people within Marketo. External Company ID: A hidden system field used in non-native company object integrations. The Company ID can be accessed through the {{company.Id}} token, while the External Company ID is not directly viewable in the UI. Note: The Company Object API endpoints are disabled when a native CRM integration is enabled in a Marketo instance. Accessing and modifying Company ID You cannot manipulate the Company ID or External Company ID fields from the Marketo UI. Any interaction or modification of these fields must be done through the Marketo API. Updating Company Object information via API When updating the Company Object for multiple leads belonging to the same company: Use the External Company ID or company ID to update the Company Object. Updating the Company Object with the External Company ID will apply the changes to all leads associated with that company. You can also update Company Object fields using the lead API endpoints. These changes will apply to all leads associated to the company. Steps for updating Company Object Create Company: Use the Marketo API endpoint `{{base_url}}/rest/v1/companies.json` to create a company with the necessary data. Create Person: Use the Marketo API endpoint `{{base_url}}/rest/v1/leads.json` to create a person associated with the company. Field Inheritance: Once a person is linked to a Company Object via the External Company ID, certain fields like Billing City, Address, and Postal Code are inherited from the Company Object and are no longer editable from the UI. Creating Fields on the Company Object: Contact Marketo Support to request the conversion of these person fields to company fields.  
View full article
Issue There are discrepancies in the leads activity logs within Marketo, where the Email Delivered activity timestamp is sometimes recorded a few seconds before the Email Sent activity. This sequencing issue causes confusion for analytics teams, particularly when using external analytics platforms like Tableau, as the logical sequence would typically show that an email is sent before it is delivered. Solution Understanding email statuses and utilizing Campaign Run ID for analytics: The confusion arises from a misunderstanding of how Marketo logs email activities and the meaning behind the statuses Sent and Delivered.   Email Sent Status: In Marketo, when an email status is logged as Sent, it indicates that the email has been considered for sending or queued for sending. The status does not mean the email has been physically sent through the servers but rather is prepared to be sent. The logging of this event happens shortly after the email is queued, which could be almost instantaneous.   Email Delivered Status: The Delivered status is an acknowledgment from the SMTP (Simple Mail Transfer Protocol) infrastructure, signifying that the recipient's email server has accepted the email. This status is logged after the event has occurred and the email has been accepted by the remote server.   It is important to note that while both statuses are recorded after their respective events, they come from different systems within the email delivery process. This can sometimes result in the Delivered status being logged before the Sent status, although such instances should be rare. To correctly analyze and interpret the email activity logs, users should adhere to the following guidelines: Recognize that the timestamps for Sent and Delivered may not always be in the expected order due to the separate systems involved in logging these events. Focus on the Campaign Run ID for analytics purposes. This ID is unique to each campaign run and can be used to accurately reassemble the sequence of events, regardless of the order in which Sent and Delivered statuses are logged.
View full article
Issue Multiple alerts are sent from the same campaign.   Solution Recognize that Send Alert functions at the person level, triggering an alert for each individual in a campaign. Utilize Marketo's reporting to send a consolidated notification: Create an Email or Campaign Performance report. Tailor the report settings for the specific campaign. Schedule the report to be sent after campaign completion. This method provides a summarized notification, avoiding the repetition of alerts per campaign member.   Alternatively, use Send Alert for individual notifications where needed, such as: Alerting a lead owner of a form submission. Triggering personalized alerts for specific lead activities.  
View full article
Issue Files uploaded to Marketo's Design Studio, like PDFs or image files, are assigned an HTTP URL instead of HTTPS. This discrepancy can trigger security warnings in emails, as modern browsers and mail clients expect secure links that match the SSL certificate's domain.   Solution To address this issue, follow these steps: Ensure you have a custom landing page rather than the default domain. See under Admin > Landing Pages. Apply an SSL certificate to any new domains added. Marketo won't do this automatically. You can contact Marketo Support to request an SSL application for your domain. Provide necessary details. After SSL implementation, send test emails to check for proper HTTPS encryption and the absence of security warnings.   By implementing these actions, asset URLs and landing pages in Marketo communications should be secure.
View full article
Issue Learn how to design smart campaigns using triggers and filters within the same campaign. Create a campaign that reacts to several different initiating actions or conditions, such as a change in lead status, form fills, or change in data values. Find out whether triggers and filters can be used together, how to combine them effectively, and how to apply advanced filter logic to achieve the desired workflow.   Solution Marketo allows the combination of triggers and filters within a smart campaign. Triggers are considered as initiating events that start the campaign, while filters are used to further refine the selection of leads based on specific criteria. Triggers are always evaluated with an OR logic, meaning if any trigger event occurs, the campaign will consider it for further action. Filters, on the other hand, can be evaluated using AND logic, OR logic, or advanced logic, depending on the requirements. Steps for smart campaign configuration: Combining triggers and filters: In a smart list within a smart campaign, you can have multiple triggers. Each trigger is treated with OR logic, meaning if any of the triggers occur, the campaign will proceed to evaluate filters. Filters are then applied to further refine which leads or records should move through the campaign flow. By default, without advanced logic, filters are evaluated with AND logic, meaning all filters must be true for a lead to qualify. Using advanced filter logic: Advanced filter logic can be used once you have three or more filters. You cannot use advanced logic to change the inherent OR logic of triggers. Filters can be combined using AND, OR, and other complex logical conditions, but this logic applies only to filters, not to the combination of triggers and filters. Understanding the distinction between triggers and filters: Triggers are based on activities or actions, such as Data Value Changes or Person is Created. Filters are based on properties or criteria of the lead records, such as Product Interest = C or Field A = B. A trigger can only occur once per lead action, whereas filters can continuously apply to lead records based on their properties. Creating complex logic: To create a logic such as (Trigger1 AND Filter1) OR (Trigger2 AND Filter2), you would set up two separate smart campaigns or smart lists, as within a single, smart list, triggers cannot have AND logic between them or between triggers and filters. Troubleshooting smart campaigns: If a smart campaign is not running as expected, review the combination of triggers and filters to ensure the logic is set up correctly. Remember that a trigger must occur for any filters to be evaluated. Verify that the filters are correctly defined to match the leads you intend to target after the trigger event. By understanding and applying these principles, you can effectively manage smart campaigns in Marketo, ensuring that the right leads are targeted with appropriate actions based on both their activities and their attributes.
View full article
Issue Leads were uploaded into Marketo with the wrong opt-in date and time, which also synced with Microsoft Dynamics 365.   Solution To correct the opt-in date and time, do the following. Update information in Marketo. Prepare and upload a corrected list for the leads. Confirm the opt-in field in Marketo is not blocked from updates. CRM Sync The corrected data in Marketo will auto-sync with Dynamics 365. If auto-sync fails, manually update the opt-in dates in the CRM. Additional Steps Check for any automated actions triggered by the wrong data and rectify them If needed. Confirm data accuracy in both systems after updates. Back up data before mass updates to prevent data loss.  
View full article
Summary When attempting to approve snippet error Access Token is Invalid appears. Have the customer sign out and sign back in. Seems maybe they got logged out somehow. Issue When attempting to approve a snippet you receive  "Access Token Is Invalid" error. Solution The error can occur when your internet browser logs you out of Marketo in the background. To resolve, sign back in to Marketo and retry the approval. 
View full article
Issue New leads created through form submissions in Marketo are not being registered by the "Fills Out Form" trigger in associated campaigns. Solution To address this issue: Verify Referrer Value: You'll see a referrer value in the Fills Out Form. Confirm that the referrer value in the Fill Out Form activity aligns with the campaign trigger criteria. Check Configuration Changes: Inspect any recent changes to URLs that may affect form submissions. Communicate these changes to the Marketing Operations team for proper adjustments. Review Campaign Setup: Ensure the campaign is set up to include the specific form and that no filters exclude new leads. By following these steps, you should be able to resolve the issue and have new leads correctly trigger the Fills Out Form activity in Marketo campaigns.
View full article
Issue When attempting to move a folder with a program into a different workspace, the below exception is thrown: Rule is incomplete, '<Field Name> is...' requires value In the below example, the field name is 'New Status ID':   Solution This exception is thrown when a smart list within the Folder contains an incomplete filter. To resolve, you can either: 1. Remove the Smart List filter that is incomplete 2. Set a value for the Smart List filter
View full article
Issue When using Interactive Webinars, if a host changes the layout, previously on-camera speakers must switch on their cameras again. Is there a way to keep the camera always on when you move from one layout to another? Solution This is not supported due to privacy concerns. If a video pod is not present in a layout, the camera is turned off. If a video pod is present in the next layout again, the presenters need to switch on the camera again to consent to their video being shown again to everyone. There however is a workaround to this. A video pod can be placed on the poll pod layout but it can be positioned so that it is behind the poll pod. The size of video pod does not matters on this layout so it can be reduced so that it is completely hidden behind the poll pod. This way the video pod will be hidden and not visible to participants but since the video pod is present, the camera will not be turned off on this layout. On switching to the next layout (Intro), presenters will not need to turn their cameras on. However, they need to be cautious as their video will go live as soon as the intro layout goes live. Additional information on Interactive Webinars can be found here: Best Practices for Interactive Webinars Designing Interactive Webinars  
View full article
Issue You may see the error "Program with name already exists" when saving a program name, and this is because Marketo requires each program name to be unique. There may be a scenario where you are trying to re-name an existing program to correct capitalization. (For example, your program is currently called "Test program" and you want to re-name it to be "Test Program", but you get this error message.)   Solution As a workaround to resolve this: 1) Re-name your program with an extra character at the end, essentially to temporarily make it a different program name 2) After that, re-name the program back to your original desired program name and it will save
View full article
Issue When retrieving result sets from the /rest/v1/activities.json end-point using a Paging Token, the result set returned by the API appears to be less data than what is in the Marketo UI. In this scenario, we're going to explore how and why Paging Tokens work when utilizing them in REST API calls. SCENARIO Say we wanted to grab all 'Send Email' activities (activityType = 6) that have occurred since 2024-04-12T12:00:00Z, and we're planning to pull these activities every two hours, and increment our paging token every two hours prior to making the /activities.json call to obtain the latest data. Current Time Apr 12, 2024, 8:00:00 AM (MST) == 2024-04-12T14:00:00Z What We Want 1. Retrieve all Send Email activities SINCE  Apr 12, 2024, 6:00:00 AM (MST) == 2024-04-12T12:00:00Z We would start by retrieving our Paging Token with the sinceDateTime parameter = 2024-04-12T12:00:00Z: /rest/v1/activities/pagingtoken.json?sinceDatetime=2024-04-12T12:00:00Z Our response would contain the nextPageToken representing the sinceDateTime: { "requestId": "1607c#14884f3e74e", "success": true, "nextPageToken": "RW6ZK46LKV36BMJ2QARX3BFZHQNHRVPPEW4IZVEELI45V2OH6RCA====" } We would then pass that nextPageToken into our GET /rest/v1/activities.json end-point, as well as our activityTypeId = 6 to target all 'Send Email' activities that have occurred since 2024-04-12T12:00:00Z. /rest/v1/activities.json?nextPageToken=RW6ZK46LKV36BMJ2QARX3BFZHQNHRVPPEW4IZVEELI45V2OH6RCA====&activityTypeIds=6 After paging through all of the results (now leveraging the returned nextPageToken from the /activities.json end-point to page through all results), we've returned 15,000 Send Email activities.      PROBLEM We know that, from our Marketing team, that we were expecting ~20,000 email sends since 2024-04-12T12:00:00Z. So why does the result set appear to be missing 5,000 records? Let's examine this further. 'Send Email' activities aren't committed to the Marketo database until the message has successfully been sent from our mail servers. Prior to that, the email is queued, awaiting it's launch to it's receiving mail server. This can present a delay from the time the email is sent, to when the activity is recorded to the Marketo database. For example, say there were two campaigns sending 10K emails each: First Campaign Send: 2024-04-12T12:30:00Z (30 minutes after our sinceDateTime token) Second Campaign Send: 2024-04-12T13:45:00Z (110 minutes after our sinceDateTime token, 10 minutes prior to when the call was made) While the first campaign send is most likely accounted for in the database (Send Email activities have been committed), Campaign #2 is still processing and sending out all 10K emails in the background. For this scenario, Marketo has only committed 5K out of 10K email sends to the database at the time the call was made. Without noticing the missing data, you repeat this process two hours from now, incrementing your sinceDateTime token by two hours as well, assuming you'll get all the new Send Email activities for the past two hours. This would now lead to you missing the 5K Send Email activities that were still being processed, but not yet committed to the database. SOLUTION The nextPagingToken returned in the /activities.json end-point is position based, and can only pull data that has been committed to the Marketo database, which inherently changes as records are being processed. If, for instance, you made the original /activities.json call at (Apr 12, 2024, 8:00:00 AM (MST) == 2024-04-12T14:00:00Z), and used the same sinceDateTime token 5-10 minutes later (Apr 12, 2024, 8:10:00 AM (MST)), you would now notice that campaign #2 has fully finished it's processing AND committed the 'Send Email' activities to the Marketo database with dateTime stamps less than Apr 12, 2024, 8:00:00 AM (MST). So, what's the best way to ensure you're retrieving all the data? Solution #1 Increment your sinceDateTime token based on the MAX(created_at) dateTime returned in the latest result set, rather than incrementing it based on an interval (every two hours). This would help ensure you're not missing records that were processing, but not yet committed to the Marketo database. Solution #2 If the data you're retrieving does not need to be live, we would recommend using the Bulk Extract API to pull this data at a lower frequency (such as twice per day 12AM & 12PM). This would greatly decrease the chances of missing records that weren't committed to the database.
View full article
Summary Learn how to resolve the issue where Marketo only recognizes the first LinkedIn Lead Gen form and does not recognize any additional forms. Issue Marketo only recognizes the first LinkedIn Lead Gen form and does not recognize any additional forms. The problem persists even after disconnecting and reconnecting the LinkedIn account with Marketo. Solution To resolve the issue where Marketo does not recognize multiple LinkedIn Lead Gen forms, follow these steps:   Verify submissions: Ensure that each LinkedIn Lead Gen form has at least one submission. Marketo will not display a form in the dropdown lists for triggers or filters unless it has been filled out at least once.   Preview and test the form: Go to the LinkedIn campaign and use the ad preview feature to fill out the Lead Gen form yourself. This step is necessary for Marketo to recognize and sync the form.   Check for form activity: Once the test submission is complete, check the activity log in Marketo for the test record. Look for the LinkedIn Lead Gen Form Fill activity, which should be present to ensure that the form appears in Marketo dropdowns.   Using Marketo smart list: If you want to check the performance of the form, use a Smart List in Marketo with the filter Filled out LinkedIn Lead Gen Form and set Lead Gen Form Name to any. This will show submissions for all LinkedIn Lead Gen Forms with at least one submission. This filter can also be used in reports to segment people based on form submission activity.   Reauthorize connection: Remember that the authorization for the LinkedIn connection in Marketo is valid for a limited time. To avoid disruptions, set a reminder to re-authorize the connection periodically before it expires.   Additional information: Marketo integrates with LinkedIn Lead Gen forms to capture lead information directly from LinkedIn. Regular monitoring of the LinkedIn connection in Marketo is essential to maintain a seamless integration. By following the above steps, you should be able to resolve issues with Marketo not recognizing multiple LinkedIn Lead Gen forms and ensure all forms are properly synced and can be used within Marketo for lead generation and reporting purposes.  
View full article