Club logo as player headshot causes incorrect tagging

💻 Environment/Context

  • External groups
  • Clubs
  • Player profiles
  • Logos

 

In order for you to create external groups, the External groups > Can view page and Can create permission should be enabled on your account.

If you're unable to follow any of the steps below, kindly reach out to your admin or refer to the Account Type Permissions Overview article for more information.

 

 

 

❓ Issue/Question

  • Why are certain clubs, created as player profiles with the club logo set as the headshot, getting tagged in collections and videos where they don't actually appear? We've noticed several clubs getting tagged despite their logo not being present in the content.

 

👌 Resolution/Answer

Player profiles should be reserved for real athletes, since they depend on facial recognition. For clubs and teams, use External Groups instead. These use a separate detection pipeline built around logo and keyword recognition, rather than facial matching, so tagging works reliably.

  • Two ways to fix this going forward:
    • Option A: Recreate the club as an External Group instead of a player profile. This uses the correct logo and keyword recognition pipeline instead of relying on facial detection.
    • Option B: If the goal is for a team to get tagged automatically whenever one of its players appears, add the team as an associated tag on that player's profile. That way, whenever the player is detected, the team gets tagged along with them, and the content can also be filtered by team.

 

🥚 Cause

  • Player profiles are built for facial recognition: the system matches a person's headshot against faces detected in the media. When a club logo is used as the headshot instead of a real person's photo, there's no face to detect, so facial recognition can't run at all.

 

🔖 Notes