Q: Hello, thank you for this amazing deal!
I'd like to see some example use cases.
- A use case scenario demonstrating to what extent the automation will help a digital marketing agency. (multichannel - email, social, seo, gmb, ppc)
- how your platform can help perform audits (possible lead generation usages?)
- comparison to oviond (previously on appsumo - if your platform doesn't include the same level of reporting - an integration with oviond instead of data studio)
- an example report the client could receive (is it automatic and native?) or we it be reliant on data studio.
Thank you, hope it isn't too many questions, I am very interested!
Great question. I was Agency side myself for a while so let's start with why we are doing this.
The most common pain points that I saw and wanted to address was:
- Agencies want to minimise the time spent doing manual labour on data governance, performance analysis and keyword research
- Agencies need to show their clients that they are adding value every month, but don’t currently have an easy way to log activity and report back to clients about issues and solutions they have implemented
- Managing multiple clients and analysing their performance with the Google suite of tools is difficult to do at scale
- Portfolio managers lack adequate top level views of clients that are churn risks due to performance or executional issues
I'll number the discussion points below so that you can ask any follow up questions (As its too long for a single reply)
1. A lot of Agencies have separate (channel) teams that make up a single client account. This leads to a silo of shared learning and no centralised view. We wanted to alleviate this by allowing teams to create their own channel focused KPIs and overall business KPIs (what you are being paid to achieve). The KPI predictions should allow you to start proactive conversations around meeting your targets and getting on the front foot instead of the dreaded 1st day of the month reporting time and you didn’t meet your target. This paired with the Insights feature, which is a combination of Automation Jobs or Anomalies meeting their trigger, will give you a way to track activity and actioned items for that Client.
2. The Automation jobs feature was created so that you have a way of adding things to your report about what’s going on so that you are seen as proactive and the ability to spot things that you just can’t do manually. For example the Google Ads change history Job can be used as an internal compliance check to see that ppc managers are maintaining the accounts as they should. Or if the way a Goal is being tracked has changed in Analytics you get an alert so you don’t have missing data. Agency life is chaotic with competing priorities and a lack of time and we are trying to solve that in ways that address real world problems and relate directly to the retainer fees that you are being paid.
3. Audits will depend whether you have access to the Google Accounts or not. Our plan is to provide an audit capability around Google Analytics configuration as this is useful for onboarding, audits as well as ongoing data hygiene which will support not only better client reporting but our prediction and anomaly detection algorithms. Our approach will predominantly be focused on authenticated data extraction and not public website technical audits. We believe that your Agency can utilise our ML as a selling point rather than the traditional you have too many H1 tags on your site, type emails that most people use for lead gen.
Continuation from above.
4. Managing email alerts from the Google Suite is difficult as most Agencies have a single google account that is added to a clients Ads, Analytics, etc. which all team members utilise. This email address then gets all the alerts and it can be confusing to know which team member the alert is for and when they have actioned it. This is why we created Insights as the centralised feed of that data and provide a Zapier integration so you can push those notifications into your own Project Management tool like Asana, Trello, etc. with bi-directional sync. So if you close the task in Asana we resolve the Insight in Jepto.
5. Oviond looks great but I never wanted to compete with Google Data Studio as we love the direction its going. So we made the decision very early on to have a native Data Studio connector. You can currently pull in all your Insights data and KPIs for native Data Studio chart creation. See here for more info: https://www.jepto.com/integration/data-studio (It’s still waiting final Google approval before being available in the connector list but its working and ready to go). We also built a free GMB Data Studio connector which is currently used by thousands of businesses and agencies world wide. It’s not related to the App, but you can try it out here: https://www.jepto.com/google-my-business-data-studio-connector
6. We had to make the decision if Jepto would be serving Agencies and/or end Clients. We decided that Agencies had so many different reporting needs and we would be spending a lot of engineering effort on something that already exists (Data Studio). Therefore we decided that we would build our App to enhance your existing reports and utilise the rich ecosystem of Data Studio and then you can apply your Jepto data in ways that is relevant for you. This way you are free to create reports in the style and format that you like rather than the way we think you should. Having said that we do provide rich notifications in slack and email so you can see what’s going on.