Connect Adobe Marketo Engage to Crush
Give Crush governed access to Adobe Marketo Engage’s 118 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Adobe Marketo Engage to Crush in four steps
Admins approve the server once. Everyone in Crush then gets it through the same governed connection.
- 1
Add Adobe Marketo Engage to Runlayer
Adobe Marketo Engage isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.
Adding a connector manually - 2
Connect Crush to Runlayer
Users add the Runlayer Plugin to Crush by following Runlayer’s setup guide. Crush reaches Adobe Marketo Engage’s 118 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Crush setup guide - 3
Sign in to Adobe Marketo Engage
Sign in the way Adobe Marketo Engage requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Adobe Marketo Engage from Crush
Adobe Marketo Engage’s approved tools appear in Crush. Every call is checked against policy and recorded.
Tools
118 Adobe Marketo Engage tools in Crush
Runlayer policy decides which of these Crush users can call.
Activate smart campaign
Activate a smart campaign to start processing leads.
Add field set
Add a field set (field group) to a form.
Add field to form
Add a new field to a form.
Add field visibility rule
Add visibility rules to a form field.
Add flow step
Add a flow step to a smart campaign at the specified index.
Add flow step choice
Add a conditional choice branch to an existing flow step, so the step can do different things for different leads ("if the lead is in California send email A, otherwise send email B").
Add leads to list
Add existing leads to a static list (list membership).
Add rich text field
Add a rich text element to a form.
Control
What Runlayer can see and stop in Crush
Some controls apply to every client at the gateway. Others depend on what Crush exposes to Runlayer.
Gateway policy (available)
Every Adobe Marketo Engage call from Crush passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Crush as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Crush yet, so control happens at the gateway.
Frequently asked questions
Connect more