Currently the Change the Default From Email and From Label an Admin-only function. It'd be great if, as an Admin, I could set these as defaults for my whole instance and all users (one step further would be to make them conditional to the channel tags). Alternatively, have a way for individual users to set this for themselves as default other than their details in ‘My account’? This will prevent some mistakes and save effort of having to update the values on each new email created.
... View more
Use Case: Vendors or internal employees who manage Ad services or others who may present a security risk by giving them
Issue: Current "Access Event Partners" either does not work or is limited.
The current "Access Event Partners - Gives users access to LaunchPoint in Admin*" is limited or does not work depending on the service. While this role correctly lets them only view LaunchPoint, this role lets them see every single LaunchPoint, and they are unable to authorize services - this was the point of using this role, to have a vendor authorize a service through their LinkedIn / Google Account. A recent example was Google Ads, where a vendor needs to authorize the Google Account, but received this error (which Marketo Support had no comment on): "Limited Access: You do not have sufficient privileges to perform this action."
This makes the LaunchPoint only Access Events Role limited.
1. Change Access Event Partners to be able to authorize services, or have this up as a role option.
2. Have Access Event Partners able to select which LaunchPoint services this Role can access. This is the most ideal: Give access to a specific LaunchPoint, and whether they can authorize, change, delete, etc.
This documentation also does not describe what the nature of Access Event Partners even means. So far, it has seemed "able to login, and view a LaunchPoint".
... View more
The current default setting for the Root Block Elements in Email is set to "<p>" and Landing Pages is set to "<div>". This is problematic for folks that are new to Marketo and didn't elect for, or aren't aware of, this setting.
1) It behaves like a "ghost in the machine" whenever a user uses the Rich Text Editor to modify an editable area which can produce unexpected results based on how an email is coded to handle this.
2) <p> elements in email display different from browser to browser and are not an industry standard root block element (<div> would be much better even). This is a functional issue that can "break" email layouts. 3) It assumes that content is going to be some kind of text in Email using the <p> element which is problematic for non-text elements inside an editable area -- while assuming that content is going to be some kind of block in Landing Pages using the <div> element which is problematic for text element editable areas (ex. <h1 class="mktoText" id="edit_h1" mktoName="headline 1">...</h1>).
Rather than setting the defaults to a value (<p>,<div>) and having the end-user discover this default setting by way of an error (which is perceived to be a Marketo issue b/c it's the OotB default setting), reversing the defaults to "None" would provide a more common-sense starting point and create the perception that the ability to add Root Block Elements is a feature that's built-in and ready-when-you-are rather than something you've got to discover in frustration.
PROPOSED: Change the default setting for both EM and LP to "None".
Admin > Email > Edit Text Editor Settings
... View more