Your Achievements

0% to

Next /

to gain points, level up, and earn exciting badges like the new !

View All Badges

Open Alert Bar

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?

Issue My SFDC production instance is undergoing Instance Refresh Maintenance in SFDC. Will this impact the SFDC and Marketo sync? Salesforce Article: Help And Training Community Solution Provided the org ID of your SFDC environment stays the same, it will remain connected to your Marketo instance. As best practice, double check with your SFDC team that all of your SFDC records will retain their unique IDs after the refresh. After the refresh occurs, double check that the Marketo connection in Marketo (under Admin > Salesforce) is intact.

Issue Email won't be approved due to too many custom tokens Solution Sometimes when approving an email with a large number of of tokens, the following error message will appear: 'The number of custom tokens in the email exceeds the limit ' This is a article attached image This means that you have too many custom tokens in the email and that if you wish to approve the email, you will need to remove one or more of your custom tokens in the email. Its important to note that this only applies to custom tokens, which are tokens based on a custom field in Marketo. This means that while you will be allowed to add more of the standard tokens to the email and approve it, you will not be allowed to go beyond the 40 custom token limit we have in place for the non-standard tokens. Here you will find all the standard tokens in Marketo

Issue You receive a page with the error "Cannot get email content" when visiting View as Webpage link in email. Solution The view as webpage link is tied to the original email asset when it was sent. Occasionally customers will say they're receiving an error message when visiting the link like so: This is a article attached image There are multiple reasons this can happen: The email was a sample send of a draft of an email that no longer exists. It was discarded, or approved. The email asset was deleted You tried to use the view as webpage token from MSI. Root Cause This issue occurs when the visit webpage link is trying to refer to an email or email version that no longer exists either because it was deleted, replaced or approved.

Summary If you're using the Bulk Custom Object Import API to push records to a Marketo custom object (and you're importing separate files that have duplicates across the files) -- the records will not be deduped on the custom object if multiple imports are pushed at the same time. Issue If you are using a Bulk Custom Object Import API third party service to push records to a custom object (and multiple files, containing duplicates across those files are being imported to the Marketo custom object in a similar time window) -- the records will not be deduped on the custom object, even if the dedupe field value is matched. This is because two concurrent imports can be processed at the same time if they are pushed close together. More information can be found here. "A maximum of 2 jobs are processed at the same time. A maximum of 10 jobs are allowed in the queue at any given time (including the 2 currently being processed)." Solution In this scenario, the third-party App/API service provider that is making the bulk import calls must be consulted to ensure that separate files containing duplicate records aren't being imported to a Custom Object at the same time (or close together times). Once the calls are spaced out adequately so there aren't concurrent imports running containing duplicate records in separate import files, the custom object will dedupe as expected based on the designated dedupe fields. More on dedupe fields can be found here: "Dedupe fields can be used to retrieve, update, or delete custom objects. Every custom object definition must contain at least one (and no more than three) dedupe fields." In Summary, while Marketo does deduplicate on custom object records at import based on the dedupe field(s), it cannot dedupe when concurrent imports are being processed at the same time with duplicates in the separate files (for example: file 1 has dupe A while file 2 has dupe B). If all the duplicates are in the same file, however, Marketo can dedupe within that file as its imported to the custom object. Root Cause Concurrent Custom Object imports running at the same time: when this occurs, the two files being imported concurrently don't have time to check against each other to dedupe based on the configured dedupe field.

Issue You receive the following error: "Ouch! 500 Error Something went wrong. We monitor this sort of thing, but if you are an authorized support contact, you should create a support ticket." Solution This can happen because of temporary network issues. Try out the following troubleshooting steps. 1. Clear Browser Cache 2. Try a different browser 3. Try a different device 4. Try a different internet connect (Hotspot/Tether from mobile) If you still have any issue after trying all these steps, please contact Marketo Support for further assistance.

Issue Importing programs from one Marketo instance to another doesn't bring program membership with the program Solution There is not a direct way to import the program membership. However this can still be identified by exporting the original program membership from the first instance to a CSV file. This file can then be imported to a static list in the new instance to identify these records.Then the records can be processed either manually or by batch campaign to update the campaign membership status.

Issue What happens when you enable "Send all Tout emails in my team through this server connection" within the SMTP Server settings on ToutApp.com. Solution When you select "Send all Tout emails in my team through this server connection" within the Tout admin panel, this will provide the option to all standard users to either choose to use the ToutApp Email Servers or your company's own Email servers. If you decide to share the SMTP Settings with the team, t is recommended that you have your IT team setup a dedicated STMP/Email account to use as the Custom SMTP Credentials. Note: Each user can choose to either use the Tout servers or the configured & shared SMTP server. It is not applied automatically to all users.

Issue You would like to have a new lead created in SFDC after every form submission regardless of whether the contact/lead already exists. Solution When you use the "sync lead", assign the person to lead queue explicitly, that will create a new lead since contacts cannot be assigned to queues. However, this is going to create a lot of duplicates in your database unless your salespeople are converting/merging these leads correctly. Furthermore, these new leads will have no campaign history, no interesting moments, no score. It's better to use an "Inbound sales rep campaign" in SFDC and attach the person to it using an "add to SFDC campaign" flow step. Campaigns can contain leads and contacts and can have workflows assigned to them.

