This is an evolving document which outlines our current implementation process, and how we work together throughout partnership. We welcome your feedback, reflections and suggestions.

Best Practice

We have been fortunate to work with exceptional customers who have delivered positive ROI ahead of schedule. All those organisations have had dedicated individuals who take ownership of the Permutive relationship, and actively manage deployment. By carefully reviewing the implementation plan, co-ordinating internal resource, sharing successes and pre-empting challenges they have fast-tracked deployment and delivered exceptional results. Towards this end, we strongly recommend that you dedicate one individual to managing the Permutive relationship and being the main POC day-to-day.

Preparing for Implementation

To prepare for your implementation, we work closely with you to understand your technical requirements. Your CSM will co-ordinate with you to setup each of the following:

Allocate Dev Resource

You should set aside dev resource to deploy Permutive. This includes setting up Permutive code, deploying on test sites, deploying on live sites, making corrections and changes, optimising and re-arrange code. In our experience this process takes between 1 and 4 weeks.

Decide on the Data Collected On Each Pageview
Follow the steps outlined in this doc and this doc to prepare your pageview event schema. This is a pre-requisite to us preparing your custom Permutive JS tag.

Technical Implementation Call

To understand your implementation needs, and how these will be prioritised, we suggest a call with the main commercial POC and technical lead. From this we can put together a technical implementation plan. A suggested agenda for that meeting is below:

  • Websites and platforms going live
  • Media formats being sold e.g. display/ video/ native
  • Integrations e.g. Ad-Servers, DSPs, SSPs
  • Sending data to your own internal database
  • Recognising logged in/ registered users
  • Other integrations and add-ons e.g. IBM Watson, Third-party Data
  • Header Bidding wrapper

With all this technical information, and the priorities agreed in the kick-off meeting, we can put together your detailed implementation plan.

Kick-Off Meeting

To agree goals, and how these will be prioritised and measured, we suggest a kick-off meeting with all key stakeholders. This should include everyone who has been involved in the commercial decision for this partnership.

In our experience, the most successful implementations focus on delivering reliable monthly recurring revenue (MRR) from Permutive in the first 3 - 6 months. Having achieved this, and optimised the revenue stream, we can work together to explore additional opportunities later in the year. This kick-off meeting is vital to achieving this focus, so everyone can work together to deliver on your organisation's goals.

 A suggested agenda for that meeting is below:

  • Our Approach. Our goals and values, and how we see this partnership
  • Context. Your current set-up, how you generate revenue
  • Why Permutive? What you're excited about in this partnership, and your concerns
  • Goals. Your revenue goals, and wider business goals
  • 6 Month Plan. Prioritising goals to agree a strategy to deliver your revenue goals
  • Opportunities. Ways you might generate additional revenue from Permutive
  • Working Together. How we can make this partnership successful

Implementation Plan

The aim of the implementation plan is to achieve your objectives for the first 3 months. This project plan uses a RACI model to describe the tasks involved, and attribute responsibility to individuals.

The plan will be written by your Customer Success Manager, and we suggest that the main day-to-day POC in your organisation signs off on the plan. We recommend having a kick-off meeting and full technical implementation discussions (as above) before committing to an implementation plan.

Business As Usual

Once you have signed off on the implementation plan, you can begin implementation. This doc outlines the technical integration process, and this doc outlines the non-technical integration process.

Your CSM will take responsibility for managing the implementation plan, and co-ordinating individuals for each task. During this time, your CSM will work closely with the main day-to-day POC in your organisation to manage the implementation plan. We will agree the structure of this in the kick-off meeting, for example monthly review meetings and weekly 30 minute phone-calls.

QBR

The aim of each QBR is to reflect on progress towards your goals and agree priorities for the next 3 months. Much like the kick-off meeting, this is an opportunity to meet in person and reflect on progress. The agenda covers progress, your goals, opportunities, working together, our roadmap and anything additional which you would like to cover. As always, we value an open and direct approach, so please be as forthright as possible.

The meeting will be led by your Customer Success Manager. We suggest that it is supported by the main day-to-day POC in your organisation, and that all your key stakeholders are included.

In advance of this meeting, the CSM will evaluate your progress and reflect on your priorities and potential opportunities. With this understanding we hope that the meeting is an opportunity to objectively evaluate progress, and agree on next steps. To prepare effectively for this, we suggest that the CSM works closely with you to measure results, ask questions and broaden their understanding.




Did this answer your question?