Request a Campaign in a Different Workspace

[Caitlin_Poliksa]

I have a "request a campaign" in one workspace calling on a campaign in another workspace...will it work?

[Anonymous]

Hi Edward, 

It seems to be pretty legit.

We tested the requestCampaign field for:

• custom tool that searches old automation system's data and sets requestCampaign field in MKTO
• enabling some staff to request campaigns from Netsuite (they have a saved search and just set the requestCampaign field)
• dynamically setting the requestCampaign field in a hidden webform field
• requesting a campaign that lives in another workspace

We're moving forward with the strategy if it helps. 😃 

[Anonymous]

Definitely using this. Awesome solution.

[Caitlin_Poliksa]

Hi all! So, I found a differnt solution that worked for us.
Esentially I have global Contact Us form that would change the lead partition when a certain action took place. I think created camaigns in the other workspaces that listened for the workspace change then would request the proper campaign.

[Edward_Masson]

Mark P,
how is your testing going regarding your solution above?

[Anonymous]

Mark's suggestion makes sense. It is simple to implement and very flexible.

Answering your quesion: "Sharing Assets Between Workspaces"

http://community.marketo.com/MarketoArticle?id=kA050000000KyxDCAS

[Anonymous]

Hi Caitlin,  I've run into the same thing and think there may be a 3rd option. 

Rather than using the 'request campaign' option across workspaces, I'm looking at using a custom field and 'Change Data Value'  to solve the problem.

Example: Workspace 1 contains the campaign you would like to ultimately request from Workspace 2.  For ease of explanation, lets call the campaign that lives in workspace 1 'send to sales'. 

Create a custom field called 'reqCampaign' 

Within workspace 2, rather than using 'Request Campaign' in the flow, use 'Change Data Value'  and set the 'reqCampaign' field to 'workspace1.sendtosales'.   

Create a Smart Campaign in Workspace 1 that listens for the reqCampaign field to get set to 'workspace1.sendtosales' and in the flow use Request Campaign on the 'send to sales' campaign.  

I haven't fully vetted this option but my team is just about to start testing this solution. It seems like it could allow for a fairly dynamic solution. 

 **The workspaces would most likely need access to the same partitions to make the setup reliable. 

hope it makes sense!

[Caitlin_Poliksa]

how would you share a program or smart campaign across workspaces? And moving to the default, does that make it accessible to all?

[Anonymous]

Moving the campaign to the default workspace would be an option. Sharing across workspaces would be an alternative.