The Tribify Engine coordinates outreach and prioritizes leads across an entire team in order to maximize the value of every minute the team spends building relationships.
This generates an avalanche of data, so every instance of the Tribify Engine features a convenient dashboard that provides a high-level view and serves as a gateway to the Tribify Engine toolbox.
Every instance of the Tribify Engine is a little different! Your instance might have…
- several attached LinkedIn accounts
- several different targeting models
- drop locations for files generated by other systems
- exports to deliver Tribify Engine data to other systems
Here’s an example of a typical Tribify Engine dashboard. See below for a detailed description of each section.
A Profile is an individual contact record. The Tribify Engine accumulates Profile data from every source it touches. Profiles are keyed on their LinkedIn profile ID.
This section summarizes unique Profiles in the Tribify Engine database, across all connected LinkedIn accounts. Remember that more than one Account might be connected to the same LinkedIn profile!
Here’s what the numbers mean:
|Count||Total unique Profiles.|
|Scraped||Profiles that have been scraped, which brings in work & school history and connections as well as endorsed skills.|
|Emails||Profiles with an email address.|
|All Cxns||Profiles directly connected to at least one Tribify Engine Account.|
|Tbfy Reqs||Profiles that have received a connection request generated by the Tribify Engine.|
|Tbfy Cxns||Profiles that have accepted at least one connection request generated by the Tribify Engine.|
|Tbfy Cxn %||The historical success rate of connection requests generated by the Tribify Engine.|
|Other Cxns||Profiles directly connected to at least one Tribify Engine Account that were never issued a connection request by the Tribify Engine.|
|Open Reqs||Profiles with at least one open Tribify Engine generated connection request.|
The Tribify Engine tracks connections between Profiles. Some, like work & school connections, are so numerous that the Tribify Engine can currently only track them in the aggregate. This section is specifically about LinkedIn connections between Profiles.
Note that a Profile may have hundreds or thousands of LinkedIn connections. Only those relevant to your search universe will be represented here. So these metrics describe the network within your network that matters most to you!
We’re always working on adding more and better metrics! For a deeper insight into what these mean, read this gentle introduction to graph theory.
|Count||LinkedIn connections captured between Profiles in the Tribify Engine database.|
|Degree||The average number of LinkedIn connections captured for each connected profile in the database.|
|Density||Total captured connections expressed as a ratio of total connections possible.|
The Tribify Engine database keeps a record of every unique profile attribute it encounters. The Engine assigns tags to these values, which we then use to construct targeting models.
Here’s what we keep track of:
|Companies||We track every company listed in every job on every profile, so long as it has a LinkedIn company page.|
|Degree Specs||A degree specialty, usually a topic of study like law or engineering. The Tribify Engine is smart enough to know that EE, E.E., Elec. Eng., and Electrical Engineering all mean the same thing!|
|Degrees||The Tribify Engine knows that MBA, M.B.A., and Master of Business Administration all describe the same degree!|
|Job Titles||The Tribify Engine does extensive keyword analysis & pattern recognition so we can distinguish jobs by type, level, and keyword!|
|Locations||We track location by city, region, country, and more!|
|Schools||We can focus on individual schools or whole categories (like Service Academies or the Ivy League).|
|Skills||We can distinguish variations of specific skills or group them into broad categories.|
|Tags||These are our tag definitions. It’s easy to create new ones to meet your precision targeting needs!|
These are links to some of the key data repositories that make up your instance of the Tribify Engine.
Some of them are greyed out. The links work, but you won’t have access to the underlying objects. They are for admin use and to support the numbers reported on your Dashboard.
Some of them are not greyed out, and you’re welcome to explore them! Here’s what they are:
|Events||This is your Events master, which drives invitations to LinkedIn events and also supports registration and attendance feedback into your targeting models.|
|Maintenance||Sometimes things don’t line up. For example, what if somebody attends a Zoom event under a different email address than the one in their LinkedIn profile? This sheet lets you correct such issues.|
|Reference||This sheet contains all the detail summarized in the Reference section above. It includes statistics that let you explore your network’s most common attributes. Stand by for surprises!|
|Targets||Defines all Targeting models, which are articulated using tags defined on the Reference sheet described above.|
This section contains a row for each LinkedIn account attached to your instance of the Tribify Engine. Here’s a breakdown of the columns:
|Account||The LinkedIn profileId associated with the account.|
|Profiles||A count of the LinkedIn profiles in the Tribify Engine database associated with this account from all sources.|
|Pxn %||The account’s Penetration Rate. How much of the database does this account’s contacts cover? There will be overlap between accounts, so these numbers will not sum to 100%!|
|d1||First-order connections from all sources (i.e. searches, scrapes, etc.). Note that this number is calculated differently than the Connected metric in the Profiles section. That one is based on profiles with a known connection date, whereas this one is based on reported connection distance. In single-account Tribify Engine instances, expect this number to be larger than the Profiles version.|
|d2||Second-order connections from all sources.|
|d?||Profiles with a connection distance that is either unknown or greater than two.|
|Tbfy Reqs||Total connection requests generated by the Tribify Engine in this account.|
|Tbfy Cxns||Total connections preceded by a Tribify-generated connection request.|
|Tbfy Cxn %||Average success rate of Tribify-generated connection requests.|
|Other Cxns||Total connections not preceded by a Tribify-generated connection request.|
|Open Reqs||Currently open (i.e. not accepted, not withdrawn) connection requests.|
|Profiles||This is a link to the account’s Account Profiles sheet, which calculates these stats and also graphs the account’s performance over time.|
A Targeting Model is similar to what the rest of the marketing world calls a customer persona: it contains a very nuanced description of precisely who you’d like to meet in order to sell your product or service, populate your community, or whatever it is you are doing.
What sets a Tribify Engine Targeting Model apart from a typical customer persona is that it is dynamic. Over time, a Targeting Model learns from experience by observing who registers for and attends your events, buys your product, and generally engages with your offering. So over time, a Targeting Model produces more leads like the people who engage with your offering, and fewer like the ones who don’t.
Targeting Models are defined at the Targets link in the Data section described above. Each Targeting Model defined on your Tribify Instance has its own row in the Targeting Models section. Here’s a breakdown of the columns:
|Target||A name uniquely identifying the Targeting Model on your Tribify Instance.|
|Prospects||A link to the Prospect List associated with this Targeting Model, which ranks your entire database according to its criteria.|
|Feedback||A link to the Feedback Sheet associated with this Targeting Model, where you (or your automation) can update your targeting model as prospects move through key milestones in your sales process.|
The Tribify Engine can be integrated with all kinds of external systems via CSV file transfer. The procedure is the same in every case:
- Generate the file in the external system.
- Optionally rename the file add metadata not included in the file,
- Drop the file into a designated directory.
That’s it! As long as the file is properly formatted and named, the Tribify Engine will ingest it and update the database with its contents.
Propagation Time Alert
If you don’t see an immediate change in your numbers after dropping a file, don’t panic! The file ingestion process process can take a couple of hours.
There is no limit to the integrations we can perform, but two are so common that we include them by default:
- LinkedIn will produce a file with Registrants to a public event, who may or may not have LinkedIn accounts. The Engine will ingest this file, match the Registrants to LinkedIn profiles by email, and indicate any unknown emails on the Data Maintenance sheet described above for manual resolution. This is a great way to flesh out your mailing list!
- Zoom will produce an Attendees file after every event. The Engine will ingest this file, match Attendees by email, and indicate attendance on the Registrant Export. Note that event registration and attendance can also factor into your Targeting Model!
Each data import defined on your Tribify Engine instance is included in this section. Here’s a breakdown of the columns:
|Source||The source system (e.g. LinkedIn, Zoom).|
|Key||The source artifact (e.g. Registrants, Attendees).|
|File Name||Any special coding required for the file name. For example, both the LinkedIn Registrants and Zoom Attendees files should begin with the eventCode defined at the Events link in the Data section described above.|
|Folder||This is a link to the file drop directory. Once you have created and appropriately named the file, just drop it here and it will be automatically ingested!|
Tribify Engine integrations work in both directions. In addition to consuming CSV files, the Engine can also produce them to be consumed by other systems.
By default, the Tribify Engine produces a single export. The Registrants Export identifies prospects who have registered for Events defined on the Events link in the Data section described above, and indicates who actually attended.
Every export defined on your Tribify Instance is represented here. Here’s a breakdown of the columns:
|Export||A name uniquely identifying the Export on your Tribify Instance,|
|Sheet||A link to the Google Sheet containing this Export.|
|CSV||A direct link to this Export’s data in CSV form.|