{"id":8861,"date":"2026-03-18T14:05:32","date_gmt":"2026-03-18T14:05:32","guid":{"rendered":"https:\/\/phantombuster.com\/blog\/?p=8861"},"modified":"2026-03-18T14:05:32","modified_gmt":"2026-03-18T14:05:32","slug":"reference-linkedin-context-without-sounding-like-you-scraped-it","status":"publish","type":"post","link":"https:\/\/phantombuster.com\/blog\/linkedin-automation\/reference-linkedin-context-without-sounding-like-you-scraped-it\/","title":{"rendered":"How to reference LinkedIn context in outreach without sounding like you scraped it"},"content":{"rendered":"<p>Most cold outreach tries too hard to prove it did its homework. You&#8217;ve seen the formula: mention a recent post, reference a job title, or drop a &#8220;congrats on the promotion.&#8221; In such cases, outreach feels &#8220;list-built&#8221; when you state an obvious fact about someone, then pivot straight into a pitch. Most prospects have seen that pattern enough times to recognize it instantly.<\/p>\n<p>On the surface, that counts as personalization. Yet many of these messages still feel strangely mechanical, almost as if the line about the post or role was pulled from a spreadsheet.<\/p>\n<p>The reason is subtle. Adding context does not automatically make a message sound human. When the structure of the message stays identical and only a few details change, the personalization becomes easy to recognize.<\/p>\n<p>In the sections below, we&#8217;ll look at how to reference LinkedIn signals in a way that feels natural, avoids the &#8220;list message&#8221; effect, and makes your outreach sound like it was written for one specific person.<\/p>\n<h2>Why outreach feels templated, and why it matters<\/h2>\n<p>Most outreach feels robotic because it follows a predictable &#8220;Logic + Variable&#8221; formula that prospects have been trained to ignore. Here is why your outreach feels templated:<\/p>\n<ul>\n<li>Many senders use a LinkedIn detail simply to prove they visited the profile, rather than using it to justify the message. If your personalization doesn&#8217;t actually connect to your pitch, it feels like a chore you completed just to get to the selling part.<\/li>\n<li>Most automated tools use the same sentence structures: <em>&#8220;I saw your [Post] about [Topic] and thought&#8230;&#8221;<\/em> When a prospect sees that specific phrasing for the tenth time that week, their brain registers it as noise before they even finish the sentence.<\/li>\n<li>When you sound like every other SDR in their inbox, you&#8217;ve already lost. Even if your product is a strong fit, a templated intro makes your solution feel generic.<\/li>\n<li>Vague praise like <em>&#8220;Great insights on your recent article&#8221;<\/em> is a clear giveaway. Without a specific takeaway or a counter-opinion, it&#8217;s clear you&#8217;re checking a box rather than engaging with the content.<\/li>\n<\/ul>\n<p>Real conversations connect the observation to a reason for reaching out. Prospects and platforms respond to patterns, not the mere presence of profile data. For example, sending the same opener structure to 100 contacts in one day tends to draw fewer replies than varied openers spread over several days.\u00a0If your messages repeat the same shape, they&#8217;ll read automated even when the details are accurate.<\/p>\n<blockquote><p>LinkedIn doesn&#8217;t behave like a simple counter. It reacts to patterns over time. &#8211; PhantomBuster Product Expert, <a href=\"https:\/\/www.linkedin.com\/in\/brianejmoran\/\" target=\"_blank\" rel=\"noopener\">Brian Moran<\/a><\/p><\/blockquote>\n<h2>What is the bridge technique: observation, insight, relevance,\u00a0ask?<\/h2>\n<p>The core fix is simple: add a &#8220;bridge&#8221; between the observation and your ask.<\/p>\n<p>Use this structure:<\/p>\n<ol>\n<li><strong>Observation:<\/strong> what you saw (post, comment, job change)<\/li>\n<li><strong>Insight:<\/strong> what it made you think, notice, or question<\/li>\n<li><strong>Relevance:<\/strong> why that insight connects to your outreach<\/li>\n<li><strong>Ask:<\/strong> a low-pressure question or next step<\/li>\n<\/ol>\n<p>Most outreach skips steps 2 and 3. That gap is why a message can feel like variable insertion.<\/p>\n<p><strong>Example without a bridge:<\/strong> &#8220;Saw your post about pipeline forecasting. We help sales teams improve forecast accuracy. Open to a chat?&#8221;<\/p>\n<p><strong>Example with a bridge:<\/strong>&#8220;Your post on pipeline forecasting stood out, especially the point about reps shifting commit dates. That usually shows up when the team has visibility but not timing discipline. Is that something you&#8217;re dealing with right now?&#8221;<\/p>\n<p>The &#8220;bridge&#8221; creates a human pause between what you noticed and what you want. It signals thought, not just data.<\/p>\n<h3>Bridge phrases that sound natural<\/h3>\n<p>These phrases signal a real thought process:<\/p>\n<ul>\n<li>&#8220;That stood out because\u2026&#8221;<\/li>\n<li>&#8220;It brings up a pattern we see a lot\u2026&#8221;<\/li>\n<li>&#8220;It raises a question\u2026&#8221;<\/li>\n<li>&#8220;Curious if that&#8217;s affecting how your team\u2026&#8221;<\/li>\n<li>&#8220;That lines up with what we&#8217;re hearing from\u2026&#8221;<\/li>\n<\/ul>\n<p>Use them to move from observation to insight. Rotate them across segments so your messages don&#8217;t all follow the same rhythm.<\/p>\n<h2>How to reference specific LinkedIn signals without forcing it<\/h2>\n<p>Different signals call for different phrasing. The goal is consistent: show what you noticed, show how you interpreted it, then ask a simple question.<\/p>\n<h3>How do you mention a post they wrote?<\/h3>\n<p>Anchor on one specific idea. Avoid generic praise.<\/p>\n<p><strong>Natural:<\/strong> &#8220;Your point about async communication in distributed teams stood out, especially the part on decision documentation. That&#8217;s where handoffs tend to break down when teams scale.&#8221;<\/p>\n<p><strong>Templated:<\/strong><br \/>\n&#8220;Really enjoyed your recent post on LinkedIn.&#8221;<\/p>\n<p>The first version proves you read it. The second could apply to anyone.<\/p>\n<h3>How do you mention a comment they left?<\/h3>\n<p>Reference the topic of the thread and the substance of their take. Don&#8217;t make the comment itself the headline.<\/p>\n<p><strong>Natural:<\/strong> &#8220;Your comment on Sarah&#8217;s thread about RevOps handoffs was on point, CRM hygiene is often the real constraint. When it&#8217;s treated as admin work, forecasting and routing usually suffer.&#8221;<\/p>\n<p><strong>Templated:<\/strong><br \/>\n&#8220;Saw you commented on a post about RevOps.&#8221;<\/p>\n<p>The first version shows you understood the conversation. The second only shows you saw activity.<\/p>\n<h3>How do you reference a mutual connection?<\/h3>\n<p>Add a real reason the connection matters. Otherwise it&#8217;s just name-dropping.<\/p>\n<p><strong>Natural:<\/strong> &#8220;Looks like we both know Marcus Chen. We worked together at Salesforce. His rule of thumb: outbound speed without targeting discipline burns lists fast.&#8221;<\/p>\n<p><strong>Templated:<\/strong><br \/>\n&#8220;Looks like we&#8217;re both connected to Marcus Chen.&#8221;<\/p>\n<p>The first version explains why the connection is relevant to the topic you&#8217;re raising.<\/p>\n<h3>How do you mention a job change or hiring signal?<\/h3>\n<p>Skip &#8220;Congrats on the new role.&#8221; Tie the change to a real operational constraint.<\/p>\n<p><strong>Natural:<\/strong><br \/>\n&#8220;Noticed you&#8217;re building out the sales team at Acme. That usually means pressure to ramp quickly without letting deal quality slide. How are you thinking about enablement in the first 60 to 90 days?&#8221;<\/p>\n<p><strong>Templated:<\/strong><br \/>\n&#8220;Congrats on the new role. We help companies like yours hire better.&#8221;<\/p>\n<p>The first version shows you understand the situation. The second reads like a canned opener.<\/p>\n<h2>What &#8220;template tells&#8221; should you remove?<\/h2>\n<p>Certain language patterns signal automation. In practice, removing these tells improves replies more than adding extra variables.<\/p>\n<table style=\"min-width: 75px;\">\n<colgroup>\n<col style=\"min-width: 25px;\" \/>\n<col style=\"min-width: 25px;\" \/>\n<col style=\"min-width: 25px;\" \/><\/colgroup>\n<tbody>\n<tr>\n<th colspan=\"1\" rowspan=\"1\">Template tell<\/th>\n<th colspan=\"1\" rowspan=\"1\">Why it reads automated<\/th>\n<th colspan=\"1\" rowspan=\"1\">Human alternative<\/th>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">Full legal company names (&#8220;Acme Corporation, Inc.&#8221;)<\/td>\n<td colspan=\"1\" rowspan=\"1\">Almost nobody writes that way in a message<\/td>\n<td colspan=\"1\" rowspan=\"1\">&#8220;Acme&#8221;<\/td>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">Exact job titles copied from the profile<\/td>\n<td colspan=\"1\" rowspan=\"1\">It feels pasted and overly formal<\/td>\n<td colspan=\"1\" rowspan=\"1\">&#8220;In your role&#8221; or a shortened title (&#8220;VP Sales&#8221;)<\/td>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">Generic flattery (&#8220;impressive profile&#8221;)<\/td>\n<td colspan=\"1\" rowspan=\"1\">No specifics, so it signals a template<\/td>\n<td colspan=\"1\" rowspan=\"1\">Reference one concrete detail you can point to<\/td>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">&#8220;I stumbled across\u2026&#8221;<\/td>\n<td colspan=\"1\" rowspan=\"1\">High-volume outreach and &#8220;stumbled&#8221; don&#8217;t match<\/td>\n<td colspan=\"1\" rowspan=\"1\">&#8220;Was looking at leaders in [industry] and your post on [topic] stood out because\u2026&#8221;<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>These tells don&#8217;t just make messages sound automated\u00a0\u2014 they can make them sound insincere. It&#8217;s better to remove them than to try to hide them with more personalization.<\/p>\n<h2>Copy-paste template: a natural opener you can adapt<\/h2>\n<p>Use this structure, then rewrite it in your own words per segment. Don&#8217;t send it as-is.<\/p>\n<blockquote><p>Subject: Question on [topic] at [company]<\/p><\/blockquote>\n<blockquote><p>Hi [Name],<\/p><\/blockquote>\n<blockquote><p>Your post\/comment on [topic] stood out, especially [specific detail].<\/p><\/blockquote>\n<blockquote><p>It raises a question we see often in [their context]: [your insight in one sentence].<\/p><\/blockquote>\n<blockquote><p>If it&#8217;s relevant, open to a quick comparison on how other teams handle [problem]?<\/p><\/blockquote>\n<blockquote><p>Best,<br \/>\n[Your Name]<\/p><\/blockquote>\n<p><strong>Note:<\/strong> If you&#8217;re sending this as a <a href=\"https:\/\/phantombuster.com\/blog\/outbound-sales\/linkedin-outreach-message-framework\/\" target=\"_blank\" rel=\"noopener\">LinkedIn connection note<\/a>, drop the subject line and sign-off to stay within the character limit.<\/p>\n<p><strong>Why this works:<\/strong><\/p>\n<ul>\n<li>It proves you read something real, not just the header of a profile<\/li>\n<li>It shows your reasoning before your offer<\/li>\n<li>It keeps the ask low-pressure and specific<\/li>\n<li>It avoids the most common template tells<\/li>\n<\/ul>\n<h2>Next step: build a repeatable context workflow<\/h2>\n<p>If you&#8217;re doing this weekly, treat it like a system, not a one-off writing exercise. Decide which signals you&#8217;ll use per segment, then define the bridge and ask you&#8217;ll rotate through.<\/p>\n<p>To scale this ethically, treat context as a system. This is where PhantomBuster supports the workflow: use PhantomBuster&#8217;s LinkedIn Automations \u2014 for example, the\u00a0<a href=\"https:\/\/phantombuster.com\/automations\/linkedin\/5589386912058181\/linkedin-profile-scraper\" target=\"_blank\" rel=\"noopener\">LinkedIn Profile Scraper<\/a>\u00a0automation\u00a0\u2014 to extract key public profile fields (headline, current role, company) and, where available, a small sample of recent activity.<\/p>\n<p>Schedule extractions to a Google Sheet or CSV so you can focus on writing the human part.\u00a0Instead of manually clicking through dozens of tabs, you update a single sheet with useful context signals\u2014 stated hiring needs, niche topics they\u00a0engaged with, or a short quote from a recent comment when relevant.\u00a0Store the minimum data required for outreach, and only process data you have permission to use within platform policies.<\/p>\n<p>Here&#8217;s a concrete workflow to implement this:<\/p>\n<ol>\n<li>Define signals to capture (e.g., role change, recent post topic, hiring note)<\/li>\n<li>Set up PhantomBuster&#8217;s LinkedIn Profile Scraper automation with Scheduler to extract those fields daily to Google Sheets or CSV<\/li>\n<li>Add columns for Observation, Insight, Relevance, and Ask; write one unique bridge per lead<\/li>\n<li>Cap daily sends (e.g., 30\u201350) and vary opener phrasing to avoid repetition patterns<\/li>\n<li>Review replies weekly and update the signal list based on what resonates<\/li>\n<\/ol>\n<h2>Frequently asked questions<\/h2>\n<h3>How can LinkedIn profile context be referenced without sounding like it came from a list?<\/h3>\n<p>LinkedIn context should be introduced as an observation rather than a data point. Start with one specific detail from the profile or recent activity, explain why it caught attention, then ask a short question. This sequence mirrors how real conversations start. One concrete signal plus a thoughtful question usually sounds more natural than stacking several variables from a bulk list.<\/p>\n<h3>What are the most common template signals in LinkedIn outreach messages?<\/h3>\n<p>Template signals usually appear as overly formal or generic language. Examples include full legal company names copied from profiles, job titles pasted exactly as written, empty compliments like &#8220;impressive profile,&#8221; and vague phrases such as &#8220;I came across your profile.&#8221; Replacing these with natural shorthand, one real observation, and a clear reason for reaching out reduces the impression of automation.<\/p>\n<h3>What bridge phrases make LinkedIn context feel conversational?<\/h3>\n<p>Bridge phrases work best when they reveal a thought process between the observation and the outreach. Phrases such as &#8220;That stood out because\u2026,&#8221; &#8220;It reminded me of a pattern we&#8217;re seeing\u2026,&#8221; or &#8220;Curious whether this shows up in your team\u2026&#8221; help transition from what was noticed to why the message was sent. These bridges create a pause that makes the interaction feel reflective rather than scripted.<\/p>\n<h3>Is it too intense to reference someone&#8217;s LinkedIn post or comment in a cold message?<\/h3>\n<p>Referencing a post or comment is usually effective when the reference stays focused and proportional. Mention one idea or takeaway from the post, connect it briefly to a broader industry pattern, and ask whether it resonates. Problems arise when outreach summarizes several posts or appears to analyze someone&#8217;s entire activity history.<\/p>\n<h3>What context can be used if a prospect has not posted recently?<\/h3>\n<p>When recent activity is unavailable, use low-intensity context signals that still make sense professionally. Examples include role responsibilities, team expansion signals, hiring patterns, product launches, or market shifts affecting that function. Instead of repeating profile facts, reference the implication of the role and invite correction or perspective.<\/p>\n<h3>How can a LinkedIn connection request note be personalized within the character limit?<\/h3>\n<p>A connection request note should focus on a single signal and a short bridge to a question. Treat the request as a permission step rather than a full pitch. A simple structure works well: acknowledge a specific observation, mention why it was interesting, and ask whether connecting would make sense.<\/p>\n<h3>Why does behavioral authenticity matter more than the source of the data?<\/h3>\n<p>Behavioral authenticity matters because recipients react to patterns that feel mass-produced. Repeated message structures, generic compliments, and immediate pitching can reduce credibility faster than the presence of LinkedIn data itself. Both human readers and platform systems often respond to repetition patterns rather than to the fact that a data point was used.<\/p>\n<blockquote><p>Automation should amplify good behavior, not replace judgment.&#8221; \u2014 PhantomBuster Product Expert, <a href=\"https:\/\/www.linkedin.com\/in\/brianejmoran\/\" target=\"_blank\" rel=\"noopener\">Brian Moran<\/a><\/p><\/blockquote>\n<h3>How can personalization be scaled without messages looking automated?<\/h3>\n<p>Scaling personalization requires separating data collection from message composition. Gather profile signals first, then rotate opening observations, bridge phrases, and questions across segments. Keep pacing consistent and avoid sending identical structures to large batches at once. Slight variations in wording and timing reduce repetitive patterns. For a deeper look at how top teams approach this, see how to <a href=\"https:\/\/phantombuster.com\/blog\/outbound-sales\/how-top-teams-scale-linkedin-outreach-without-losing-the-human-touch\/\" target=\"_blank\" rel=\"noopener\">scale LinkedIn outreach without losing the human touch<\/a>.<\/p>\n<blockquote><p>Avoid slide and spike patterns. Gradual ramps outperform sudden jumps.<br \/>\n\u2014 PhantomBuster Product Expert, <a href=\"https:\/\/www.linkedin.com\/in\/brianejmoran\/\" target=\"_blank\" rel=\"noopener\">Brian Moran<\/a><\/p><\/blockquote>\n<h2>Ready to scale thoughtful outreach?<\/h2>\n<p>Set up PhantomBuster&#8217;s LinkedIn Automations to extract permitted profile signals to a Google Sheet, then apply the Observation\u2013Insight\u2013Relevance\u2013Ask model in every opener. Start with 50 leads, measure reply rates, and iterate based on what works. The goal is sustainable personalization, not volume.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Learn how to reference LinkedIn context without sounding like you scraped it using the bridge technique (observation, insight, ask), remove template tells, and boost replies.&#8221;<\/p>\n","protected":false},"author":11,"featured_media":9846,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[55],"tags":[35],"class_list":["post-8861","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-linkedin-automation","tag-generate-leads"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v26.8 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>How to reference LinkedIn context in outreach without sounding like you scraped it<\/title>\n<meta name=\"description\" content=\"Learn how to reference LinkedIn context without sounding like you scraped it using the bridge technique (observation, insight, ask), remove template tells, and boost replies.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/phantombuster.com\/blog\/linkedin-automation\/reference-linkedin-context-without-sounding-like-you-scraped-it\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"How to reference LinkedIn context in outreach without sounding like you scraped it\" \/>\n<meta property=\"og:description\" content=\"Learn how to reference LinkedIn context without sounding like you scraped it using the bridge technique (observation, insight, ask), remove template tells, and boost replies.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/phantombuster.com\/blog\/linkedin-automation\/reference-linkedin-context-without-sounding-like-you-scraped-it\/\" \/>\n<meta property=\"og:site_name\" content=\"PhantomBuster Blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-03-18T14:05:32+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/phantombuster.com\/blog\/wp-content\/uploads\/2026\/03\/How-to-reference-LinkedIn-context-in-outreach-without-sounding-like-you-scraped-it.webp\" \/>\n\t<meta property=\"og:image:width\" content=\"1200\" \/>\n\t<meta property=\"og:image:height\" content=\"800\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/webp\" \/>\n<meta name=\"author\" content=\"Julia Estrella\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Julia Estrella\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"10 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":[\"Article\",\"BlogPosting\"],\"@id\":\"https:\/\/phantombuster.com\/blog\/linkedin-automation\/reference-linkedin-context-without-sounding-like-you-scraped-it\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/phantombuster.com\/blog\/linkedin-automation\/reference-linkedin-context-without-sounding-like-you-scraped-it\/\"},\"author\":{\"name\":\"Julia Estrella\",\"@id\":\"https:\/\/phantombuster.com\/blog\/#\/schema\/person\/0149648db8c80031f255d28011c506f3\"},\"headline\":\"How to reference LinkedIn context in outreach without sounding like you scraped it\",\"datePublished\":\"2026-03-18T14:05:32+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/phantombuster.com\/blog\/linkedin-automation\/reference-linkedin-context-without-sounding-like-you-scraped-it\/\"},\"wordCount\":2157,\"image\":{\"@id\":\"https:\/\/phantombuster.com\/blog\/linkedin-automation\/reference-linkedin-context-without-sounding-like-you-scraped-it\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/phantombuster.com\/blog\/wp-content\/uploads\/2026\/03\/How-to-reference-LinkedIn-context-in-outreach-without-sounding-like-you-scraped-it.webp\",\"keywords\":[\"generate-leads\"],\"articleSection\":[\"LinkedIn Automation\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/phantombuster.com\/blog\/linkedin-automation\/reference-linkedin-context-without-sounding-like-you-scraped-it\/\",\"url\":\"https:\/\/phantombuster.com\/blog\/linkedin-automation\/reference-linkedin-context-without-sounding-like-you-scraped-it\/\",\"name\":\"How to reference LinkedIn context in outreach without sounding like you scraped it\",\"isPartOf\":{\"@id\":\"https:\/\/phantombuster.com\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/phantombuster.com\/blog\/linkedin-automation\/reference-linkedin-context-without-sounding-like-you-scraped-it\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/phantombuster.com\/blog\/linkedin-automation\/reference-linkedin-context-without-sounding-like-you-scraped-it\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/phantombuster.com\/blog\/wp-content\/uploads\/2026\/03\/How-to-reference-LinkedIn-context-in-outreach-without-sounding-like-you-scraped-it.webp\",\"datePublished\":\"2026-03-18T14:05:32+00:00\",\"author\":{\"@id\":\"https:\/\/phantombuster.com\/blog\/#\/schema\/person\/0149648db8c80031f255d28011c506f3\"},\"description\":\"Learn how to reference LinkedIn context without sounding like you scraped it using the bridge technique (observation, insight, ask), remove template tells, and boost replies.\",\"breadcrumb\":{\"@id\":\"https:\/\/phantombuster.com\/blog\/linkedin-automation\/reference-linkedin-context-without-sounding-like-you-scraped-it\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/phantombuster.com\/blog\/linkedin-automation\/reference-linkedin-context-without-sounding-like-you-scraped-it\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/phantombuster.com\/blog\/linkedin-automation\/reference-linkedin-context-without-sounding-like-you-scraped-it\/#primaryimage\",\"url\":\"https:\/\/phantombuster.com\/blog\/wp-content\/uploads\/2026\/03\/How-to-reference-LinkedIn-context-in-outreach-without-sounding-like-you-scraped-it.webp\",\"contentUrl\":\"https:\/\/phantombuster.com\/blog\/wp-content\/uploads\/2026\/03\/How-to-reference-LinkedIn-context-in-outreach-without-sounding-like-you-scraped-it.webp\",\"width\":1200,\"height\":800,\"caption\":\"Image that explains how to reference LinkedIn context in outreach\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/phantombuster.com\/blog\/linkedin-automation\/reference-linkedin-context-without-sounding-like-you-scraped-it\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Blog\",\"item\":\"https:\/\/phantombuster.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"LinkedIn Automation\",\"item\":\"https:\/\/blogv2.phantombuster.com\/blog\/category\/linkedin-automation\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"How to reference LinkedIn context in outreach without sounding like you scraped it\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/phantombuster.com\/blog\/#website\",\"url\":\"https:\/\/phantombuster.com\/blog\/\",\"name\":\"PhantomBuster Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/phantombuster.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/phantombuster.com\/blog\/#\/schema\/person\/0149648db8c80031f255d28011c506f3\",\"name\":\"Julia Estrella\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/phantombuster.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/8dcbbffe9d8be201813e442dd111fd81339570cdb322e92b013bd46bd0b92dfc?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/8dcbbffe9d8be201813e442dd111fd81339570cdb322e92b013bd46bd0b92dfc?s=96&d=mm&r=g\",\"caption\":\"Julia Estrella\"},\"url\":\"https:\/\/phantombuster.com\/blog\/author\/julia-estrella\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"How to reference LinkedIn context in outreach without sounding like you scraped it","description":"Learn how to reference LinkedIn context without sounding like you scraped it using the bridge technique (observation, insight, ask), remove template tells, and boost replies.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/phantombuster.com\/blog\/linkedin-automation\/reference-linkedin-context-without-sounding-like-you-scraped-it\/","og_locale":"en_US","og_type":"article","og_title":"How to reference LinkedIn context in outreach without sounding like you scraped it","og_description":"Learn how to reference LinkedIn context without sounding like you scraped it using the bridge technique (observation, insight, ask), remove template tells, and boost replies.","og_url":"https:\/\/phantombuster.com\/blog\/linkedin-automation\/reference-linkedin-context-without-sounding-like-you-scraped-it\/","og_site_name":"PhantomBuster Blog","article_published_time":"2026-03-18T14:05:32+00:00","og_image":[{"width":1200,"height":800,"url":"https:\/\/phantombuster.com\/blog\/wp-content\/uploads\/2026\/03\/How-to-reference-LinkedIn-context-in-outreach-without-sounding-like-you-scraped-it.webp","type":"image\/webp"}],"author":"Julia Estrella","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Julia Estrella","Est. reading time":"10 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":["Article","BlogPosting"],"@id":"https:\/\/phantombuster.com\/blog\/linkedin-automation\/reference-linkedin-context-without-sounding-like-you-scraped-it\/#article","isPartOf":{"@id":"https:\/\/phantombuster.com\/blog\/linkedin-automation\/reference-linkedin-context-without-sounding-like-you-scraped-it\/"},"author":{"name":"Julia Estrella","@id":"https:\/\/phantombuster.com\/blog\/#\/schema\/person\/0149648db8c80031f255d28011c506f3"},"headline":"How to reference LinkedIn context in outreach without sounding like you scraped it","datePublished":"2026-03-18T14:05:32+00:00","mainEntityOfPage":{"@id":"https:\/\/phantombuster.com\/blog\/linkedin-automation\/reference-linkedin-context-without-sounding-like-you-scraped-it\/"},"wordCount":2157,"image":{"@id":"https:\/\/phantombuster.com\/blog\/linkedin-automation\/reference-linkedin-context-without-sounding-like-you-scraped-it\/#primaryimage"},"thumbnailUrl":"https:\/\/phantombuster.com\/blog\/wp-content\/uploads\/2026\/03\/How-to-reference-LinkedIn-context-in-outreach-without-sounding-like-you-scraped-it.webp","keywords":["generate-leads"],"articleSection":["LinkedIn Automation"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/phantombuster.com\/blog\/linkedin-automation\/reference-linkedin-context-without-sounding-like-you-scraped-it\/","url":"https:\/\/phantombuster.com\/blog\/linkedin-automation\/reference-linkedin-context-without-sounding-like-you-scraped-it\/","name":"How to reference LinkedIn context in outreach without sounding like you scraped it","isPartOf":{"@id":"https:\/\/phantombuster.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/phantombuster.com\/blog\/linkedin-automation\/reference-linkedin-context-without-sounding-like-you-scraped-it\/#primaryimage"},"image":{"@id":"https:\/\/phantombuster.com\/blog\/linkedin-automation\/reference-linkedin-context-without-sounding-like-you-scraped-it\/#primaryimage"},"thumbnailUrl":"https:\/\/phantombuster.com\/blog\/wp-content\/uploads\/2026\/03\/How-to-reference-LinkedIn-context-in-outreach-without-sounding-like-you-scraped-it.webp","datePublished":"2026-03-18T14:05:32+00:00","author":{"@id":"https:\/\/phantombuster.com\/blog\/#\/schema\/person\/0149648db8c80031f255d28011c506f3"},"description":"Learn how to reference LinkedIn context without sounding like you scraped it using the bridge technique (observation, insight, ask), remove template tells, and boost replies.","breadcrumb":{"@id":"https:\/\/phantombuster.com\/blog\/linkedin-automation\/reference-linkedin-context-without-sounding-like-you-scraped-it\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/phantombuster.com\/blog\/linkedin-automation\/reference-linkedin-context-without-sounding-like-you-scraped-it\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/phantombuster.com\/blog\/linkedin-automation\/reference-linkedin-context-without-sounding-like-you-scraped-it\/#primaryimage","url":"https:\/\/phantombuster.com\/blog\/wp-content\/uploads\/2026\/03\/How-to-reference-LinkedIn-context-in-outreach-without-sounding-like-you-scraped-it.webp","contentUrl":"https:\/\/phantombuster.com\/blog\/wp-content\/uploads\/2026\/03\/How-to-reference-LinkedIn-context-in-outreach-without-sounding-like-you-scraped-it.webp","width":1200,"height":800,"caption":"Image that explains how to reference LinkedIn context in outreach"},{"@type":"BreadcrumbList","@id":"https:\/\/phantombuster.com\/blog\/linkedin-automation\/reference-linkedin-context-without-sounding-like-you-scraped-it\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Blog","item":"https:\/\/phantombuster.com\/blog\/"},{"@type":"ListItem","position":2,"name":"LinkedIn Automation","item":"https:\/\/blogv2.phantombuster.com\/blog\/category\/linkedin-automation\/"},{"@type":"ListItem","position":3,"name":"How to reference LinkedIn context in outreach without sounding like you scraped it"}]},{"@type":"WebSite","@id":"https:\/\/phantombuster.com\/blog\/#website","url":"https:\/\/phantombuster.com\/blog\/","name":"PhantomBuster Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/phantombuster.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/phantombuster.com\/blog\/#\/schema\/person\/0149648db8c80031f255d28011c506f3","name":"Julia Estrella","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/phantombuster.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/8dcbbffe9d8be201813e442dd111fd81339570cdb322e92b013bd46bd0b92dfc?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/8dcbbffe9d8be201813e442dd111fd81339570cdb322e92b013bd46bd0b92dfc?s=96&d=mm&r=g","caption":"Julia Estrella"},"url":"https:\/\/phantombuster.com\/blog\/author\/julia-estrella\/"}]}},"_links":{"self":[{"href":"https:\/\/phantombuster.com\/blog\/wp-json\/wp\/v2\/posts\/8861","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/phantombuster.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/phantombuster.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/phantombuster.com\/blog\/wp-json\/wp\/v2\/users\/11"}],"replies":[{"embeddable":true,"href":"https:\/\/phantombuster.com\/blog\/wp-json\/wp\/v2\/comments?post=8861"}],"version-history":[{"count":4,"href":"https:\/\/phantombuster.com\/blog\/wp-json\/wp\/v2\/posts\/8861\/revisions"}],"predecessor-version":[{"id":9847,"href":"https:\/\/phantombuster.com\/blog\/wp-json\/wp\/v2\/posts\/8861\/revisions\/9847"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/phantombuster.com\/blog\/wp-json\/wp\/v2\/media\/9846"}],"wp:attachment":[{"href":"https:\/\/phantombuster.com\/blog\/wp-json\/wp\/v2\/media?parent=8861"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/phantombuster.com\/blog\/wp-json\/wp\/v2\/categories?post=8861"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/phantombuster.com\/blog\/wp-json\/wp\/v2\/tags?post=8861"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}