Issue How to use a script token to calculate and populate the number of years since a given date. Solution This can be achieved by using a velocity (email script) token: #set( $defaultTimeZone = $date.getTimeZone().getTimeZone("America/New_York") ) #set( $defaultLocale = $date.getLocale() ) #set( $calNow = $date.getCalendar() ) #set( $ret = $calNow.setTimeZone($defaultTimeZone) ) #set( $calConst = $field.in($calNow) ) #set( $ISO8601 = "yyyy-MM-dd'T'HH:mm:ss" ) #set( $ISO8601DateOnly = "yyyy-MM-dd" ) #set( $calJoinDate = $convert.toCalendar( $convert.parseDate( $lead.JoinDate, $ISO8601DateOnly, $defaultLocale, $defaultTimeZone ) ) ) #set( $differenceInYears = $date.difference($calJoinDate,$calNow ).getYears() ) #set( $friendlyLabel = $display.plural($convert.toInteger($differenceInYears),"year") ) You joined us ${differenceInYears} ${friendlyLabel} ago! Where $lead.JoinDate is the joining date. More at http://blog.teknkl.com/velocity-days-and-weeks/

Issue "Currency" type fields are rounding off their value. For example, if you enter the value as 8092384905, Marketo is automatically rounding it to 809239000. Solution This is an expected behavior. TThe currency field type in MySQL is considered to be a Float field and MySQL will automatically round the values in our current database structure. As a work around for this, change the field type to "string" . Since standard fields type cannot be changed, we suggest that you create a new custom field of type "String" to use instead of the standard field..

Issue Description Getting error "Salesforce 551 unauthorized bounce" in ToutApp Issue Resolution - Head on over to your Salesforce instance and login. - Once you're logged in, head over to "Setup" > "Email" > "My Email to Salesforce" - In the "My Email to Salesforce" page, head over to the "My Acceptable Email Addresses" section and ensure the all the addresses you use are listed in here: - Just below "My Acceptable Email Addresses" you can set your email logging settings to how you would like them to enter your SFDC. - Save your settings. Who This Solution Applies To ToutApp customers Is this article helpful ? YesNo

Issue Description How is syndication ID set up while setting up a referral offer Issue Resolution For a referrer to be given credit they must have a Marketo Syndication ID assigned. This can be done manually (directly on the lead record) or via the social campaigns' Offer Details > Fulfillment Goal > should be set to Referred Sign-Ups. Once you set that up, the referrer will get issued a "syndication id" and be part of that social campaign's participant's list.

Summary This article explains why certain Company fields show up on the Person/Lead Object when you do a describe API call to Marketo. Issue When making the Describe call on the Lead object in Marketo (/rest/v1/leads/describe.json), several Company object fields are returned along with the Lead object fields. Environment Marketo REST API Solution This is expected behavior. Users can utilize the Describe Leads call to retrieve a full list of the fields available for interaction via the REST API. Several areas within Marketo treat custom Company fields as though they were on the Person/Lead object. For example if you were doing a Bulk Import, you can target the Company and Person/Lead fields and you have the ability to update Company field values as if you were changing it manually on a Person record in the UI. Root Cause This is expected behavior, due to how the Describe call retrieves all

Summary Customers may face errors referencing Segmentations when importing programs between instances. Issue Program import fails giving an error message like the example below: "Marketo encountered an error while importing Nurture Program: EXAMPLE - Acquisition NUR B2B [SMB] FY24 - TEST Why: The Segmentation_Type_1003 field exists in the following objects: Person What to do now: Create a field named Segmentation_Type_1003 in the Person object." Environment Marketing Activities Import Program Solution The simplest solution would be to temporarily remove the Segmentation references from the child assets (Smart Campaigns, Smart Lists, etc.) that currently exist in the importing Program within the source instance. Once the import succeeds, references to the Segmentations can be re-added to the source (as well as the destination, if needed) instance's Program's assets.

Summary Flow step choice condition for "Person was Deleted from SFDC" with 'in past' "7 days" causes campaign failure Issue This flow step choice type causes a campaign failure because it is not supported. This is expected behavior. Solution Customers have to use Member of Smart List as indirection for the desired filter condition. i.e. Create a new Smart List with the "Deleted from SFDC" filter. Then change this failing flow step choice to use 'Member of Smart List' with the Smart List just created. Example flow step:

Issue Changing From address on multiple email assets at once instead of one-by-one by hand. Solution You can use program/folder tokens as the from address, and then change the token. Once the token changes it will update the assets using the token. For any pre-existing emails, updates in bulk could be made through a API call to the Marketo API endpoint - http://developers.marketo.com/rest-api/assets/emails/#create_and_update.

