Steven_Vanderb3

Hi Deepali,Not all of our subscription levels have the ability to use custom objects. If you do not see that functionality, then it is likely a result of using a test instance and not a fully provisioned instance. You should contact the person that gave you access to your test instance for more in...

I can confirm that those leads that came over with no email address will count against your lead database limit. If you have no way of identifying them to merge them into some existing record or find some other use for them, you'll probably want to delete them.

Support can actually just make a filter for null email fields. We can make a filter for the value of any field the sync user can see in SFDC as far as I know.

Marketo Opportunties can be created using our API Marketo REST APIs: Opportunity Objects » Marketo Developers if you don't have a CRM. Salesforce and Dynamics Opportunties must be created and managed in the CRM. There is no UI ability to do this in Marketo.

That would be the best course of action. Support has access to email logs and can tell you if the alert emails were either bounced/rejected or accepted by your email server.

We do have two types of categories that we use to evaluate the bounces. A Category 1 will set the lead to be Email Suspended temporarily and usually relates to a Spam block. A Category 2 will mean the email address is truly invalid and we will mark the lead as such. You can add Categories as an a...

I don't believe that's available in the UI but if you contact Support and include links to the assets you have questions on, we are able to provide you with that information.

You'll need to troubleshoot with your SFDC Admin the sharing rules and roles set up in your Salesforce instance.

Are you checking how the styling is rendering in a Gmail inbox by chance? Gmail strips the HEAD out of emails for everybody.

It's likely because the record is not visible to the Marketo sync user. If you log in as the sync user and try to view the record, you can determine that. Alternatively, there could be a sync backlog and the record hasn't yet been processed through the sync queue.