Shared Experiences

Common experiences between user (seller) and contact (prospect) like same company, school, city, etc.

The Shared Experiences insight provides information about common experiences or connections between a user (seller) and a contact (prospect), such as working at the same company, living in the same city, attending the same school, or the prospect's previous company being a customer of the user's company. This insight requires both the user ID and contact ID, which can be either their LinkedIn URL or email address.

🚧

Note: the only current available parameters for generate-insights are contactEmail and contactLinkedinUrl.

• The system will pass back an array of insights, ranked by relevance.
• The below documentation still accurately covers our schema, and demonstrates what might exist in that array.
• Soon, you'll be able to specify certain insight types in your API request. Coming Q3 2024.

Retrieving Shared Experiences Insight

To retrieve the Shared Experiences insight using the Autobound Insights API, you need to make a POST request to the /generate-insights endpoint with the appropriate parameters.

Python

import requests

url = 'https://api.autobound.ai/api/external/generate-insights/v1.0.0'
headers = {
    'X-API-KEY': 'YOUR-API-KEY-HERE',
    'Content-Type': 'application/json'
}
data = {
    "contactEmail": "[email protected]",
    "insightType": "WORK_MILESTONE"
}

response = requests.post(url, headers=headers, json=data)
print(response.text)

Response Format

The API will respond with the insight in JSON format. The response will contain an object with the following fields:

json

{
  "data": [
    {
      "subtype": "You worked at the same company",
      "userLinkedinUrl": "https://www.linkedin.com/in/daniel-wiener/",
      "contactLinkedinUrl": "https://www.linkedin.com/in/ryanbasch/",
      "userName": "Daniel",
      "contactName": "Ryan",
      "sharedCompanyName": "Oracle",
      "userSharedCompanyStartYear": 2017,
      "userSharedCompanyEndYear": 2017,
      "contactSharedCompanyStartYear": 2013,
      "contactSharedCompanyEndYear": 2014
    },
    {
      "subtype": "You live in the same city",
      "userLinkedinUrl": "https://www.linkedin.com/in/daniel-wiener/",
      "contactLinkedinUrl": "https://www.linkedin.com/in/scottleese/",
      "userName": "Daniel",
      "contactName": "Scott",
      "sharedCityName": "austin",
      "sharedCurrentCity": "austin"
    },
    {
      "subtype": "You went to the same school",
      "userLinkedinUrl": "https://www.linkedin.com/in/daniel-wiener/",
      "contactLinkedinUrl": "https://www.linkedin.com/in/katparker803",
      "userName": "Daniel",
      "contactName": "Kat",
      "sharedSchool": "University of Southern California"
    },
    {
      "subtype": "Prospect's previous company is a customer",
      "userLinkedinUrl": "https://www.linkedin.com/in/daniel-wiener/",
      "contactLinkedinUrl": "https://www.linkedin.com/in/shelbymfrazier",
      "userName": "Daniel",
      "contactName": "Shelby",
      "sharedCompanyName": "Brex",
      "contactSharedCompanyStartYear": 2019,
      "contactSharedCompanyEndYear": 2020
    }
  ]
}

Field Descriptions

• subtype (string): The subtype of the shared experience. Possible values are "You worked at the same company", "You live in the same city", "You went to the same school", and "Prospect's previous company is a customer".
• userLinkedinUrl (string): The LinkedIn URL of the user (seller).
• contactLinkedinUrl (string): The LinkedIn URL of the contact (prospect).
• userName (string): The name of the user (seller).
• contactName (string): The name of the contact (prospect).
• sharedCompanyName (string, optional): The name of the company where both the user and contact worked. Only applicable for the "You worked at the same company" and "Prospect's previous company is a customer" subtypes.
• userSharedCompanyStartYear (integer, optional): The year the user started working at the shared company. Only applicable for the "You worked at the same company" subtype.
• userSharedCompanyEndYear (integer, optional): The year the user ended working at the shared company. Only applicable for the "You worked at the same company" subtype.
• contactSharedCompanyStartYear (integer, optional): The year the contact started working at the shared company. Only applicable for the "You worked at the same company" and "Prospect's previous company is a customer" subtypes.
• contactSharedCompanyEndYear (integer, optional): The year the contact ended working at the shared company. Only applicable for the "You worked at the same company" and "Prospect's previous company is a customer" subtypes.
• sharedCityName (string, optional): The name of the city where both the user and contact live. Only applicable for the "You live in the same city" subtype.
• sharedCurrentCity (string, optional): Indicates if the shared city is the current city where both the user and contact live. Only applicable for the "You live in the same city" subtype.
• sharedSchool (string, optional): The name of the school that both the user and contact attended. Only applicable for the "You went to the same school" subtype.

Use Cases

The Shared Experiences insight is valuable for various use cases, such as:

• Personalized Outreach: Tailor your outreach messages based on the shared experiences between the user and the contact. Mentioning a common workplace, city, or school can help establish rapport and make the outreach more relevant and engaging.
• Relationship Building: Leverage shared experiences to find common ground and build stronger relationships with prospects. Discussing shared experiences can help create a sense of familiarity and trust, making it easier to establish a connection.
• Referral Generation: Identify potential referral opportunities based on shared experiences. If a user and a contact have worked at the same company or attended the same school, the user may be able to leverage their network to get introduced to the contact or gain valuable insights.
• Account Mapping: Use shared experiences to map out the relationships and connections within an account. Understanding the shared experiences between key stakeholders can help identify potential influencers, decision-makers, and champions within the organization.
• Sales Coaching: Provide sales teams with insights into shared experiences to help them prepare for calls and meetings. Knowing about common experiences can help sales reps find talking points, build rapport, and tailor their approach to each prospect.
• Lead Qualification: Assess the potential of a lead based on shared experiences. Prospects with shared experiences may be more likely to engage and respond positively to outreach efforts, as there is a pre-existing connection or commonality.
• By leveraging the Shared Experiences insight, you can gain valuable information about the common experiences and connections between users and contacts, enabling more personalized and effective outreach, relationship building, and sales strategies.