Summary Mismatch between "Added to [custom object]" and "Has [custom object]" filters for a SFDC Custom object Issue You build a Smart List for "Added to [custom object]" for your SFDC Custom object and you notice the number of records qualifying is lower than expected. The "Has [custom object]" filter pulls more records, however, and matches what you see in SFDC. Environment SFDC/Marketo Solution This is expected behavior if you have records that were already associated to the SFDC Custom object before they were pushed to Marketo. If you have records that were already associated to the SFDC Custom object before they initially synced to Marketo, those records would not have an "Added to [SFDC Custom Object]" activity on their record in Marketo, which means they would not qualify for the "Was added to [SFDC Custom Object] Smart List filter" In this scenario, it is recommended to use the "Has [SFDC Custom Object]" filter to get the accurate numbers, as this should include all Marketo records that are associated to the Custom Object, even if they were added to it prior to being synced and created in Marketo. Root Cause Records already being associated to the SFDC Custom object before they were initially synced to Marketo.

Article Text Included in this article: Navigate to the Clickstream module How is Visit Duration Caluclated 00:00 Visit Duration Single page viewed Session timed out Navigate to the Clickstream module Go to the Visitors page Click on a visitor to find the Clickstream module in the bottom right How is Visit Duration Caluclated When a visitor visits a website being tracked by an RTP campaign, it records clicks in the Clickstream module in the RTP platform. Clicking on a visitor allows you to view their viewing information in the Customer Journey section, including: Links clicked Time stamp of each link click Total visit duration Visit duration is calculated by subtracting the first time stamp from the last time stamp. In other words: visit duration = last time stamp - first time stamp. See the image above for an example of this calculation. 00:00 Visit Duration Single page viewed Both RTP and Google Analytics rely on clicks to determine visit duration. This means that if a visitor only views a single page, neither RTP or GA can track when the visitor leaves the page, since there is only the initial time stamp without a time stamp to mark the exit from the page. The visit duration for viewers that didn't view more than one page during the session is recorded at 00:00 since it cannot be calculated. Session timed out Another way that a visit duration can be recorded as 00:00 is if a visitor's session times out. By default, a session will end after 15 minutes of inactivity. For example, if a visitor stays on a page without making any clicks for 25 minutes (perhaps they are reading an article or watching a long video), that session will time out and be recorded with a duration of 00:00. If the visitor finally makes a click after the 25 minutes of inactivity, a new session will begin. In Google Analytics, the session timeout can be customized to be longer or shorter than the default 15 minutes.

Article Text Included in this Article: Overview Checking for Segment Matches Reasons for not Matching Typos Non-exact Matches Overview Using segments, you can target specific organizations by using the Named Accounts attribute in the segment editor. With this attribute, you can select all organizations in a Named Account List or by manually selecting organizations. However sometimes we see one of those organizations visiting the website but it doesn't match the segment, even though it is included in the segment list. Checking for Segment Matches If a list was created manually, it's possible the organization wasn't included in the segment list in the first place. To check: Go to the Organizations tab Use the search bar to search the name of the organization in question If the organization was entered in the list correctly, it will be found through the search. If it does not appear in the search results, there are two issues that are likely to have arisen. Reasons for not Matching Typos Luckily, typos are easy to fix. Simply edit the organization's name to match the spelling you wanted it to take on. Non-exact Matches Even if an organization is spelled correctly, it will still not match the organization listed in the segment if the names aren't exactly the same. It is very common for companies to have different names for their organization. To fix these non-exact matches, you'll have to be clever about how you name your organizations. In RTP, an important character to know is the wildcard character, represented by an asterisk (*). A wildcard character will match with any character or sequence of characters For example, the string "Salesforce*" will match all three of the above spellings ("Salesforce.com", "Salesforce.com Inc.", and "Salesforce Ltd") because they all begin with "Salesforce". For more examples on how to use wildcard characters, follow this document: RTP Glossary - Marketo Docs However, you must be careful using wildcards characters, because you could potentially match organizations that you didn't intend to match. For instance, the string "Salesforce*" will not only match the three examples above, but also a company named "Salesforce Finance", a completely different company.

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Top Blocklists - What You Need to Know

SFDC Production Instance Refresh

Email won't be approved due to too many custom tokens

"Cannot get email content" message when visiting View as Webpage link in email.

Bulk Custom Object Import API: records not deduping when being added to a custom object

Troubleshooting Ouch! 500 Error

Importing Program Status from One Marketo Instance to Another

ToutApp Custom SMTP Team Settings and How They Work

Creating a New SFDC Lead with Every Form Submission

Use Email Script Token to Calculate Number of Years Based on a Date Field

Currency Type Field Is Rounding Off Its Value

Edit schedule email in ToutApp

ToutApp: Salesforce 551 unauthorized bounce

Setting up a Syndication ID for a social campaigns

Company Fields Appear in Lead Object "Describe" API Call

Error During Program Import

Flow step choice condition for "Person was Deleted from SFDC" with 'in past' "7 days" causes campaign failure

Changing from Address on Multiple Email Assets at Once

Mismatch between "Added to [custom object]" and "Has [custom object]" filters

Web Personalization (RTP) - How Visit Duration is Calculated in RTP

Troubleshooting Web Personalization (RTP) - Segment not Matching Organizations Visiting the Website