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

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 Aggregating/summing two score fields Issue You have two new score fields (for example: 'Implicit score' and 'explicit score') and you're wondering if there's a way to sum/aggregate these scores together for all records within Marketo. Solution To aggregate different score values together within Marketo, you should first create a third 'sum' field meant to capture the aggregate of the two scores. (Example: 'sum score') Now, we have 3 scores: Explicit Score, Implicit Score, and a Sum Score SOLUTION First, setup the scoring smart campaigns for implicit and explicit score as you normally would. Once those scoring programs are setup, add the sum score field to the flow of each respective campaign, increasing that score by the same interval that you increase the implicit or explicit score by. This should allow the scores to aggregate over time. Example 1 "Implicit Scoring campaign: Trigger: Visits web page 'x' Flow: 1. Change Score [Implicit score] Change: +5 2. Change Score [Sum score] Change: +5 Explicit Scoring campaign: Trigger: Fills out form 'y' Flow: 1. Change Score [Explicit score] Change +10 2. Change Score [Sum score] Change +10 Final result if a record runs through both campaigns > Implicit score: 5, Explicit score: 10, Sum score: 15" In the above example, the sum score flow step is simply added to each respective explicit/implicit scoring campaign, with the same change interval applied. Once applied to all relevant scoring programs in the instance, the sum score should continue aggregating the two scores into the sum score field. If you're increasing both explicit and implicit scores within one campaign instead of separating out by score type, you could also accomplish this with the same logic and instead adding the summed score interval within that same flow, for example: Example 2 "Scoring campaign: Trigger: Person is created Flow: 1. Change Score [Implicit score] Change: +3 2. Change Score [Explicit score] Change: +4 3. Change Score [Sum score] Change: +7 Result > Implicit: 3, Explicit: 4, Sum: 7" -------------------------------------------------------------------- Potential Alternative solutions: 1. Have your SFDC/CRM Admin create a workflow within the CRM which sums the two fields as they sync. This requires the score fields in question to be synced to the CRM. 2. Call a webhook, which will keep the aggregate in line with the individuals each time it's called. This would be a custom webhook implementation that Support cannot assist with. Sources for alternative solutions: How to sum Lead Scores in one aggregate score field Add two Scores in Marketo

Summary How to see all the historical Support cases created for Marketo Issue How to see all the Marketo Support cases, attachments, and comments related to your historical support cases Environment Support Portal Solution Authorized Contacts can see the cases that they personally created/own, and the Support Admins can access the all cases on the entitlement from within the Support portal. Below is a community article with additional information and instructions: Managing your Support Cases

Issue Customers may run into limitations with Webhook providers or other third party REST services that require their fields are an integer type field. This may present issues with those values being inputted to Marketo (and other systems) accurately if a record has a value outside of the integer value limitation range: -2147483647 to 2147483647 Environment Marketo/Third Party REST/Webhook Providers Solution There is no way to increase/modify the integer value limitations on the Marketo side. This is not a Marketo product limitation, it's the defined constraints of Integer data types. If you're running into issues with values from a third party/webhook provider falling outside of the limitation range, this will present issues with the field value being accurately logged in Marketo. In this scenario, it's worth checking with the third party/webhook provider to see if they have any flexibility around which field types they can allow (for example, String or Float type fields have less limitations and will allow for larger or smaller numbers outside of the -2147483647 to 2147483647 range). For a full overview of Marketo field limitations, you can visit the below article: Marketo Field Limits by Field Type

Issue After going through a modification of a text field type from 'Text' to 'String', the field is no longer available as a filter for smartlists. Don't worry, the field is not gone - it is just temporarly unavailable. Solution Changing the field type from one type to another is a database intensive operation and in some cases where the field values are widely populated across your database records, this can cause the filter to be unavailable until the operation is completed in full. The time it takes for the field filter to become available may vary and it can take up to ~30 hours sometimes until the field filter is available again after the type of the field has been changed.

