My name is Sergey and I’m Marketo Admin at Wrike.
Today I will show you one of the cases of how we use Wrike in our Marketing Operations team to reduce the number of routine tasks for each team member.
Here at Wrike we use Marketo and SFDC as a core Marketing and Sales tech stack. Each marketing campaign requires numerous assets to be created, depending on the campaign goals. For instance, a single campaign can include webinar invitations, paid ads in Google, Facebook, LinkedIn, several follow-up email blasts, eGift sendouts and many more.
We create separate campaigns in SFDC for each goal and also the corresponding programs in Marketo, which we then sync together using native Marketo functionality. As we continue to expand the number of advertising campaigns the time spent on asset creation in each system significantly increased. We therefore started to explore ways to reduce manual work and luckily there was already a tool in our org that allowed us to create custom integrations - Wrike Integrate, which allows customers to add Wrike to any existing workflows of any type of business.
After researching the possible workflows for our specific use case, we found the following solution to be the best fit:
New Task (i.e. “Create campaigns for Q3 ABM promotions”) is created in Wrike by the stakeholder using the Marketing Operations request form. We created a template table for such kinds of requests, so the stakeholder must fill in the data for the goals that are supposed to be achieved in this campaign, also the budget and scheduled start date.
Our M.Ops colleague takes the desired campaign structure and creates new rows in Google Sheets, where we store all campaign data. There are formulas added to create proper campaign names based on the campaign type, goal, dates and so on.
The next step is to update our Custom Fields in the source task, we use them as a setup parameters. For example we use multiple webinar platforms to host our virtual events, and for each campaign the provider can be different, so the responsible M.Ops must pick the correct value in the dropdown.
When all the parameters are correctly entered the task status is changed to the new custom status used specifically for this campaign creation workflow. In our case it is called “SFDC/MKT Campaigns In Progress”. The status change action then triggers the recipe in Wrike Integrate, that listens specifically for this activity in Wrike.
After the recipe is triggered, it checks the setup parameters set in Custom Fields, analyses the campaign structure in the Google Sheets, performs multiple data validation steps (i.e. correct campaign name length, if start date is valid, if budget is set correctly and so on) and then creates all assets in Marketo and SFDC using APIs of these tools. If there is an error in any part of the setup, a new comment is added in the related Wrike task by our bot user Mark Ops Bot specifying the details and how to fix it.
In order to maintain consistency between all the newly created programs we use program templates in Marketo for every type of campaign, which makes the creation process as simple as cloning the existing template. Wrike Integrate is also able to update Program Tokens, and we also add some useful data there, such as a stakeholder name, Wrike Task URL and other details which makes finding the responsible person or checking the details of the task far easier, especially if it’s been a while since assets were created.
The final step in this process is to generate the report with all created campaigns/programs, their names, tactics, URLs, UTMs etc. To do that we use the same task that was used for request and add the table with this data below the original task description. After it’s done, Wrike Integrate changes the status of the task to “SFDC/MKT Campaigns Created”, that means that the workflow has been successfully processed without any errors.
The time spent on an average request is now 10x less compared to manual campaign creation, so it was definitely a game changer for us and another successful case of Wrike Integrate implementation in our internal workflows.
If you want to learn more about how we use Wrike internally and especially on what other integration possibilities we have found useful, stay tuned and subscribe to our blog!
Sergey Lebedev Wrike Team member Become a Wrike expert with Wrike Discover