Knowledgebase

Sort by:
Summary Marketo-only records must be manually synced, become a member of a default-program, encounter a Salesforce flow step in order to sync with Salesforce. Issue Records are in the Marketo database but are not syncing over to Salesforce automatically like I thought they would. Solution The sync between Marketo and Salesforce is bi-directional. However, in order for a record to be synced, one of the following conditions must be met: The record becomes a member of a program which is synced to a Salesforce campaign. This occurs when the background sync is used to keep members of a Salesforce campaign in sync with a Marketo Program status. This can easily be verified by navigating to the program and looking at the summary view. More information on this feature can be found here: https://docs.marketo.com/display/public/DOCS/Sync+an+SFDC+Campaign+with+a+Program https://docs.marketo.com/display/public/DOCS/SFDC+Sync%3A+Campaign+Sync The record encounters an SFDC flow step. Any time a record encounters a Salesforce related flow step in a smart campaign, this will cause the record to sync with Salesforce. Some of these flow steps have other implied actions, which you can read about here: https://docs.marketo.com/display/public/DOCS/Implied+Salesforce+Actions The record is manually synced to Salesforce through a single-flow action. This is an intentional user action. It can only occur when you find the record in your database or in the people tab of a smart list and select the option from the 'Person Actions' menu. More on how to do this can be found in this document: https://docs.marketo.com/display/public/DOCS/Run+a+Single+Flow+Step+from+a+Smart+List Root Cause Records had not encountered SFDC flow steps, become members of a program synced with a Salesforce campaign and hat not been manually synced to Salesforce. Environment Marketo with the built-in integration with Salesforce
View full article
Marketo has the ability to see and pull data from Salesforce Formula fields, there is however a catch which will be explained in this article.   Everytime the Marketo Sync connects to Salesforce, it will scan records and look at the " SytemModStamp " (salesforce system field) for each one of them. It will compare this value with the stored value, which was pulled at the last scheduled sync. If the values match, Marketo will move on to the next record. If the values are different (new value later date than previous value) , then Marketo will do a compare and contrast of all fields on that record in both systems and update the information as needed.   When a normal non-formula field is updated and changed on a Lead/Contact record in SFDC, the SytemModStamp value is updated. This is how on next sync Marketo knows to do a compare/contrast check and pull updates. Formula fields do not behave the same way. A formula field is calculated based on data in fields called upon in the formula; this means that the formula field calculation itself will not update the SytemModStamp in Salesforce.   Chances are you already have existing records in SFDC and Marketo. If you were to create a formula field today in your instance of SFDC and have it sync down into Marketo, the data calculated for the formula field in SFDC will not come into Marketo right away. The reason for this is, the formula field has created data based on already existing data, this does not result in a SytemModStamp change.   Typically formula fields will be a calculation of data from fields which are somehow related to the lead/contact record. This means that moving forward, any change in the normal field, will result in a SytemModStamp change as well as a recalculation of the formula field. In this case, Marketo will see the updated SytemModStamp due to the normal field change. Marketo will do the compare/contrast excercise and find that the formula field also needs updating.   If you create a formula field in SFDC and would like to have all the historical data for the formula field to come into Marketo, you can force an update on the records in SFDC to update the SytemModStamp. This way, on next sync, Marketo will see the formula data and pull it in. Alternatively, you can simply allow for natural SytemModStamp updates in SFDC to occur which should result in a slow trickle of historical data from SFDC into Marketo for the newly created formula field.   You can only use data from a formula field in Marketo to segment data and filter. If you try to do a change data value, Marketo will accept the change, tries to sync it to Salesforce and fails to update there. Eventually the Salesforce calculated value will come back into Marketo.  
View full article
Article Text 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”   When finished, your Flow will look like this:           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   When finished, your Flow will look like this:           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  
View full article
Issue A landing page is taking a significant time to load. Solution The load time of a landing page is generally due to resources that have a large file size or due to third-party scripts. This can be identified by using tools like https://tools.pingdom.com/ that breaks down the loading time of individual resources and scripts within a landing page. Another way to inspect the loading time of resources and scripts within a landing page is using the network feature of the developer tools in Google Chrome, Firefox, Safari or any other web browser: https://developers.google.com/web/tools/chrome-devtools/network-performance/reference https://developer.mozilla.org/en-US/docs/Tools/Network_Monitor https://developer.apple.com/safari/tools/    
View full article
Issue Links placed into emails by a token are not being tracked and do  not show successful click activity in the lead/person record.     Solution When Marketo sends emails, you can think of building the email in 2 steps: Marketo searches the email code for "http" or "https" and wraps the tracking code around the URL Marketo inserts the values of {{tokens}} into the email.   If the {{token}} value is http://www.domain.com , that would be expected to not track because of the above 2 steps. After the {{token}} value is inserted, Marketo does not go back to wrap tracking code around http/https. The {{token}} doesn't look like a URL when the system applies the tracking code because the tokens don't pull the values in until the next step after. The solution to tracking tokens is to place http:// or https:// on the outside of the token, like such: http:// {{token}} That way, when Marketo builds the email, in step #1, the system recognizes the http and knows it's a URL. Then the tracking is wrapped around the http and the {{token}} as well. Then in step #2, the {{token}} value is inserted into an already-wrapped link. Keep in mind is that if the {{token}} value contains http, but http is on the outside of the {{token}}, the link will break. Let's say the URL you want to insert is http://www.domain.com . You have to move the http:// out in front of the {{token}}, but you don't want to also have it inside the {{token}} as well or your link ends up being http://http://www.domain.com. To get around this, you'll need to remember to take the http:// out of the {{token}} value. {{http://www.domain.com}} would instead be http://{{www.domain.com}}
View full article
Issue You receive the "Subject is empty" error when attempting to approve an email which contains an emoji character in the subject line, and elsewhere in the email, emojis may fail to render. Solution Marketo can render any Unicode character up to 5.2 and any ASCII character, but this does not encompass emojis. The Marketo email editor will strip out any unsupported symbols. This is because we cannot guarantee the consistency of their appearance across platforms, as not all clients can render all emoji. Marketo only supports the text symbols that are generally then converted into emoji's by the recipient client or operating system. The basic symbols in a list such as https://www.copypastecharacter.com/symbols should work, as they are ASCII characters and not reliant on extra encoding. These are a set of accepted text symbols that will universally work on all clients and many will convert them to emoji. Just highlight the symbol from  https://www.copypastecharacter.com/symbols, copy and paste it into your email. Alternately, you can work around this by q-encoding the emoji in UTF-8 format, which will render a string of code to add to your subject line. This code tells the email client to render the desired emoji. All you need to do is copy your desired emoji and run it through a Unicode to UTF-8 translation tool, such as https://tools.bluestatedigital.com/kb/subject-line-assistant. As an example, say you want to send a Happy Birthday email to a lead. You could copy the  (birthday cake) emoji and run it through a translator to yield the code "=?utf-8?Q?=F0=9F=8E=82?=" Entering this code in your subject line without the quotation marks will render the emoji on the client's end, and render it in the design most compatible with their device/browser. With any email design, it's always important to test before a live send to confirm it appears the way that you expect it to.
View full article
1. Navigate to  https://status.adobe.com     2. Click Manage Subscriptions                               3. Sign in using your Adobe credentials or click Create an Account to log in                                       4. Select Experience Cloud drop-down                               5. Select Adobe Marketo Engage                                       6. Select a business service(s)                                     Prior to selecting a regional location(s), you will want to identify what data center and pod/server your instance is located in. Yo u can deduce this information by looking at the URL of your instance. The CNAME = the pod or server your instance is on.         The example above indicates that this instance is in our Ashburn data center on pod A. This user would select the regional location Marketo Ashburn, and then pod ABA, as shown below.    The abbreviations for all of our data centers are as follows:  ab = Ashburn  sj = San Jose  sn = Sydney  lon = London    NOTE: This method can also be used to identify what Real Time Personalization (RTP) pod/server your instance is in.    7. Select regional location(s) and event type(s)                             8. Select the environment(s) you would like to subscribe to and click Continue                                     9. Review your subscription preferences and click Done  
View full article
Issue Issue Description Even though the Success Path Analyzer and the RCE report may be looking at the same thing (e.g the conversions from one stage to another), the numbers in Success Path Analyzer and RCE Conversion Ratio will not match. Solution Issue Resolution Success Path Analyzer is telling you that records are flowing from one stage to another, for example a record moving from Cold List to MQL, the conversion rate will display the rate from this stage to the next stage. If you look at the RCE Conversion Ratio, this is not tracking just the conversion from the first stage on the Success Path Analyzer to the second but instead this tracks all the conversions from this stage to another (eg. Cold List to MQL, Cold List to Attempting). Thus resulting in a much higher conversion percentage as the RCE is not bound to the green path from the Success Path Analyzer. Who This Solution Applies To Customers using RCE, Customers using Success Path Analyzer
View full article
Issue You want to use Slack with webhooks to be able to customize the integration a bit more than using it as a Launchpoint service. Solution We will assume you have already created your App within the Slack API page  we will cover everything after that here. 1) Make sure you are logged in so you can access your App through the Slack API page. 2) Select your App: 3) From here you will want to select the "Incoming Webhooks" from underneath "Features": 4) Use the on/off toggle to the right of the title "Activate Incoming Webhooks"   5) Select the "Add New Webhook to Workspace" button to create a new URL that we will use for our webhook within Marketo: 6) Select where you want to post, either at a specific user or channel:   7) Now we are directed back to the page we were one, hit the copy button next to the Webhook URL to copy the URL as we will need it for a later step. 😎 Login to your Marketo instance and navigate to the Admin section. 9) Select Webhooks 10) Select Create Webhook. For the following fields assign the appropriate values: Webhook Name*        =        What ever you want to name Description                 =        A description of what the webhook is used for URL*                           =        Here is where we paste the URL we copied before Request Type*            =        POST Template                     =       This is the information you want to send to your slack channel/user It should in the following format:                                              payload={"text": "DEVELOPER SITE ALERT: {{lead.First Name:default=edit me}} {{lead.Company:default=edit me}},                                                            {{lead.Email Address:default=no email address}}" } Request Encoding Token     =  None (You can change this if you want) Response Type                    =  None 11) Click create and now we are ready to call our webhook and send necessary data to our users in Slack!  
View full article
Issue Description You have a record in Marketo that is a Contact in SFDC, and the record fails to sync with the error " INSUFFICIENT_ACCESS_OR_READONLY: insufficient access rights on object id." Issue Resolution This error can occur if the Record Type ID field is not updated in Marketo when the SFDC Lead is converted to a Contact.  If the Record Type ID value displayed in Marketo is not valid for Contacts, the sync will fail with the error, " INSUFFICIENT_ACCESS_OR_READONLY: insufficient access rights on object id ." To resolve this, you can update the Record Type ID in Marketo with the correct value from Salesforce, or you can delete the value from Marketo and allow the sync to write the correct value from Salesforce.
View full article
Issue You already have a Marketo connected to an instance of Salesforce and want to switch to a different instance of SFDC.     Solution This is not possible. Once you have connected your Marketo instance to an instance of SFDC, that connection cannot be changed. If you want to connect Marketo to a different instance of SFDC, you would need to contact your Customer Success Manager to have a new Marketo instance provisioned.        
View full article
Issue Description You want to know how long changing a segment takes. Issue Resolution Segment changes are treated like any other activity that is being queued up and processed to be run. Segment changes have an extremely low priority and can sit in the queue waiting for other activities to finish, so you should wait for some time after making the change before you reference the segment elsewhere.
View full article
Issue How to use the Web Page, Referrer URL, or Query String constraints to specify web page when using one form on multiple pages. Solution Use the appropriate constraint to specify which page the form is on when using a "Fills Out Form" trigger or "Filled Out Form" filter in a Smart List. There are three options: Web Page Referrer URL Query String   Web Page This constraint is designed for Marketo Landing Pages. If you have one form on multiple pages, and were attempting to specify a Marketo Landing Page, then you would use Web Page.  If you use Web Page, your value is the Landing Page asset name, such as "Global Contact Form Page". Or if the page is local to a program, the name format would be [program name].[landing page name]   Referrer URL This constraint is designed for external, non-Marketo pages. If the form you have is embedded on an external page, the value you would enter would be the URL of the page. This constraint is very picky about the values entered. Say the form is on http://www.pages.domain.com/contact-us.html . Only the following 2 options would function: Referrer URL - is - http://www.pages.domain.com/contact-us.html Referrer URL - contains - www.pages.domain.com/contact-us   By using "is", the exact value must match. When using "contains" a smaller portion of the whole can be used. Even "contains" /contact-us would have worked successfully, but the less specific the value is the more other pages could qualify depending on the use case. Generally, "contains" is advised with a unique portion of the URL because there can often be querystrings on URLs that would then not satisfy the "is" constraint.   Querystrings If the form is on a page, and the page has a querystring, such as: http://www.pages.domain.com/contact-us.html?product=new-stuff , then the form submission activity on the Marketo record would have a new field in the Detail called Query Parameters. ( Querystring, Query String, Query Parameters are all the same thing.) If you set up direct links to the Page with unique querystrings, then you would be able to use the Querystring constraint and use values from the querystring in the trigger/filter form fillout campaign.
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 After updating a Segmentation, a person now qualifies for a different segment than previous, but there is no change segmentation activity in the log for that person. Solution This is expected when the segmentation is recalculated. The process will not write change values as this is seen as initial value in this newly approved segment. Any subsequent changes to the records will write a Change Segment activity
View full article
Included in this article Overview Sometimes the data you see in your CRM system doesn't match what you see inside of Marketo. This document will show you the common reasons to help troubleshoot where the problem could be coming from. What Causes Data Mismatch The vast majority of data mismatches result from sync backlogs, so much of this doc will go over sync backlogs. However, since there are a number of other ways this can happen, here are the most common ones to watch out for: Sync delays from backlog Incorrect set up of campaigns to add leads to SFDC Campaigns Sync user permissions Field Value Validation Field Type Validation Sync Delays from Backlog Whenever an update is made to a record, it generates a System Modification Time Stamp, referred to as a SysModStamp. The creation of a SysModStamp on a field that is visible to the sync user will queue the record to be resynced. Whether the update is made on the Marketo side or on the CRM side, it will trigger the record to be resynced to update the information on the other end through the regular Marketo to CRM sync cycle. When large numbers of updates are made like from a field value changing, then large numbers of records are altered, causing new SysModStamps on those records. This in turn results in large numbers of lead record updates that need to be resynced between Marketo and your CRM. The sync of leads flows at the rate of approximately 10,000 records per hour. If you've updated 10,000 records at once, you can expect the sync of that data to take roughly an hour to complete. If you've updated 20,000 records at once, you can expect the sync of that data to take roughly two hours to complete, and so on. Thousands of updates are synced over in just one API call as opposed to making a single API call for each individual update. Updates synced between Marketo and your CRM through the sync cycle occur in batches—large groups of updates made all at once to allow the data to be transferred more efficiently. That means 10,000 updates to the Lead Object, 10,000 updates to the Contact Object, then 10,000 updates to the Account Object, all within one sync cycle. The sync cycle won’t let one Object dominate an entire sync cycle with large numbers of updates. Any updates over 10,000 will wait until the next sync cycle. Checking for the backlog Long sync cycles are an indication that there are a lot of updates being made. To check when did the last sync happened 1. Go to Admin 2. Go to integration for your CRM (e.g. Salesforce) in the tree on left 3. Go to the top right corner to see the information of Last Synced. Compare the time shown there to the current time. If it's a long time difference, you've probably got a significant backlog of updates waiting to sync. How do you fix it? Stop making more updates. Once the records are queued up to sync between Marketo and your CRM, there's no way to cut it off and stop it from going through the sync. The data will sync through, but essentially you'll have to just wait for it. If you can stop making continued updates until after the backlog has cleared, you'll be helping it to clear faster. Campaign to add leads to SFDC  Campaign set up incorrectly There can also be cases when you are pushing leads to SFDC Campaigns via Marketo Programs or Smart Campaigns. If you have a flow action where you enter an incorrect campaign name or the corresponding status, the leads flowing through this campaign will have issues while syncing. If you've synced the lead from Marketo to the SFDC Campaign but accidentally synced it to the wrong one, you'll have a data mismatch there. Ensure that you have the campaigns with correct names and statuses Sync user permissions Sometimes a lead won’t sync to CRM because the SFDC sync user doesn’t has permissions enabled to allow the Marketo sync user access to it. Ask your CRM Admin to update the permissions so as to allow Marketo sync user access to the record. Field Value Validation If there’s a validation in your CRM on certain fields, and the field value in Marketo doesn’t qualify for the validation, the lead would not sync.You'll see "FIELD_CUSTOM_VALIDATION_EXCEPTION" error messages, which are your indication that this is where the problems are coming from. For example: Let’s say there’s a validation in Salesforce to accept on “CA” as a value for the field “Country”, and Marketo field has it’s value as “Canada”. The lead would not sync to SFDC. To resolve this, ensure that field value aligns with the validation in SFDC. Field Type Validation Field types must be compatible between Marketo and Salesforce. If the field types are different in Marketo vs CRM, it won't be able to sync properly. For example: If the field in SFDC has the type of “Float” and field in Marketo is “Score”, then they aren't compatible and won’t sync. To resolve, ensure that the fields have similar or compatible types in Marketo and CRM
View full article
Issue Description You would like to pull a report of all the non marketable records that you have in Marketo. Issue Resolution You can do this via a Smart list: Use the Any filter in the smart list. Filters: Black Listed = true Unsubscribed = true Marketing Suspended = true Email Invalid = true Email Address is empty This smart list will pull all the people that fall into the blocked leads list.
View full article
Issue Description An Email with only emoji in the subject line is displaying "Subject is empty" error and is not approving, or emoji fail to render elsewhere in the email. Issue Resolution If the subject line only consists of emoji, consider adding text. The Email Editor was not designed to insert emoji. However some have been able to insert emoji from outside sources. Those with the most success are inserting UTF-8 encoded emoticons. This specific encoded emoticon can be inserted (copy/paste) through a 3rd party website, located with a general web search: "UTF-8 emoticons/emoji". If the inserted emoji has a different encoding, it may fail to render in the Email Editor, and it may fail to render upon delivery as well. Rendering upon delivery will be reliant on the recipient server. If the emoji is considered invalid, then the 'diamond with question mark' character may remain. Alternatively, b asic symbols could be used instead of emoji, as they are ASCII characters and not reliant on extra encoding. 3rd party sites, identified with a websearch: "ASCII symbols", can be a resource. Another option can be q-encoding the emoji in UTF-8 format to render a string of code that can be used. This code tells the email client to render the desired emoji. To q-encode, copy and paste the desired emoji through a Unicode to UTF-8 translation tool, such as https://tools.bluestatedigital.com/kb/subject-line-assistant ​and then insert the translated code.
View full article
  NOTE -  Only authorized support contacts from your organization can submit support cases. To tell if you are an authorized support contact or not, access the Support Tab and select Create Case.  If you are not an authorized contact, you will receive the below screen.  If there is available space you can select the green button and add yourself as a support contact. If there are no open available support contact slots, the green button will not appear, and you will need to contact the support admin for your account.       1. Go to Support.     2.  Click My Case Management       3. Click on +Create A Case       4. Enter a Subject to see suggested articles on the problem. Select an article to open a new tab. Select the + if you would like to see the full subject of the article first.       6. Didn't find the help you needed? Enter your information into the required fields. Click Submit.     Great! You've submitted a case. A support rep will reach out to you shortly.
View full article
Issue Description The Issue When using the Filter 'Member of SFDC Campaign' in the Smart List and checking the people tab to see which records are qualified, this message occurs: Could not evaluate rule 1 (SFDC Campaign 'Campaign Name' not found)  Note: it may state could not evaluate rule # - # can be any number, if the filter is number 5.  # will equal 5 Issue Resolution The Fix Ensure the that the SFDC Campaign being referenced in the Smart List is an ACTIVE campaign The Why This error occurs due to the SFDC Campaign not being an active campaign in SFDC. You may be wondering "then why can I select the SFDC campaign in the drop down?" This is because the Smart List Filter specifically 'Member of SFDC Campaign' similar to 'Has Opportunity' filter reference a backend table in Marketo. This backend table is updated when a SFDC Campaign is removed or renamed. Therefore, Marketo does not directly perform an API call to check if the campaign is selectable, but rather uses the backend table as reference. One way to check in Marketo if the SFDC Campaign is active is to check the 'Added to SFDC Campaign' Trigger in a Smart Campaign's Smart List as that dropdown will only show active campaigns. Who This Solution Applies To Customers integrated with Salesforce
View full article