Publisher Partner Tiers

This article explains why we have tiers of partners, how we categorise partners and what type of support to expect for each tier of partner

Last updated on September 20th, 2021

Why do we have tiers of partnerships?

We have tiers to show customers what partnerships are the highest value and to help us internally prioritize work to deliver the most value to our customers and make informed decisions on what partners will benefit Uberall and our customers the most in the future. 

How do we categorize partners into tiers?

We have a partner scoring matrix against which all prospects and existing Partners are scored. 

Each partner is given a score from 1 - 6 across the following 8 core categories;

  • Total Annual Page Visits
  • Total Annual Unique Visitors
  • Total Annual Growth %
  • Near Me Relevance
  • Network Reach
  • Innovation
  • Technical capabilities
  • Support

What do the scores mean?    

  • Over 30 - Tier 1
  • 20 - 30 - Tier 2
  • Less than 20 - Tier 3


Tier 1
These are our highest value partners which are essential to our business offering. These are the partners we dedicate the most time and resources to. We try to ensure we have the most sophisticated connection to these partners, stay up to date with their roadmaps, work together to run beta programs, proactively propose improvements and customer requests.

Troubleshooting Process
While we aim for full publication on all platforms, we know that isn't always the case when dealing with so many different partners and such a high volume of customer data. We have monthly meetings with most of our Tier 1 partners to discuss operational performance. At these meetings, we will address errors at scale and identify solutions to publication issues at scale. For Tier A customer issues at scale, we will have a shared work document to address ad-hoc publication issues reported through Jira.

Tier 2

These partners tend to be applicable for particular regions or verticals, for the most part, these partners tend to have the highest costs to Uberall. We try to ensure we connect in the most meaningful way at the point of implementation and maintain that connection for the duration of the relationship. We work to resolve bugs that are caused by our end using our established prioritization logic and customer tagging in JIRA. We report bugs on the partner's side through the shared reporting document. 

Troubleshooting Process
We have quarterly meetings with most of our Tier 2 partners to discuss and optimize operational performance.  At these meetings, we will address errors at scale and identify solutions to publication issues at scale.

Tier 3


These partners are, for the most part, extended longtail business directories. These partners provide the least value to our customers and our product and so we dedicate the least technical resources.
We do not work on resolving bugs for these partners and publication issues that are the fault of the partner are escalated by Data Operations for Tier A customers. 


Troubleshooting Process
We do not escalate case-by-case issues for Tier B &C customers. We will send the partner an automated report of all issues which occurred on their channel once a month and request they resolve those issues.


Where to find more information 


Slack - Product will update #product_partner_news slack channel with new implementation announcements or any known issues affecting many locations

ABE - you can see which tier each partner falls into are implemented per partner in the ABE

JIRA  - You can see more granular information about each implementation in the implementation tickets

Was this article helpful?

Save as PDF