Issue Executing a GET API call to retrieve a list of available activity types in the target instance using the '/rest/v1/activities/types.json' endpoint, resolves with an unexpected attribute name for a field with the display name ID in the context of Marketo Custom Objects. An example of that may be a Marketo Custom Object with the following name: '3 to be', as can be shown in the image below: One of the '3 to be' Marketo custom object fields name is 'ID'. (highlighted in red). When performing a GET API call using the '/rest/v1/activities/types.json' endpoint, you will be getting a list of available activity types in the target instance, along with associated metadata of each type, however for a Marketo custom object with an ID field name, you may see it returns back with a slightly different name, in this case, it would be returning the following output for my test Marketo Custom Object activity: { "id": 100019, "name": "Add to 3 to be", "primaryAttribute": { "name": "3 to be ObjRef", "dataType": "integer" }, "attributes": [ { "name": "3 To Be Person Id", "dataType": "integer" }, { "name": "ID (3)", "dataType": "string" }, { "name": "Linkfield4", "dataType": "string" } ] } ], Here's an image of what it may look like when making the call using POSTMAN: In fact, the character in the brackets next to the ID field represents the very first character of your Marketo Custom Object name. Environment Customers who have Marketo Custom Objects where one of the custom object fields is named 'ID'. Solution If this is interrupting your business, you may want to select a different name for the ID field under your Marketo Custom Object. (ie. ID number, Transaction ID etc.) Root Cause This behavior is expected and is a result of the 'ID' field being a unique field in the context of Marketo custom objects world and while it may be possible to create a Marketo Custom Object field with the name 'ID', it may be better to give it a distinct name that will be better describing what kind of ID field it is.

Issue When editing the expiration date for a user in Admin by completely removing the expiration date set to null and clicking save. The change is not saved, and the expiration date remain. Environment Expired Date for user Expiration Date Changing the expire date to never in Admin Solution There are two options: 1. Change the expiration date to a date in the future. 2. Delete the user in Admin and recreate the user again and set the expiration to never. *Please note that if option 2 is selected, the history of the user is will be lost and this cannot be retrieved. Root Cause This is a design limitation as it is expected for the user with an expiration date to be deleted from the Marketo Instance after the expiration date has been reached.

Issue Per our developer page: https://developers.marketo.com/rest-api/assets/programs/#update, it is possible to update tags on your existing program When updating a program tag within an existing program, you may encounter an error below given the tag and its values are correct. {"code": "709","message": "Required tags are mandatory"}]} Environment Any API clients when performing the Web Service API Solution The workaround is to have the tag updated via the UI. Root Cause "Updating tags is a destructive operation." Any attempt to update the tags of a program must include valid values for all of the required tags for a program. Unless the 'specific' tag type you are working on is the only required tag type in the instance, then that is possible to update it using the API. Otherwise, you'll encounter the error above as it is a system behaviour.

Issue When adding new IP Address to the IP Restrictions list on Admin > Login Settings > IP Restrictions, you receive this error message: "Your current IP address (XXX.XXX.XXX.XXX) cannot be blocked." Environment Admin IP Restrictions Login Solution Ensure that you have Admin Access to the Marketo instance and that you have logged into the Marketo instance via one of the IP Addresses listed on the IP Restrictions list. Root Cause User logging into the instance with an IP Address not on the IP Restrictions list.

Summary duplicate records with the same email across lead partitions can be affected by uploaded custom object activity Issue System not separating lead partitions for custom object imports Uploading custom object activity affects duplicate records across partitions Custom Object activity import writing to the most recently updated record regardless of partition Solution Use the following workaround: Run an update on the records that should be affected by the custom object activities import. This will make sure they are the most recently updated records among the duplicates Root Cause Normally when you do a list import, it would import into the one partition, whatever partition the list is located in and only impact the record in that one instance. But when you import a Custom Object, it's able the see ALL the records across ALL the partitions. If there are duplicate records, it just looks to see which one was updated most recently and grabs that one for the list import. So if you have lead record in A with Add to Custom Object already completed and you re-import again but the lead record in B has been updated more recently and has NOT had the custom object added to it, you get the duplicate "Add to Custom Object" activity. Environment Multiple lead partitions with duplicate records across them Custom Object activity import

