Vector
Reo.Dev’s Integration with Vector helps identify more de-anonymized developers.
When you receive a website visitor alert from Vector in your Slack channel, we analyze the message and based on the page visit details, match the profile with an existing anonymous developer in our system.
This triangulation allows you to de-anonymize developers and access their entire activity history.
For instance, if a developer visits a documentation page and performs actions like package manager installation or Docker pulls, we previously recorded these activities under a ReoID due to anonymity. However, with the Reo.Dev and Vector integration, you can now de-anonymize that developer and view their complete activity history.
Integrate Vector with Reo.Dev
Step 1: Head to the Integrations section under Settings
Step 2: Next, click on 'configure' in the ‘3rd Party Tools’ card.
Step 3: Click on ‘Connect’ on the vector card
Step 4: Confirm Vector site pixel installation:
a. Confirm that the Vector site pixel is installed on my website & documentation pages.
b. Confirm that slack alerts for “All Visitors” segment from Vector is turned on. Here’s a guide on Vector <> Slack Integration.
Then, click on next.
Step 5: Connect Slack:
a. Click on connect under slack
b. Click on ‘Allow’
For analyzing Slack alerts and triangulating page visit activities, we require view permissions as shown in the above image.
Once connected successfully, click on 'Next'.
Step 6: Select the Slack channel where you receive notifications from Vector.
This step allows Reo.Dev to read alert data only from that specific channel, triangulate it with developer activity already captured in Reo.Dev, and de-anonymize identified profiles.
Once done, click on Submit.
Note:
Reo.Dev enriches developer profiles with details like Name, Company Name, email address and more using the LinkedIn URL identified by Vector. You can access these developers directly on Reo.Dev’s dashboard. However, in cases where a LinkedIn profile identified by Vector cannot be verified, it will not be enriched or displayed on the Reo.Dev dashboard.
Only those leads surfaced by Vector after the Vector integration is set up on Reo.Dev will be enriched and visible on Reo.Dev's dashboard.
FAQs
How much enrichment can I expect from the Vector and Reo.Dev Integration?
You can expect a noticeable uplift in your total de-anonymized traffic once Vector is connected with Reo.Dev. With our RB2B integration, we've seen anywhere between 10–15% increase in identified visitors. We’re still collecting more data to establish exact benchmarks for Vector Integration, reason being:
Not all profiles that come in via Vector will be de-anonymized because there may be some notifications where the LinkedIn URL is missing or LI URL points to a profile that does not exist.
There could be some irrelevant profiles that do show up. There is one level of filtering that we have where we remove those profiles and we don't add them into the de-anonymization. This is something that is always in progress. As and when we see irrelevant profiles coming, we keep on adding those rules to maintain clean, high quality data.
The way the integration works - We triangulate contacts identified by Vector or RB2B with an FID on Reo by matching the timestamps of notifications from RB2B or Vector with the timestamps recorded for corresponding activities by our JavaScript.
In the case of RB2B, we already have sufficient historical data to determine the reasonable time range between an RB2B notification and Reo’s capture of that activity, allowing us to confidently handle triangulation.
For Vector, we’re still in the data collection phase — once enough activity is captured, we’ll be able to accurately predict the expected enrichment uplift.
When Vector shares a LinkedIn ID, how does Reo.Dev map that LinkedIn ID to an existing contact in Reo.Dev?
When Vector provides a LinkedIn ID, there are three possible mapping scenarios in Reo:
Mapped to an already de-anonymized FID - This is a direct match. If the same activity captured by Vector is also tracked by Reo’s JavaScript, we link them. In this case, Reo’s JS remains the source of truth for activity data.
Mapped to an anonymous FID (and it's perfect match/successful triangulation) - We will only take the LinkedIn ID from the Vector notification and enrich the FID. The activity from Vector notification will not be a part of the enrichment, as that activity would already be tracked by our JS and updated against the FID.
No matching FID found - If the LinkedIn profile doesn’t match any existing FID, we create a new de-anonymized developer profile using the LinkedIn data from Vector and associate it with the single activity detected by Vector.
When will I start seeing this data on Reo.Dev?
You’ll start seeing data in Reo.Dev after 24 hours of setting up the integration.
Last updated
Was this helpful?