CINXE.COM

How to Be Great at Reaching Out: What Every InMail Sent in 2022 Told Us

<!DOCTYPE html> <html lang="en"> <head> <meta name="pageKey" content="d_lithograph_content"> <!----><!----> <meta name="locale" content="en_US"> <meta id="config" data-app-id="lithograph" data-app-version="0.0.1084" data-call-tree-id="AAYn3EV8QtiCXMd0wjte2A==" data-multiproduct-name="lithograph-publish-frontend" data-service-name="lithograph-publish-frontend" data-browser-id="b6257d84-f955-457c-82de-c1a57717dc2f" data-page-instance="urn:li:page:d_lithograph_content;hC4+HXjxStiMErXmwyzo6g==" data-disable-jsbeacon-pagekey-suffix="false"> <link rel="canonical" href="https://www.linkedin.com/business/sales/blog/prospecting/data-on-sending-inmails-higher-acceptance-rates"> <!----><!----> <!----> <!----> <!----> <link rel="manifest" href="/homepage-guest/manifest.json" crossorigin="use-credentials"> <link rel="icon" href="https://static.licdn.com/aero-v1/sc/h/al2o9zrvru7aqj8e1x2rzsrca"> <script> function getDfd() {let yFn,nFn;const p=new Promise(function(y, n){yFn=y;nFn=n;});p.resolve=yFn;p.reject=nFn;return p;} window.lazyloader = getDfd(); window.tracking = getDfd(); window.impressionTracking = getDfd(); window.ingraphTracking = getDfd(); window.appDetection = getDfd(); window.pemTracking = getDfd(); </script> <!----> <meta name="viewport" content="width=device-width, initial-scale=1.0"> <title>How to Be Great at Reaching Out: What Every InMail Sent in 2022 Told Us</title> <meta name="description" content="We analyzed every Sales Navigator InMail sent in 2022 and identified six learnings you can immediately apply."> <meta property="og:type" content="website"> <meta property="og:title" content="How to Be Great at Reaching Out: What Every InMail Sent in 2022 Told Us"> <meta property="og:description" content="We analyzed every Sales Navigator InMail sent in 2022 and identified six learnings you can immediately apply."> <meta property="og:url" content="https://www.linkedin.com/business/sales/blog/prospecting/data-on-sending-inmails-higher-acceptance-rates"> <meta property="og:image" content="https://media.licdn.com/dms/image/v2/D4D08AQFheDRKbsvnjQ/croft-frontend-shrinkToFit1024/croft-frontend-shrinkToFit1024/0/1644436006943?e=2147483647&amp;v=beta&amp;t=5o6SPElXzvgVwbG_XHJR7CPnAMMI8aLx5LOCMdo_sGI"> <meta name="twitter:title" content="How to Be Great at Reaching Out: What Every InMail Sent in 2022 Told Us"> <meta name="twitter:site" content="@linkedin"> <meta name="twitter:image" content="https://media.licdn.com/dms/image/v2/D4D08AQEbnlGbPoGikA/croft-frontend-shrinkToFit1024/croft-frontend-shrinkToFit1024/0/1644436011373?e=2147483647&amp;v=beta&amp;t=3By9YObJ_Rq-dKlfMdT4wzrKJu2In-Dr58MEijgmqiU"> <meta name="twitter:description" content="We analyzed every Sales Navigator InMail sent in 2022 and identified six learnings you can immediately apply."> <meta name="robots" content="noarchive"> <meta name="linkedin:pageTag" content="/business/sales/blog/prospecting/data-on-sending-inmails-higher-acceptance-rates"> <meta name="litmsProfileName" content="lithograph"> <!----> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <meta name="asset-url" id="artdeco/static/images/icons.svg" content="https://static.licdn.com/aero-v1/sc/h/6sz1e821vgereyxaakx87tt4z "> <link rel="stylesheet" href="https://static.licdn.com/aero-v1/sc/h/crjcj3vgj0tgpae2eu4u9y7eb"> <!----> <!----> </head> <body dir="ltr"> <!----> <a href="#lithograph-app" class="skip-link btn-md btn-primary absolute z-11 -top-[100vh] focus:top-0"> Skip to main content </a> <!----> <div class="page-header__wrapper page-header__wrapper--margin" data-custom-nav-wrapper="true"> <div class="page-header__container"> <header id="page-header" class="page-header page-header--hide-dropshadow"> <div class="page-header__content-container"> <div class="header__logo"> <a href="https://linkedin.com/business/sales/blog" class="custom-nav__logo-link"> <img class="header__linkedin-logo header__full-logo" src="https://static.licdn.com/aero-v1/sc/h/6zm111mce7vohqze950ilreo4" alt="LinkedIn Logo"> <img class="header__linkedin-logo header__in-bug" src="https://static.licdn.com/aero-v1/sc/h/5g0hjlcng3j5pgn50n2et1ca2" alt="LinkedIn Logo"> <span class="t-17 t-black t-bold default-header-title"> Sales Blog </span> </a> </div> <!----> <a class="artdeco-button artdeco-button--secondary artdeco-button--muted custom-nav__button" href="https://forms.feedblitz.com/636?src=topnavbutton" target="_blank"> Subscribe to blog </a> <button class="stripped header__expand-nav-button" data-mobile-header-navigation-button data-header-expand-navigation-button aria-expanded="false"> <li-icon class="header__expand-nav-icon" a11y-text="Open navigation" type="hamburger-icon"></li-icon> </button> <button class="stripped header__expand-nav-button hidden" data-mobile-header-navigation-button data-header-collapse-navigation-button aria-expanded="false"> <li-icon class="header__expand-nav-icon" a11y-text="Close navigation" type="cancel-icon"></li-icon> </button> </div> </header> </div> <nav class="header-nav fixed" aria-label="main" data-header-navigation> <ul class="header-nav__list"> <li> <div class="artdeco-dropdown"> <div class="artdeco-dropdown__trigger"> <a href="https://business.linkedin.com/sales-solutions/sales-navigator?trk=lss-blog-nav" class="t-sans t-black--light t-semibold header-nav__toplink" target="_self"> LinkedIn Sales Navigator </a> <button class="header-navigation__button" aria-label="Expand to show more links for LinkedIn Sales Navigator" aria-expanded="false" data-trigger-dropdown-menu type="button"> <li-icon size="small" type="caret-filled-down-icon"></li-icon> </button> <div class="artdeco-dropdown__content header-nav__dropdown-offset"> <ul> <li> <div class="artdeco-dropdown__item"> <a href="https://business.linkedin.com/sales-solutions/sales-navigator?trk=lss-blog-nav" class="t-14 t-sans t-black t-bold header-nav__link" target="_self">Learn more</a> </div> </li> <li> <div class="artdeco-dropdown__item"> <a href="https://business.linkedin.com/sales-solutions/request-free-demo-form?trk=lss-blog-nav-drop" class="t-14 t-sans t-black t-bold header-nav__link" target="_self">Request demo</a> </div> </li> </ul> </div> </div> </div> </li> <li> <div class="artdeco-dropdown"> <div class="artdeco-dropdown__trigger"> <a href="https://linkedin.com/business/sales/blog/topics" class="t-sans t-black--light t-semibold header-nav__toplink" target="_self"> Topics </a> <!----> </div> </div> </li> </ul> </nav> <nav class="custom-header__nav--mobile invisible" data-mobile-navigation="true" aria-label="main"> <ul class="custom-header__list--mobile"> <li class="custom-header__list-item--mobile" data-mobile-navigation-list-item="true"> <a href="https://business.linkedin.com/sales-solutions/sales-navigator?trk=lss-blog-nav" class="t-16 t-sans t-black t-semibold header-nav__toplink" target="_self"> LinkedIn Sales Navigator </a> <button class="header-navigation__button" aria-label="Expand to show more links for LinkedIn Sales Navigator" aria-expanded="false" data-mobile-dropdown-trigger type="button"> <li-icon size="small" type="chevron-down-icon"></li-icon> </button> <ul class="custom-header__dropdownlink-list--mobile hidden" data-dropdownlinks-list="true"> <li> <a href="https://business.linkedin.com/sales-solutions/sales-navigator?trk=lss-blog-nav" class="t-sans t-black t-normal header-nav__link" target="_self">Learn more</a> </li> <li> <a href="https://business.linkedin.com/sales-solutions/request-free-demo-form?trk=lss-blog-nav-drop" class="t-sans t-black t-normal header-nav__link" target="_self">Request demo</a> </li> </ul> </li> <li class="custom-header__list-item--mobile" data-mobile-navigation-list-item="true"> <a href="https://linkedin.com/business/sales/blog/topics" class="t-16 t-sans t-black t-semibold header-nav__toplink" target="_self"> Topics </a> <!----> </li> </ul> <div class="custom-header__button-share-container--mobile"> <a class="medium-secondary-muted-button" href="https://forms.feedblitz.com/636?src=topnavbutton" target="_blank"> Subscribe to blog </a> </div> </nav> </div> <main role="main"> <div id="lithograph-app"> <section id="component-container" data-attach-collapse-behavior="true"> <div id class="component component-articleHeadline" data-component-type="articleHeadline"> <div class="article-headline-container"> <p class="article-headline__topic"> <a class="t-14" href="https://www.linkedin.com/business/sales/blog/prospecting">Sales prospecting</a> </p> <h1 class="article-headline t-40" data-article-title="How to Be Great at Reaching Out: What Every InMail Sent in 2022 Told Us">How to Be Great at Reaching Out: What Every InMail Sent in 2022 Told Us</h1> <div class="article-meta t-14 article-meta__hairline"> <div class="article-meta__byline-container"> <div class="author-profile__author-container"> <img class="author-profile__author-image" srcset="https://media.licdn.com/dms/image/v2/D4E03AQGa16zw46XgSQ/profile-displayphoto-shrink_100_100/profile-displayphoto-shrink_100_100/0/1701820015987?e=2147483647&amp;v=beta&amp;t=ONNHwS5ebF3vu5lyii8k6jGRDU1-XXzgRQGMsX6QRoE 100w,https://media.licdn.com/dms/image/v2/D4E03AQGa16zw46XgSQ/profile-displayphoto-shrink_200_200/profile-displayphoto-shrink_200_200/0/1701820015987?e=2147483647&amp;v=beta&amp;t=Bd36gCyOTlmr9MrBApfzN-5ZIddt1Fy9hJ3PYnKK2-8 200w,https://media.licdn.com/dms/image/v2/D4E03AQGa16zw46XgSQ/profile-displayphoto-shrink_400_400/profile-displayphoto-shrink_400_400/0/1701820015987?e=2147483647&amp;v=beta&amp;t=Z0JIK180-_Qcn-R_qlJUEyXCeKXp73o7ESDHdexBhq8 400w,https://media.licdn.com/dms/image/v2/D4E03AQGa16zw46XgSQ/profile-displayphoto-shrink_800_800/profile-displayphoto-shrink_800_800/0/1701820015987?e=2147483647&amp;v=beta&amp;t=Mu2luk_9r1KfM8yi5aXrvkY7wlkZGLMIBDlpR_sioNc 800w," sizes="(max-width: 480px) 480px, (max-width: 767px) 767px, (max-width: 1024px) 1024px, 1920px" src="https://media.licdn.com/dms/image/v2/D4E03AQGa16zw46XgSQ/profile-displayphoto-shrink_800_800/profile-displayphoto-shrink_800_800/0/1701820015987?e=2147483647&amp;v=beta&amp;t=Mu2luk_9r1KfM8yi5aXrvkY7wlkZGLMIBDlpR_sioNc" alt="Paul Petrone"> <div class="author-profile__author-text-container"> <a href="https://www.linkedin.com/in/paulpetrone" target="_blank" class="t-14 t-bold"><span class="screen-reader">Authored by</span>Paul Petrone</a> <p class="t-14">Marketing @ LinkedIn</p> <p class="t-14 t-black--light" data-published-date="2023-4-18"> April 18, 2023 </p> </div> </div> <!----> <div class="author-profile__co-authors-container"> <p> Co-authors: <!----> <a href="https://www.linkedin.com/in/paulpetrone" target="_blank"><span class="screen-reader">Co-authored by</span>Paul Petrone</a><!----> and <a href="https://www.linkedin.com/in/carlaintal" target="_blank"><span class="screen-reader">Co-authored by</span>Carla Intal</a><!----> </p> </div> </div> <div class="social-share"> <ul class="social-share__list share-list" title="Share via" data-share-list> <li class="share-list__item share-item"> <a href="#" class="share-item__link medium-round-muted-tertiary-button" role="button" data-tracking-control-name="_linkedin_share" data-share-type="linkedin" aria-label="Share on LinkedIn, New window will open"> <li-icon class="share-item__icon" type="linkedin-icon"></li-icon> </a> </li> <li class="share-list__item share-item"> <a href="#" class="share-item__link medium-round-muted-tertiary-button" role="button" data-tracking-control-name="_facebook_share" data-share-type="facebook" aria-label="Share on Facebook, New window will open"> <li-icon class="share-item__icon" type="facebook-icon"></li-icon> </a> </li> <li class="share-list__item share-item"> <a href="#" class="share-item__link medium-round-muted-tertiary-button" role="button" data-tracking-control-name="_twitter_share" data-share-type="twitter" aria-label="Share on Twitter, New window will open"> <li-icon class="share-item__icon" type="twitter-icon"></li-icon> </a> </li> </ul> </div> </div> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--reader"> <p>What does an InMail represent?</p> <p>For a <a rel="" href="https://business.linkedin.com/sales-solutions?trk=lss-blog-InMail-data" target="_self">Sales Navigator</a> user, an opportunity. <a rel="" href="https://business.linkedin.com/sales-solutions/resources/prospecting?trk=lss-blog-InMail-data" target="_self">And a good one at that</a> – InMails are 3x more likely to be accepted than a cold call, and 6x more likely than email.&nbsp;</p> <p>Then again, an InMail could also mean nothing. If the person doesn’t accept it and respond to it, it’s just words in the ether.</p> <p>How do you get more of the former and less of the latter? To find out, we analyzed every single Sales Navigator InMail sent in 2022.</p> <p>From that, we identified six learnings you can immediately apply. Let’s dive in.</p> <h2><strong>1. Researching your prospect and their organization before sending an InMail has a massive payoff.</strong></h2> <p>If you view a person’s LinkedIn profile and then send them an InMail within 30 days, that person is 78% more likely to accept it. The more you view someone’s profile in that 30-day period, the more likely they are to accept your InMail.</p> </div> </div> <div id class="component component-standaloneImage" data-component-type="standaloneImage"> <div class="standalone-image-component standalone-image-component--article-width"> <figure> <img class="standalone-image-component__image" sizes="(max-width: 480px) 480px, (max-width: 767px) 767px, (max-width: 1024px) 1024px, 1920px" data-delayed-url="https://media.licdn.com/dms/image/v2/D4D08AQHkNiU2YNftYA/croft-frontend-shrinkToFit1024/croft-frontend-shrinkToFit1024/0/1682350358378?e=2147483647&amp;v=beta&amp;t=1Vy__-B-9XYW4qorTFhJmSWo_TxwbO5t983Rommmg4o" alt="If you view a person’s LinkedIn profile and then send them an InMail within 30 days, that person is 78% more likely to accept it."> <!----> </figure> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--reader"> <p>Why? Viewing a person’s profile for the sake of viewing their profile is meaningless. The bigger point is it means you’ve done some research on the person, which will help you to write a more personalized InMail when you do reach out.</p> <p>The same goes for researching a person’s organization before InMailing. If you follow a prospect’s organization on LinkedIn before reaching out, they are 15% more likely to accept your InMail.</p> <p>Why? Same reason. Following your prospect’s organization is meaningless on its own; what it gives you is insight into what that organization is focused on. If you can tailor your InMail around what their organization is focused on, your prospect is much more likely to accept it.&nbsp;</p> <p><a rel="" href="https://www.linkedin.com/business/sales/blog/b2b-sales/how-to-do-sales-research-tactics-from-great-sellers-what-to-look-for?trk=lss-blog-InMail-data" target="_self">This jives with our finding that top-performing sellers</a> – i.e. those who hit 150% of quota – do twice as much <a rel="" href="https://www.linkedin.com/business/sales/blog/b2b-sales/how-to-do-sales-research-tactics-from-great-sellers-what-to-look-for?trk=lss-blog-InMail-data" target="_self">research</a> as their peers. The <a rel="" href="https://business.linkedin.com/sales-solutions/cx/23/03/how-companies-drive-bigger-deals-stronger-pipeline-and-higher-revenue?trk=lss-blog-InMail-data" target="_self">deeper</a> you understand your buyer, the more relevant the message you’ll be able to send them.</p> <h2><strong>2. Having a strong LinkedIn presence leads to more people accepting your InMails.</strong></h2> <p>Salespeople hear a lot about building out their brand on LinkedIn and positioning themselves as thought leaders. But does it really work?</p> <p>The data says yes. Specifically, having a complete LinkedIn profile can lead to an 87% increase in InMail acceptance rates, <a rel="" href="https://www.linkedin.com/business/sales/blog/strategy/virtual-selling-actions-assured-to-help-you-exceed-sales-targets?trk=lss-blog-InMail-data" target="_self">our analysis found</a>.</p> </div> </div> <div id class="component component-standaloneImage" data-component-type="standaloneImage"> <div class="standalone-image-component standalone-image-component--article-width"> <figure> <img class="standalone-image-component__image" sizes="(max-width: 480px) 480px, (max-width: 767px) 767px, (max-width: 1024px) 1024px, 1920px" data-delayed-url="https://media.licdn.com/dms/image/v2/D4D08AQHAPv-I-uJMbA/croft-frontend-shrinkToFit1024/croft-frontend-shrinkToFit1024/0/1680100291745?e=2147483647&amp;v=beta&amp;t=1xUyz2kdfWU_qyvJsc9ns4tzHrvoo-QzhQuvkzpBDTc" alt="InMail.Data"> <!----> </figure> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--reader"> <p>The reason why – our study found that salespeople’s profiles are viewed at twice the rate of the normal professional. Meaning, people are likely to research you and use that to decide if they will accept your InMail or not.</p> <p>What message are you sending to buyers with your LinkedIn profile? Are you warm and engaging, with a solid photo and a good summary, who has some credibility in the space they are selling into? Or, is your LinkedIn profile bare, making it feel like the InMail came from a bot?</p> <p><strong>Bonus tip:</strong> <a rel="" href="https://www.linkedin.com/business/sales/blog/b2b-sales/the-mistake-sellers-make-with-their-linkedin-profile-and-how-to-fix-it?trk=lss-blog-InMail-data" target="_self">This post details how to make a great LinkedIn profile as a seller</a>.</p> <h2><strong>3. Encourage your company to build out its brand on LinkedIn, too.</strong></h2> <p>You are a brand, but the company you work for also is a brand too. And the more your company works to build out its brand on LinkedIn, the easier it’ll be for you to sell.</p> <p>Case-in-point – there are massive tailwinds to your company building out its following on LinkedIn, for you as a seller. That’s because if a member follows your company on LinkedIn, they are 270% more likely to accept your InMail. Two-hundred-and-seventy percent!</p> </div> </div> <div id class="component component-standaloneImage" data-component-type="standaloneImage"> <div class="standalone-image-component standalone-image-component--article-width"> <figure> <img class="standalone-image-component__image" sizes="(max-width: 480px) 480px, (max-width: 767px) 767px, (max-width: 1024px) 1024px, 1920px" data-delayed-url="https://media.licdn.com/dms/image/v2/D4D08AQHEn8_HODJbGA/croft-frontend-shrinkToFit1024/croft-frontend-shrinkToFit1024/0/1680100401278?e=2147483647&amp;v=beta&amp;t=EygKhez_3uISu0ziasusxgF_SqzFLlHT565aAxrQCxU" alt="If a member follows your company on LinkedIn, they are 270% more likely to accept your InMail"> <!----> </figure> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--reader"> <p><a rel="" href="https://business.linkedin.com/marketing-solutions/linkedin-pages/best-practices?trk=lss-blog-InMail-data" target="_self">Here are best practices</a> your company can use to build out its company page on LinkedIn.&nbsp;</p> <p>Granted, this might not be in your control, as a seller. But, if both you and your company work to build out your collective brands on LinkedIn, both will benefit.</p> <h2><strong>4. People are much more likely to accept an InMail if they just started a new job.</strong></h2> <p>When is a good time to InMail a prospect?&nbsp;</p> <p>According to the data, shortly after someone starts a new job. The data:</p> <ul> <li>People who started a new job at a new company within the past 90 days are 62% more likely to accept an InMail, versus everyone else.&nbsp;</li> <li>People who started a new role within the past 90 days – even if it’s at the same company –&nbsp;are 51% more likely to accept an InMail, versus everyone else.</li> </ul> </div> </div> <div id class="component component-standaloneImage" data-component-type="standaloneImage"> <div class="standalone-image-component standalone-image-component--article-width"> <figure> <img class="standalone-image-component__image" sizes="(max-width: 480px) 480px, (max-width: 767px) 767px, (max-width: 1024px) 1024px, 1920px" data-delayed-url="https://media.licdn.com/dms/image/v2/D4D08AQEDe7Bp2NNQoQ/croft-frontend-shrinkToFit1024/croft-frontend-shrinkToFit1024/0/1680100456688?e=2147483647&amp;v=beta&amp;t=krOGLXO_PpUYkymiOswz-5Sa0QSVdsK07-_FSe_wUbw" alt="People who started a new job at a new company within the past 90 days are 62% more likely to accept an InMail, versus everyone else. "> <!----> </figure> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--reader"> <p>In other words – when it comes to InMailing, change is good.</p> <p>This makes sense, as when someone starts a job, they often want to put their imprint on it. They want to explore new options.</p> <p><strong>Bonus tip:</strong> <a rel="" href="https://www.linkedin.com/business/sales/blog/prospecting/inmail-someone-starts-a-new-job?trk=lss-blog-InMail-data" target="_self">This post details what to InMail prospects who just changed jobs</a>.</p> <h2><strong>5. The more active a buyer is on LinkedIn, the more likely they’ll accept your InMail.</strong></h2> <p>This one isn’t too shocking. The more active someone is on LinkedIn, the more likely they’ll accept your InMail.</p> <p>The data – someone who has posted at least once on LinkedIn in the past three months is 45% more likely to accept your InMail. And the more they’ve posted, the data shows the more likely they are to accept an InMail.</p> </div> </div> <div id class="component component-standaloneImage" data-component-type="standaloneImage"> <div class="standalone-image-component standalone-image-component--article-width"> <figure> <img class="standalone-image-component__image" sizes="(max-width: 480px) 480px, (max-width: 767px) 767px, (max-width: 1024px) 1024px, 1920px" data-delayed-url="https://media.licdn.com/dms/image/v2/D4D08AQGNHcNx_aGNYQ/croft-frontend-shrinkToFit1024/croft-frontend-shrinkToFit1024/0/1680100499145?e=2147483647&amp;v=beta&amp;t=IYbY8ih83xBLvvTbWgFwHYllpforWdLvWIIHO8v1Dew" alt="Someone who has posted at least once on LinkedIn in the past three months is 45% more likely to accept your InMail. And the more they’ve posted, the data shows the more likely they are to accept an InMail."> <!----> </figure> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--reader"> <p>How do you action this? Two ways:</p> <ul> <li>One of the <a rel="" href="https://www.linkedin.com/business/sales/blog/sales-navigator/how-to-use-filters-to-find-the-best-leads-in-linkedin-sales-navigator?trk=lss-blog-InMail-data" target="_self">Spotlight search filters</a> within Sales Navigator is “Posted on LinkedIn in the past 30 days.” Use it – it’s a great way to identify people who are more active on the platform.</li> <li>Go beyond just InMailing someone who is active on the platform! <a rel="" href="https://www.linkedin.com/help/sales-navigator/answer/a101025/view-and-save-leads-in-sales-navigator?lang=en?trk=lss-blog-InMail-data" target="_self">Save them as a lead</a>, so you are alerted whenever they post on LinkedIn. If you can, thoughtfully respond to their posts. This exponentially improves your chances of building a lasting relationship with them.</li> </ul> <h2><strong>6. What doesn’t matter – what day you send your InMails.</strong></h2> <p>You know what doesn’t really matter, when it comes to sending InMails?&nbsp;</p> <p>The day you send them. InMail acceptance rates are consistent across all days of the week.</p> <p>Buyers are slightly more likely to accept an InMail on the weekend, versus the weekday. Although far fewer InMails are sent on weekends, so the data isn’t statistically significant.</p> <p>The bigger point – don’t worry about when you send your InMails. Instead, focus your energy on who you're sending them to and how you can best tailor your message to their needs.</p> <h2><strong>The takeaway: InMailing effectively is about deeply understanding your buyer.</strong></h2> <p>This InMail data cements the <a rel="" href="https://business.linkedin.com/sales-solutions/deep-sales?trk=lss-blog-InMail-data" target="_self">deep sales philosophy</a>. When it comes to outreach, the deeper you understand your buyer, the more likely you’ll be able to create a compelling opening message and ultimately build a relationship with them.</p> <p>The data also highlights the worst way to InMail – the “quantity over quality” approach, where you are just sending to whoever with generic messaging. Not only is that strategy ineffective, it <a rel="" href="https://www.linkedin.com/business/sales/blog/trends/why-unwelecomed-sales-outreach-wont-just-be-annoying-it-will-destroy-brand-equity?trk=lss-blog-InMail-data" target="_self">erodes you and your company’s brand over time</a>.</p> <p>Additionally, the best InMailers also understand that all senders aren’t created equal. If they can establish themselves on LinkedIn as a trusted industry voice, then when they do send an InMail, it’s far more likely to be opened and accepted.</p> <p>Bottom line, there’s no shortcut to InMailing. Getting the most out of it comes down to work – putting the work in to build your own brand and putting in the work writing each InMail.</p> <p>That work has a massive payoff though. The hope is this data will help you focus your efforts.</p> <p><strong>Looking to get even more out of Sales Navigator? These posts can help:</strong></p> <ul> <li><a rel="" href="https://www.linkedin.com/business/sales/blog/sales-navigator/sales-navigator-alerts-what-they-are-how-to-best-use-them" target="_self"><strong>Sales Navigator Alerts: What They Are and How to Best Use Them</strong></a></li> <li><a rel="" href="https://www.linkedin.com/business/sales/blog/b2b-sales/buyer-intent-for-sales-what-it-is-and-how-it-can-help-you-close-deals" target="_self"><strong>Buyer Intent for Sales: What It Is and How It Can Help You Close Deals</strong></a></li> <li><a rel="" href="https://www.linkedin.com/business/sales/blog/sales-navigator/how-to-search-within-sales-navigator-top-tricks-hacks" target="_self"><strong>3 Tips Worth Checking Out When Searching in Sales Navigator</strong></a></li> <li><a rel="" href="https://www.linkedin.com/business/sales/blog/product-updates/what-is-relationship-explorer-linkedin-sales-navigator-and-how-to-use-it" target="_self"><strong>What is Relationship Explorer – And Why LinkedIn's Sellers Are Excited About It</strong></a></li> </ul> <p><strong>Don’t have Sales Navigator?</strong> <a rel="" href="https://business.linkedin.com/sales-solutions/sales-navigator?trk=lss-blog-InMail-data" target="_self">See how it can help you and your team here</a><strong>.</strong></p> </div> </div> <div id class="component component-standaloneImage" data-component-type="standaloneImage"> <div class="standalone-image-component standalone-image-component--article-width"> <a class="standalone-image-component__link" href="https://www.linkedin.com/business/sales/blog/prospecting/7-steps-attract-more-clients-with-linkedin" target="_self"> <figure> <img class="standalone-image-component__image" sizes="(max-width: 480px) 480px, (max-width: 767px) 767px, (max-width: 1024px) 1024px, 1920px" data-delayed-url="https://media.licdn.com/dms/image/v2/D4D08AQH3o_NTqe6BOA/croft-frontend-shrinkToFit1024/croft-frontend-shrinkToFit1024/0/1683645955527?e=2147483647&amp;v=beta&amp;t=lRQJB7RLJTmaa0lVSnaNARdY72iTom90jtD1rmAtpbU" alt="Deep Sales Advantage"> <!----> </figure> </a> </div> </div> <div id class="component component-postList" data-component-type="postList"> <section id="postList0FocusPoint" class="component__content-container list-layout" data-post-list> <section class="simple-topic-list"> <p class="t-14 t-bold">Topics: <a class="simple-topic-list__topic" href="https://www.linkedin.com/business/sales/blog/prospecting"> Sales prospecting </a> </p> </section> <hr class="artdeco-divider"> <section class="list-layout__headline-container"> <p class="list-layout__headline t-32 t-sans">Related articles</p> <!----> </section> <ul class="list-layout__posts"> <li class="post-list__item list-post"> <div class="list-post__content-container"> <p class="list-post__content-container__topic"> <a class="t-14 t-bold" href="https://www.linkedin.com/business/sales/blog/prospecting"> Sales prospecting </a> </p> <div class="list-post__content-container__title"> <a class="list-post__link t-20 t-black" href="https://www.linkedin.com/business/sales/blog/prospecting/how-to-get-sales-referrals-and-turn-them-into-meetings"> Referrals in Sales = Awesome. Here's How to Get Them Consisten... </a> </div> <div class="list-post__content-container__byline"> <p class="list-post__content-container__author t-14 t-bold t-black"> Jack McKissen </p> <p class="list-post__content-container__date t-14 t-black--light"> Jan 9, 2024 </p> </div> </div> <div class="list-post__image-container"> <figure class="post__image-figure"> <img class="post__image" alt="Referrals are one of the best ways to source deals. Here’s how sellers can consistently make it happen." data-delayed-url="https://media.licdn.com/dms/image/v2/D4D08AQEbRDg2qmi6fQ/croft-frontend-shrinkToFit1024/croft-frontend-shrinkToFit1024/0/1680699153133?e=2147483647&amp;v=beta&amp;t=6FJ_48QqBKgTzaYRLrJtQNH2OqAwrxEmQb3tYYFZYpI" data-ghost-url="https://static.licdn.com/aero-v1/sc/h/8pouyb1ly746xtru0x7p2axm0" sizes="(max-width: 480px) 480px, (max-width: 767px) 767px, (max-width: 1024px) 1024px, 480px"> </figure> </div> </li> <li class="post-list__item list-post"> <div class="list-post__content-container"> <p class="list-post__content-container__topic"> <a class="t-14 t-bold" href="https://www.linkedin.com/business/sales/blog/prospecting"> Sales prospecting </a> </p> <div class="list-post__content-container__title"> <a class="list-post__link t-20 t-black" href="https://www.linkedin.com/business/sales/blog/prospecting/sales-navigator-small-business-first-five-things-i-would-do"> Sales Navigator for Small Businesses: The 5 First Steps I'd St... </a> </div> <div class="list-post__content-container__byline"> <p class="list-post__content-container__author t-14 t-bold t-black"> David J.P. Fisher </p> <p class="list-post__content-container__date t-14 t-black--light"> Dec 18, 2023 </p> </div> </div> <div class="list-post__image-container"> <figure class="post__image-figure"> <img class="post__image" alt="When I ran my own small business, LinkedIn Sales Navigator was a great platform I used to find new clients. Here's where I recommend fellow small business owners should start wi..." data-delayed-url="https://media.licdn.com/dms/image/v2/D4D08AQEHmLr3y_oOEg/croft-frontend-shrinkToFit1024/croft-frontend-shrinkToFit1024/0/1701446084626?e=2147483647&amp;v=beta&amp;t=8-38I77_Idwu1TtbOlowM4ErRMhRReI0WbEwG3OkRsg" data-ghost-url="https://static.licdn.com/aero-v1/sc/h/8pouyb1ly746xtru0x7p2axm0" sizes="(max-width: 480px) 480px, (max-width: 767px) 767px, (max-width: 1024px) 1024px, 480px"> </figure> </div> </li> <li class="post-list__item list-post"> <div class="list-post__content-container"> <p class="list-post__content-container__topic"> <a class="t-14 t-bold" href="https://www.linkedin.com/business/sales/blog/prospecting"> Sales prospecting </a> </p> <div class="list-post__content-container__title"> <a class="list-post__link t-20 t-black" href="https://www.linkedin.com/business/sales/blog/profile-best-practices/how-to-use-who-viewed-your-profile-in-linkedin-to-find-new-clients"> 'Who’s Viewed Your LinkedIn Profile' — How to Use This Feature... </a> </div> <div class="list-post__content-container__byline"> <p class="list-post__content-container__author t-14 t-bold t-black"> Paul Petrone </p> <p class="list-post__content-container__date t-14 t-black--light"> Dec 4, 2023 </p> </div> </div> <div class="list-post__image-container"> <figure class="post__image-figure"> <img class="post__image" alt="This feature, which shows people who viewed your LinkedIn profile, can be a great source of inbound leads. Here's how to make the most out of them." data-delayed-url="https://media.licdn.com/dms/image/v2/D4D08AQHN6T0R2Rf7qg/croft-frontend-shrinkToFit1024/croft-frontend-shrinkToFit1024/0/1701107548247?e=2147483647&amp;v=beta&amp;t=t9WtR7N906zPRKo5pzHW_ouG6nOacPN4oeLMWJh5LI8" data-ghost-url="https://static.licdn.com/aero-v1/sc/h/8pouyb1ly746xtru0x7p2axm0" sizes="(max-width: 480px) 480px, (max-width: 767px) 767px, (max-width: 1024px) 1024px, 480px"> </figure> </div> </li> </ul> <!----> </section> </div> <div id class="component component-banner" data-component-type="banner"> <div class="banner banner--v3 banner--full-width banner--light-colored-background banner--center banner-height-desktop--default banner-height-tablet--default banner-height-mobile--default" data-banner> <div class="banner__image-container " aria-hidden="true"> <img class="banner__image image-pin--middle-center" alt srcset="https://media.licdn.com/dms/image/v2/C4D08AQHwHMvxZ-OaEA/croft-frontend-shrinkToFit480/croft-frontend-shrinkToFit480/0/1591839930119?e=2147483647&amp;v=beta&amp;t=WDTIqi9Yt3oOnRf1AvcM7uzgs2kQG1g6FTgCuMdLIgk 480w,https://media.licdn.com/dms/image/v2/C4D08AQHwHMvxZ-OaEA/croft-frontend-shrinkToFit767/croft-frontend-shrinkToFit767/0/1591839930119?e=2147483647&amp;v=beta&amp;t=i2K-jDHburAzmgqwYRv6klrOV85oodl-A4oK2URJUUA 767w,https://media.licdn.com/dms/image/v2/C4D08AQHwHMvxZ-OaEA/croft-frontend-shrinkToFit1920/croft-frontend-shrinkToFit1920/0/1591839930119?e=2147483647&amp;v=beta&amp;t=I_8al1qZp_-DZIbk9JOjuSOGOQfqib-cVehiS-3DO8w 1280w,https://media.licdn.com/dms/image/v2/C4D08AQHwHMvxZ-OaEA/croft-frontend-shrinkToFit600/croft-frontend-shrinkToFit600/0/1591839930119?e=2147483647&amp;v=beta&amp;t=YjYKdqUFv9cWkYhT5Cjy_27tneU8lxX24YB3hJ02GRk 600w,https://media.licdn.com/dms/image/v2/C4D08AQHwHMvxZ-OaEA/croft-frontend-shrinkToFit1200/croft-frontend-shrinkToFit1200/0/1591839930119?e=2147483647&amp;v=beta&amp;t=ekWXam3tRXyE0dlyAm6P-B0Vz5d7z-jioBQQJV0dAFU 1200w,https://media.licdn.com/dms/image/v2/C4D08AQHwHMvxZ-OaEA/croft-frontend-shrinkToFit1024/croft-frontend-shrinkToFit1024/0/1591839930119?e=2147483647&amp;v=beta&amp;t=q2eTdt0VMr3_cJWfmT0l8INHuNv0Fi6VY_2A88akrA4 1024w," sizes="(max-width: 480px) 480px, (max-width: 767px) 767px, (max-width: 1024px) 1024px, 1920px" src="https://media.licdn.com/dms/image/v2/C4D08AQHwHMvxZ-OaEA/croft-frontend-shrinkToFit1024/croft-frontend-shrinkToFit1024/0/1591839930119?e=2147483647&amp;v=beta&amp;t=q2eTdt0VMr3_cJWfmT0l8INHuNv0Fi6VY_2A88akrA4"> <div class="banner__overlay"></div> </div> <div class="banner__headline-container"> <div class="banner__position"> <!----><!----> <h2 class="banner__headline t-32"> Sales is about building the right relationships. </h2> <!----> <p class="banner__subheadline t-18"> See how LinkedIn Sales Solutions can help. </p> <!----><!----><!----> <div class="banner__button-container"> <!----> <a class="banner__button button__mainButton button__secondary" href="https://business.linkedin.com/sales-solutions?trk=lss-blog-banner-article" target="_self"> Learn more </a> </div> </div> </div> </div> </div> <div id> <div class="messaging-overlay__container" data-collapse-container="true"> <button class="messaging-overlay__header t-16 t-bold t-sans" data-collapse-trigger data-messaging-overlay-header> <div> <li-icon class="messaging-overlay__header-icon t-16" size="small" type="rss-icon"></li-icon> <span class="messaging-overlay__header-title t-16 t-bold"> Subscribe to blog </span> </div> <li-icon class="messaging-overlay__header-icon messaging-overlay__header-icon--closed" size="small" a11y-text="Messaging overlay" type="chevron-down-icon"></li-icon> </button> <div class="messaging-overlay__body t-16 t-normal t-sans" data-collapse-target="true" data-collapsed="true" data-messaging-overlay-content="true" data-open-automatically="false"> <p class="messaging-overlay__body-text"> Join the Buyer First Movement. Right in your inbox </p> <div class="messaging-overlay__button-container"> <a class="medium-button" href="http://forms.feedblitz.com/636" target="_blank"> Subscribe now </a> </div> <hr class="messaging-overlay__rule" aria-hidden="true"> <ul class="messaging-overlay__secondary-links t-14 t-bold t-sans"> <li class="messaging-overlay__secondary-link"> <a href="https://business.linkedin.com/sales-solutions?trk=lss-blog-pa" target="_blank"> Learn more about LinkedIn Sales Solutions </a> </li> </ul> </div> </div> </div> </section> </div> <script src="https://static.licdn.com/aero-v1/sc/h/8hfbuq1ftcvnnx4dd5067pi0t" async></script> <script src="https://static.licdn.com/aero-v1/sc/h/dev5px9xu71l67oqmrrbimi6b" async></script> <script src="https://static.licdn.com/aero-v1/sc/h/3e9epkft4bs8unu9ky8gss8ya" async></script> </main> <footer class="li-footer bg-transparent w-full "> <ul class="li-footer__list flex flex-wrap flex-row items-start justify-start w-full h-auto min-h-[50px] my-[0px] mx-auto py-3 px-2 papabear:w-[1128px] papabear:p-0"> <li class="li-footer__item font-sans text-xs text-color-text-low-emphasis flex flex-shrink-0 justify-start p-1 relative w-50% papabear:justify-center papabear:w-auto"> <span class="sr-only">LinkedIn</span> <icon class="li-footer__copy-logo text-color-logo-brand-alt inline-block self-center h-[14px] w-[56px] mr-1" data-delayed-url="https://static.licdn.com/aero-v1/sc/h/e12h2cd8ac580qen9qdd0qks8"></icon> <span class="li-footer__copy-text flex items-center">&copy; 2024</span> </li> <li class="li-footer__item font-sans text-xs text-color-text-low-emphasis flex flex-shrink-0 justify-start p-1 relative w-50% papabear:justify-center papabear:w-auto"> <a class="li-footer__item-link flex items-center font-sans text-xs font-bold text-color-text-low-emphasis hover:text-color-link-hover focus:text-color-link-focus" href="https://about.linkedin.com?trk=content_footer-about" data-tracking-control-name="content_footer-about" data-tracking-will-navigate> About </a> </li> <li class="li-footer__item font-sans text-xs text-color-text-low-emphasis flex flex-shrink-0 justify-start p-1 relative w-50% papabear:justify-center papabear:w-auto"> <a class="li-footer__item-link flex items-center font-sans text-xs font-bold text-color-text-low-emphasis hover:text-color-link-hover focus:text-color-link-focus" href="https://www.linkedin.com/accessibility?trk=content_footer-accessibility" data-tracking-control-name="content_footer-accessibility" data-tracking-will-navigate> Accessibility </a> </li> <li class="li-footer__item font-sans text-xs text-color-text-low-emphasis flex flex-shrink-0 justify-start p-1 relative w-50% papabear:justify-center papabear:w-auto"> <a class="li-footer__item-link flex items-center font-sans text-xs font-bold text-color-text-low-emphasis hover:text-color-link-hover focus:text-color-link-focus" href="https://www.linkedin.com/legal/user-agreement?trk=content_footer-user-agreement" data-tracking-control-name="content_footer-user-agreement" data-tracking-will-navigate> User Agreement </a> </li> <li class="li-footer__item font-sans text-xs text-color-text-low-emphasis flex flex-shrink-0 justify-start p-1 relative w-50% papabear:justify-center papabear:w-auto"> <a class="li-footer__item-link flex items-center font-sans text-xs font-bold text-color-text-low-emphasis hover:text-color-link-hover focus:text-color-link-focus" href="https://www.linkedin.com/legal/privacy-policy?trk=content_footer-privacy-policy" data-tracking-control-name="content_footer-privacy-policy" data-tracking-will-navigate> Privacy Policy </a> </li> <!----> <li class="li-footer__item font-sans text-xs text-color-text-low-emphasis flex flex-shrink-0 justify-start p-1 relative w-50% papabear:justify-center papabear:w-auto"> <a class="li-footer__item-link flex items-center font-sans text-xs font-bold text-color-text-low-emphasis hover:text-color-link-hover focus:text-color-link-focus" href="https://www.linkedin.com/legal/cookie-policy?trk=content_footer-cookie-policy" data-tracking-control-name="content_footer-cookie-policy" data-tracking-will-navigate> Cookie Policy </a> </li> <li class="li-footer__item font-sans text-xs text-color-text-low-emphasis flex flex-shrink-0 justify-start p-1 relative w-50% papabear:justify-center papabear:w-auto"> <a class="li-footer__item-link flex items-center font-sans text-xs font-bold text-color-text-low-emphasis hover:text-color-link-hover focus:text-color-link-focus" href="https://www.linkedin.com/legal/copyright-policy?trk=content_footer-copyright-policy" data-tracking-control-name="content_footer-copyright-policy" data-tracking-will-navigate> Copyright Policy </a> </li> <li class="li-footer__item font-sans text-xs text-color-text-low-emphasis flex flex-shrink-0 justify-start p-1 relative w-50% papabear:justify-center papabear:w-auto"> <a class="li-footer__item-link flex items-center font-sans text-xs font-bold text-color-text-low-emphasis hover:text-color-link-hover focus:text-color-link-focus" href="https://brand.linkedin.com/policies?trk=content_footer-brand-policy" data-tracking-control-name="content_footer-brand-policy" data-tracking-will-navigate> Brand Policy </a> </li> <li class="li-footer__item font-sans text-xs text-color-text-low-emphasis flex flex-shrink-0 justify-start p-1 relative w-50% papabear:justify-center papabear:w-auto"> <a class="li-footer__item-link flex items-center font-sans text-xs font-bold text-color-text-low-emphasis hover:text-color-link-hover focus:text-color-link-focus" href="https://www.linkedin.com/psettings/guest-controls?trk=content_footer-guest-controls" data-tracking-control-name="content_footer-guest-controls" data-tracking-will-navigate> Guest Controls </a> </li> <li class="li-footer__item font-sans text-xs text-color-text-low-emphasis flex flex-shrink-0 justify-start p-1 relative w-50% papabear:justify-center papabear:w-auto"> <a class="li-footer__item-link flex items-center font-sans text-xs font-bold text-color-text-low-emphasis hover:text-color-link-hover focus:text-color-link-focus" href="https://www.linkedin.com/help/linkedin/answer/34593?trk=content_footer-community-guide" data-tracking-control-name="content_footer-community-guide" data-tracking-will-navigate> Community Guidelines </a> </li> <!----> <li class="li-footer__item font-sans text-xs text-color-text-low-emphasis flex flex-shrink-0 justify-start p-1 relative w-50% papabear:justify-center papabear:w-auto"> <div class="collapsible-dropdown collapsible-dropdown--footer collapsible-dropdown--up flex items-center relative hyphens-auto language-selector z-2"> <!----> <ul class="collapsible-dropdown__list hidden container-raised absolute w-auto overflow-y-auto flex-col items-stretch z-1 bottom-[100%] top-auto" role="menu" tabindex="-1"> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="العربية (Arabic)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-ar_AE" data-locale="ar_AE" role="menuitem" lang="ar_AE"> العربية (Arabic) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="বাংলা (Bangla)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-bn_IN" data-locale="bn_IN" role="menuitem" lang="bn_IN"> বাংলা (Bangla) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Čeština (Czech)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-cs_CZ" data-locale="cs_CZ" role="menuitem" lang="cs_CZ"> Čeština (Czech) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Dansk (Danish)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-da_DK" data-locale="da_DK" role="menuitem" lang="da_DK"> Dansk (Danish) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Deutsch (German)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-de_DE" data-locale="de_DE" role="menuitem" lang="de_DE"> Deutsch (German) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Ελληνικά (Greek)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-el_GR" data-locale="el_GR" role="menuitem" lang="el_GR"> Ελληνικά (Greek) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="English (English) selected" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link--selected" data-tracking-control-name="language-selector-en_US" data-locale="en_US" role="menuitem" lang="en_US"> <strong>English (English)</strong> </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Español (Spanish)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-es_ES" data-locale="es_ES" role="menuitem" lang="es_ES"> Español (Spanish) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="فارسی (Persian)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-fa_IR" data-locale="fa_IR" role="menuitem" lang="fa_IR"> فارسی (Persian) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Suomi (Finnish)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-fi_FI" data-locale="fi_FI" role="menuitem" lang="fi_FI"> Suomi (Finnish) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Français (French)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-fr_FR" data-locale="fr_FR" role="menuitem" lang="fr_FR"> Français (French) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="हिंदी (Hindi)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-hi_IN" data-locale="hi_IN" role="menuitem" lang="hi_IN"> हिंदी (Hindi) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Magyar (Hungarian)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-hu_HU" data-locale="hu_HU" role="menuitem" lang="hu_HU"> Magyar (Hungarian) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Bahasa Indonesia (Indonesian)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-in_ID" data-locale="in_ID" role="menuitem" lang="in_ID"> Bahasa Indonesia (Indonesian) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Italiano (Italian)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-it_IT" data-locale="it_IT" role="menuitem" lang="it_IT"> Italiano (Italian) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="עברית (Hebrew)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-iw_IL" data-locale="iw_IL" role="menuitem" lang="iw_IL"> עברית (Hebrew) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="日本語 (Japanese)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-ja_JP" data-locale="ja_JP" role="menuitem" lang="ja_JP"> 日本語 (Japanese) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="한국어 (Korean)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-ko_KR" data-locale="ko_KR" role="menuitem" lang="ko_KR"> 한국어 (Korean) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="मराठी (Marathi)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-mr_IN" data-locale="mr_IN" role="menuitem" lang="mr_IN"> मराठी (Marathi) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Bahasa Malaysia (Malay)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-ms_MY" data-locale="ms_MY" role="menuitem" lang="ms_MY"> Bahasa Malaysia (Malay) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Nederlands (Dutch)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-nl_NL" data-locale="nl_NL" role="menuitem" lang="nl_NL"> Nederlands (Dutch) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Norsk (Norwegian)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-no_NO" data-locale="no_NO" role="menuitem" lang="no_NO"> Norsk (Norwegian) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="ਪੰਜਾਬੀ (Punjabi)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-pa_IN" data-locale="pa_IN" role="menuitem" lang="pa_IN"> ਪੰਜਾਬੀ (Punjabi) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Polski (Polish)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-pl_PL" data-locale="pl_PL" role="menuitem" lang="pl_PL"> Polski (Polish) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Português (Portuguese)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-pt_BR" data-locale="pt_BR" role="menuitem" lang="pt_BR"> Português (Portuguese) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Română (Romanian)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-ro_RO" data-locale="ro_RO" role="menuitem" lang="ro_RO"> Română (Romanian) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Русский (Russian)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-ru_RU" data-locale="ru_RU" role="menuitem" lang="ru_RU"> Русский (Russian) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Svenska (Swedish)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-sv_SE" data-locale="sv_SE" role="menuitem" lang="sv_SE"> Svenska (Swedish) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="తెలుగు (Telugu)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-te_IN" data-locale="te_IN" role="menuitem" lang="te_IN"> తెలుగు (Telugu) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="ภาษาไทย (Thai)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-th_TH" data-locale="th_TH" role="menuitem" lang="th_TH"> ภาษาไทย (Thai) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Tagalog (Tagalog)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-tl_PH" data-locale="tl_PH" role="menuitem" lang="tl_PH"> Tagalog (Tagalog) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Türkçe (Turkish)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-tr_TR" data-locale="tr_TR" role="menuitem" lang="tr_TR"> Türkçe (Turkish) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Українська (Ukrainian)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-uk_UA" data-locale="uk_UA" role="menuitem" lang="uk_UA"> Українська (Ukrainian) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Tiếng Việt (Vietnamese)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-vi_VN" data-locale="vi_VN" role="menuitem" lang="vi_VN"> Tiếng Việt (Vietnamese) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="简体中文 (Chinese (Simplified))" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-zh_CN" data-locale="zh_CN" role="menuitem" lang="zh_CN"> 简体中文 (Chinese (Simplified)) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="正體中文 (Chinese (Traditional))" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-zh_TW" data-locale="zh_TW" role="menuitem" lang="zh_TW"> 正體中文 (Chinese (Traditional)) </button> </li> <!----> </ul> <button class="language-selector__button select-none relative pr-2 font-sans text-xs font-bold text-color-text-low-emphasis hover:text-color-link-hover hover:cursor-pointer focus:text-color-link-focus focus:outline-dotted focus:outline-1" aria-expanded="false" data-tracking-control-name="footer-lang-dropdown_trigger"> <span class="language-selector__label-text mr-0.5 break-words"> Language </span> <icon class="language-selector__label-chevron w-2 h-2 absolute top-0 right-0" data-delayed-url="https://static.licdn.com/aero-v1/sc/h/cyolgscd0imw2ldqppkrb84vo"></icon> </button> </div> </li> </ul> <!----> </footer> <script src="https://static.licdn.com/aero-v1/sc/h/eh08muqvrde4h3hc6koyij5ti" async></script> <!----> </body> </html>

Pages: 1 2 3 4 5 6 7 8 9 10