Summary This method can be used when moving a CNAME from an old instance to a new instance. Often at times, when changing to a new instance, this question can come around, and ones would wonder how to do it or a solution on how to do it. This steps will show you the two phases which I will explain below. (Note: This would need to be done before the old instance deactivated) Issue A CNAME needs to be moved from an old instance to a new instance Solution NOTE: You cannot have the same CNAME in two different instances (Pointing to two instances, e.g. cname1.company.com pointing to instance1.mktoweb.com and instance2.mktoweb.com) Key terms: CNAME 1 = Initial cname in the old instance CNAME 2 = Additional cname created in the old instance INSTANCE1 = Old instance (Instance Name) INSTANCE2 = New instance (Instance Name) Phase 1: --------------- 1. Create an additional CNAME (a replacement CNAME) which you would want to swap as the default in the second step. CNAME 1 > INSTANCE1 (Default) <Existing CNAME in the Marketo Admin > Landing Pages section> CNAME 2 > INSTANCE1 This would be the additional CNAME created for the replacement. 2. Swap the default with the replacement CNAME you just created in step 1 and set this CNAME1 as a domain alias in the old instance. CNAME 1 > INSTANCE1 A domain alias in the old instance. CNAME 2 > INSTANCE1 (Default) ————————————————————————————————————————————————————————————————— Phase 2: --------------- ** Transition might not be smooth during the cutover. 🙂 (The Landing page links might get some interruption during the cutover) During the Cutover (Before the old instance deactivated) : 1. [Your Action] - To remove the CNAME1 which is a domain alias in the old instance (INSTANCE1) 2. [Your Action (IT Team)] - To create CNAME1 as a domain alias in the new instance (INSTANCE2). (During this time the link to old landing pages will be broken) 3. [You need to raise a support ticket to enable SSL for CNAME1 for the new instance (INSTANCE2). If you have any questions, please contact Marketo Engage Support at https://support.marketo.com. Environment Production/Sandbox

Summary Creating many-to-many relationships with Marketo custom objects requires an intermediary object with one link to a Lead or Company and another link to a secondary custom object. Here's how to solve the problem of the secondary custom object not showing up to be selected as the linked object. Issue Creating a many-to-many or N:N custom object structure such that a lead or company can be associated with multiple custom objects and a custom object can be associated with multiple leads or companies at the same time. When adding a link to the secondary custom object, that secondary object is not list as an available linked object. Solution If you find that the custom object you'd like to link to is not list in the "Link Object" list, there are two things two check: The secondary CO must be approved. The secondary CO must not have any link type fields. Since it's not possible to change a link field once a custom object is approved, if you already have link fields, the only solution is discard the secondary custom object and create a new one. Recreate the custom object without link fields. Then, in the intermediary object, the target object will show up as an available link object. More detail can be found at: Understanding Marketo Custom Objects Add Marketo Custom Object Link Fields - Create a Link Field for a Many-to-Many Structure Root Cause The secondary custom object type is not approved. - or - The secondary custom object type is approved type and has link fields. Environment Marketo Custom Objects Many to Many Relationship - N:N Link Fields

Note: Once you have migrated to Admin Console, you can manage your support cases through the feature provided in the Admin Console Platform. To learn more, visit: https://experienceleague.adobe.com/docs/customer-one/using/home.html. Once you have submitted a case to Marketo support, we provide a simple way of staying connected to your case and the cases submitted from your company through the Marketo Support Portal. You can access the support portal through your Marketo instance by selecting Community in the top right corner: This is a article attached image You can also access the support portal directly at https://support.marketo.com and login with your Marketo credentials (login and password). This will not work for users with SSO. Once you are in the support portal you can Create a Case for Marketo Support or you can also review any cases that are open and being worked on by support or review your case history. Navigate to My Case management: This is a article attached image From the My Cases navigation you can access the following case views: This is a article attached image My Recent Cases* - Cases that you have opened in the past 30 days All Company Recent Cases* - Cases that any authorized support contact has opened in the past 30 days My Open Cases – Cases created by you that are being triaged by Support and pending Support’s response and are more than 30 days old My Closed Cases – Cases that were created by you and are now closed My Awaiting Fix Cases – Cases that were created by you where Marketo is developing a fix which will be implemented at a later date All Company Closed Cases – Cases that were created by you or your colleagues that are now closed All Company Open Cases - All open cases submitted for the account Company Awaiting Fix Cases – Cases that were created by you or your colleagues where Marketo is developing a fix which will be implemented at a later date Management Escalations - Escalations opened by you or your colleagues Survey Cases - Surveys that are available for you to fill out after a case is closed *Cases that have been opened for more than 30 days will move from Recent cases to Open cases To view specific case details, click a case number. This is a article attached image From the Case Details, you can perform the following: Close your Case - Select the "My Case is Resolved" button to close your case Add Comments - Provide additional comments to support or respond to a Support question Add Attachment - Provide any screenshots or documents that will help illustrate the issue you are reporting If your case has been closed there are two options available to you. Reopen - You can reopen your case if you are not satisfied with the case resolution by adding a comment in the case. Case Survey - Once your case has closed, please consider offering feedback on the level of Support you received.

Overview SSO Authentication Updating SSO Credentials Tips SSO Only Login Wait to disable the existing certificate Overview Marketo’s Single Sign On (SSO) feature allows your company to use your own company’s SSO service to authenticate your login into your Marketo instance. Your initial setup of the SSO is covered in the documentation here. You may need to change your SSO authentication settings after the initial setup. This document will show you the process on how to do so. SSO Authentication The Identity Provider (IdP) you use will provide you with your SSO authentication credentials and security certificate. Marketo uses this information to validate your login from your IdP, so these credentials come from your IdP. Updating SSO Credentials Once you have retrieved the new security certificate, you can enter it into Marketo. 1. Under Admin click on Single Sign-On. 2. Select Edit in the SAML Settings 3. Enter your Issuer ID, Entity ID, select the User ID Location and click Browse. 4. Select your Identity Provider Certificate file. 5. Click Save. Tips There are a couple things to watch out for when changing your SSO certificate. Here’s a couple tips to avoid trouble along the way. SSO Only Login If your company uses SSO for login, you’ll have an optional setting to restrict login access to your Marketo instance to SSO logins only. This prevents users from logging in directly, forcing the use of SSO. You can check for this setting under Admin > Login Settings These settings do allow the creation of a special User Role that can bypass the SSO restriction. However, sometimes as people come and go within the company, the users enabled with that User Role could no longer be available. TIP: Before changing your SSO certificate, create a new user utilizing this User Role that bypasses the SSO requirement. If something goes wrong while setting up the new certificate, you’ll be glad you have a back door into the Marketo instance! Wait to disable the existing certificate Your IdP will issue a new certificate, but what if something goes wrong while entering the new information into Marketo? TIP: Get the new certificate and set it up in Marketo before you fully disable the existing certificate within your IdP on their side. If something happens to the new certificate, you’ll be glad you have the do-over available and can switch back to the existing certificate that still works!

Issue The email was sent from an engagement program or email program where Recipient Time Zone was enabled, however, emails sent to several leads were not sent based on their time zone. Solution If the time zone calculation for the affected leads falls under the conditions mentioned in https://docs.marketo.com/display/public/DOCS/Understanding+Recipient+Time+Zone, then check in [Admin > Field Management] if the Person Time Zone field is hidden. If this field is hidden, then this would be the reason as this field is where the Person's Time Zone is stored for when it is calculated and is used to determine the Recipient Time Zone for sending emails.

Issue In an instance where there are multiple workspaces, when creating a new email and right-clicking on a Marketo Starter Template to send a sample email, an error is displayed: Access Denied This error occurs even though the user has all permissions to Access Design Studio and all permissions to Access Marketing Activities. This includes the 'Run Single Flow Action' permission which is required for sending sample emails: "You must have the Access Database - Run Single Flow Actions permission to send sample emails." https://docs.marketo.com/display/public/DOCS/Send+a+Sample+Email Solution This error can occur if the user does not have access to the Default workspace. To solve this, the user must be provided with access to the Default workspace in [Admin > Users & Roles]

Issue When I go to the Support area of Nation, I do not have full access to all the areas and tools. Solution Our system is specific about how you need to access the Support Portal before we can authorize you to use it. The proper steps to take for us to authorize, and for you to submit cases, are as follows: Log into your instance Click the Community tile (step 1 image) Click Support in the top banner (step 2 image) Click Submit a Case option (step 3 image) Choose from top options depending on what you need to do (step 4 image) Create a case, Manage authorized contacts, edit your Info Simply going straight to the nation.marketo.com will not have the desired result. You must access the Support Portal from your instance by using these steps so that our system recognizes you properly. If this is your first time following these steps, your view of Step 3 will be different- not to worry, as that will be updated for you manually. Step 1 Step 2 Step 3 Step 4 If you experience issues, please email marketocares@marketo.com

Issue Issue Description API Only user is not appearing when creating a service in [Admin > LaunchPoint] Solution Issue Resolution It is highly likely that the reason why the API user was not appearing because it did not have "API Only" ticked. This can be checked in [Admin > Users & Roles > User > Edit User]. However, this cannot be modified once the API user is created, so in order for the API user to appear in LaunchPoint, "API Only" must be ticked when the API user is created. Reference: Create an API Only User Role Who This Solution Applies To Admin users

Issue Issue Description When any link within an Email is clicked, the user is redirected to the wrong page. Solution Issue Resolution This can occur when Branded Tracking Links have been incorrectly configured and the user is being redirected to the fallback page. The following checks should be conducted: 1. Ensure the correct Branding Domain is listed in Admin > Email > Branding Domains. 2. Ensure your IT team have set a CNAME record to redirect from your Branding Domain to your Marketo Tracking Link. (e.g.mkto-****.com) Who This Solution Applies To Customers using Branding Domains

Issue Issue Description The user role has all the permissions to Design Studio, but whenever trying to preview an email, a limited access message is displayed: "You do not have sufficient privileges to perform this action" Solution Issue Resolution The user role must have permission to 'Access Database'. The full access to Database is not needed, just the main access by selecting 'Access Database' and unchecking everything else underneath. The reason for this permission is that, when previewing emails, you are able to select to preview an email as a specific lead. In order for this to happen, users will need access to leads.

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Company Fields Appear in Lead Object "Describe" API Call

Aggregating Two Score Fields

See Past Marketo Support Cases & Comments

Can Marketo Increase The Max Integer Value Limit of 2147483647?

Custom field is missing as a filter after changing the field type

Get Activity Types via API returns a character wrapped in brackets for a Marketo Custom Object field named ID

Changing the expiration for a user to never

API Error 709 When Updating Tags of an Existing Marketo Program

Restrict Marketo Logins Based on IP Error

system not separating lead partitions for custom objects

Moving A CNAME From An Old Instance To A New Instance

I can't add a link from one custom object to another.

Managing your Support Cases

Changing your Single Sign On Certificate

Email was not sent based on Recipient Time Zone

Unable to send sample email from Marketo Starter Template

Support Portal Access Issues

API Only User Is Not Appearing When Creating a Service In Admin > LaunchPoint

Email Links Aren't Going to Right Location

Limited Access Message Displayed When Previewing Email