# How to Ensure Better Email Deliverability Rates? Your domain reputation is one of your most valuable marketing assets. Good email deliverability isn't just about having email IDs—it's about how and who you email. This guide will help your team safely and effectively use contact data (especially developer identities) in your outreach workflows. *** ### Understanding Reo.Dev's Contact Data Points Reo.Dev provides multiple data points that enable different types of marketing campaigns: #### **What Data We Provide** * **Named Companies** – Revealed accounts showing intent * **Named Developers** – Individual developer profiles with activity signals * **LinkedIn Profile URLs** – Professional profiles for social outreach * **Business Emails** – Verified work email addresses * **Personal Emails** – Only when provided directly by the person through first-party assets (website forms, product signups, etc.) #### **Multi-Channel Activation Options** Each data type opens up different outreach channels: | **Data Type** | **Campaign Channels** | **Best Use Case** | | --------------- | ------------------------------------------ | ---------------------------------------------------------------------- | | Named Companies | LinkedIn Ads, Google Display Network (GDN) | Increase brand awareness and digital impressions among target accounts | | LinkedIn URLs | LinkedIn cold outreach, InMail campaigns | Direct professional networking and engagement | | Business Emails | Email marketing, cold outbound sequences | Personalized 1:1 outreach and nurture campaigns | Each channel comes with its own nuances and best practices—especially email, where strict spam filters and deliverability algorithms can impact your domain reputation. *** ### Signal Strength: Understanding Data Maturity Not all intent signals are created equal. The number and type of signals an account shows directly impacts campaign success rates. #### **Single-Source Signals (Lower Maturity)** When an account or developer is revealed from **only one intent source**—like hiring signals or a single GitHub repository interaction—we consider this lower signal maturity (in comparison to compounded intent signals). **Recommended approach:** * **Start with awareness campaigns**: Run LinkedIn Ads or GDN to increase brand visibility * **Build engagement gradually**: Drive prospects to engage with your website, product docs, or product itself * **Move them down the funnel**: As they show deeper interest, they become warmer prospects for email and LinkedIn outreach #### **Multi-Source Signals (Higher Maturity)** When prospects show **2+ different intent signals**—for example, they've starred your GitHub repo AND visited your documentation—this indicates stronger buying intent and higher receptivity to direct outreach. **Why it matters:** * Multiple touchpoints signal genuine interest * Higher likelihood of positive response to email/LinkedIn campaigns * Reduced risk of being marked as spam {% hint style="info" %} **Important Note:** While multi-source signals are the ideal threshold, this isn't a hard rule. Many Reo.Dev customers have achieved strong results with single-source campaigns by following best practices and running well-crafted, non-spammy outreach.\ \ **Success Story:** [Kubegrade](https://www.reo.dev/customer-stories/kubegrade) achieves 50%+ positive response rates on LinkedIn outbound campaigns using GitHub repository data alone—proof that good execution matters more than perfect data conditions. {% endhint %} #### **The General Thumbrule** When prospects engage with your ads, visit your website multiple times, interact with your docs, or show product interest—these combined signals make them significantly more likely to respond positively to your email and LinkedIn campaigns. *** ### Email Deliverability Best Practices Email deliverability is heavily influenced by sender practices, domain configuration, list hygiene, and sender reputation. Follow these guidelines to protect your domain health while running effective campaigns. #### **✅ Do's: What You Should Do** **1. Authenticate Your Sending Domains** Ensure all sender domains have proper authentication records configured: * **SPF (Sender Policy Framework)** – Authorizes which mail servers can send on your behalf * **DKIM (DomainKeys Identified Mail)** – Adds a digital signature to verify email authenticity * **DMARC (Domain-based Message Authentication)** – Tells receiving servers how to handle emails that fail SPF/DKIM checks **Why it matters:** ISPs use these records to verify you're a legitimate sender, drastically improving inbox placement rates. **2. Use High-Quality TLD Domains** Stick with reputable top-level domains (TLDs) like .com, .io, .net, or .co. **Avoid low-credibility TLDs** that are often flagged as spam: * .xyz * .top * .info * .click * .loan * .work **Why it matters:** Certain TLDs have higher spam association rates, causing ISPs to filter them more aggressively. **3. Warm Up Your Sending Inboxes** Before launching campaigns, gradually increase your sending volume using email warm-up tools like [Instantly.ai](https://instantly.ai/) or similar platforms. **Why it matters:** Sudden high-volume sending from a new or cold inbox triggers spam filters. Warm-up tools simulate natural email activity to build sender reputation. **4. Use Professional Sender Identities** Your sender profile matters. Ensure: * **Real person's name** (not "Marketing Team" or "Sales Dept") * **Profile picture** on linked accounts * **Valid reply-to email** that's monitored * **Domain redirects** to your main website **Why it matters:** Recipients and spam filters trust emails from real people, not faceless entities. **5. Personalize Your Emails** Generic, templated emails get marked as spam. Personalization signals genuine interest and relevance. **Best practices:** * Use recipient's first name, company name, and relevant context * Reference specific activities or signals (e.g., "I noticed you starred our repo") * Tailor messaging to their role or use case **Why it matters:** Personalized emails have higher open rates, engagement rates, and lower spam complaints. **6. Avoid Links in First Emails (Especially Cold Outreach)** For cold outreach, keep your first email clean and link-free. Links—especially multiple links or shortened URLs—are red flags for spam filters. **Why it matters:** Reduces the likelihood of being filtered as spam, especially when reaching out to cold audiences. **7. Validate Emails Before Sending** Run your email list through an email verification tool like [NeverBounce](https://www.neverbounce.com/) or similar services to: * Remove invalid email addresses * Flag risky emails (role-based, disposable, catch-all domains) * Reduce bounce rates **Why it matters:** High bounce rates damage sender reputation. Clean lists = better deliverability. **8. Include Clear Unsubscribe Options** Make it easy for recipients to opt out. Include an unsubscribe link in every marketing email. **Why it matters:** Required by CAN-SPAM and GDPR compliance. Also prevents spam complaints, which hurt deliverability more than unsubscribes. **9. Start Small: Test with Under 500 Contacts** For your first campaign, limit your list to **under 500 contacts**. Monitor performance before scaling. **Why it matters:** Allows you to catch issues early (bad copy, deliverability problems, targeting mismatches) before damaging your sender reputation at scale. **10. A/B Test Your Personalization** Test different personalization angles to see what resonates: * Subject line variations * Opening lines * Call-to-action phrasing * Timing and cadence **Why it matters:** Small improvements in engagement (opens, clicks, replies) compound over time and signal to ISPs that your emails are wanted. **11. Create Developer-Friendly Content (Value > Pitch)** When reaching out to developers and technical end-users, focus on **education and value**, not sales pitches. **Best practices:** * Share relevant resources, guides, or tools * Offer to help solve a specific problem * Reference the technical context they care about * Invite them to training workshops/webinars that help. them upskill {% hint style="success" %} **Need inspiration?** Check out our [cold outreach email and LinkedIn templates](https://roverly.notion.site/Templates-for-cold-outreach-via-Email-and-Linkedin-29133e0c3ba280068e83c98030759a9a?pvs=74) designed specifically for developer audiences. {% endhint %} **Why it matters:** Developers are notoriously averse to sales pitches. Value-first approaches earn trust and engagement. **12. Prioritize Multi-Signal Audiences** Whenever possible, target contacts with **at least 2 different intent signals**—for example, developers who've both starred your repository AND visited your documentation. **Why it matters:** Multi-signal audiences are warmer, more receptive, and more likely to engage positively—reducing spam risk and improving campaign ROI. **13. Monitor Domain Health with Google Postmaster** Set up [Google Postmaster Tools](https://www.gmail.com/postmaster/) for your sending domains and conduct regular audits to monitor: * Domain reputation score * IP reputation * Spam rate * Delivery errors **Why it matters:** Proactive monitoring helps you catch deliverability issues before they snowball into major sender reputation damage. *** #### **❌ Don'ts: What You Should Avoid** **1. Don't Use Your Primary Website Domain for Outreach** **Never** send marketing or cold outbound emails from your main website domain (e.g., yourcompany.com). **Why it matters:** If your outreach domain is flagged or blacklisted, it affects your entire digital presence—including transactional emails, customer communications, and even your domain authority for SEO. **Best practice:** Use a subdomain (e.g., mail.yourcompany.com) or a separate domain for outreach campaigns. **2. Don't Blast Cold Lists of Unknown Developers** Sending mass emails to developers you've never engaged with is a fast track to spam folders and blacklists. **Why it matters:** Developers are highly sensitive to unsolicited outreach. High spam complaint rates destroy sender reputation. **3. Don't Skip Email Validation** Sending to unverified email addresses results in high bounce rates, which ISPs interpret as poor list hygiene—a direct hit to your sender reputation. **Why it matters:** Email validation is a small upfront cost that protects your long-term deliverability. **4. Don't Send High Volume on Day 1** Ramping up too quickly—especially from a new or cold inbox—triggers spam filters and ISP throttling. **Why it matters:** ISPs monitor for suspicious sending patterns. Gradual ramp-up is critical for inbox placement. **5. Don't Use "noreply@" or Generic Sender Names** Generic sender identities like "" or "Marketing Team" signal automated, impersonal outreach. **Why it matters:** Recipients are less likely to engage, and spam filters penalize emails that discourage replies. *** ### Pre-Send Checklist: Before You Hit Send Use this checklist to validate your campaign setup before launching: #### **Domain & Authentication** * \[ ] Domain authenticated (SPF/DKIM/DMARC records configured) * \[ ] Using a subdomain or separate domain (not primary website domain) * \[ ] High-quality TLD domain (.com, .io, .net) #### **Email Validation & List Quality** * \[ ] Email IDs validated with the verification tool * \[ ] List size is under 500 for the first campaign * \[ ] Removed bounced, unsubscribed, or inactive emails from previous campaigns #### **Sender Identity** * \[ ] Real person's name as sender * \[ ] Valid reply-to email address * \[ ] Professional email signature included #### **Audience Warmth & Targeting** * \[ ] Audience has at least 2 intent signals (ideally) * \[ ] Contacts have been warmed through ads, LinkedIn, or community engagement (if possible) * \[ ] Segment focuses on engaged or known prospects (not purely cold) #### **Email Content** * \[ ] Personalization included (name, company, context) * \[ ] Content is developer-friendly: value-focused, not pitch-heavy * \[ ] No links in first email (for cold outreach) * \[ ] Clear call-to-action included #### **Compliance & Deliverability** * \[ ] Unsubscribe link included * \[ ] Sending volume throttled (gradual ramp-up plan in place) * \[ ] Inbox warmed up using the warm-up tool * \[ ] A/B test plan ready for subject lines and personalization angles #### **Monitoring Setup** * \[ ] Google Postmaster Tools configured for domain monitoring * \[ ] Tracking metrics ready: open rate, reply rate, bounce rate, spam rate *** ### Additional Resources #### **Learn More About Outbound Campaigns** We hosted a comprehensive webinar on **LinkedIn outbound campaigns**, but the principles of messaging, list building, and account research also apply to email campaigns. 🔗 [**Watch the LinkedIn Outreach Playbook**](https://www.reo.dev/resources/linkedin-outreach-playbook) #### **Related Guides** * [Run Bulk Email Campaigns in Reo.Dev](https://docs.reo.dev/campaigns/run-bulk-email-campaigns) * [How to Integrate Apollo.io with Reo.Dev](https://docs.reo.dev/faqs-troubleshooting/broken-reference) * [How to Integrate Outreach.io with Reo.Dev](https://docs.reo.dev/faqs-troubleshooting/broken-reference) * [How to Integrate Salesloft with Reo.Dev](https://docs.reo.dev/faqs-troubleshooting/broken-reference) *** ### Key Takeaways Reo.Dev is committed to providing highly accurate, intent-based B2B contact data. However, **email deliverability is a shared responsibility. H**eavily influenced by sending practices, domain configuration, list hygiene, and sender reputation. By following the best practices outlined in this guide, you'll: * **Protect your domain reputation** and sender credibility * **Improve inbox placement rates** and campaign performance * **Build trust** with your prospects through thoughtful, personalized outreach * **Maximize ROI** from Reo.Dev's developer intelligence data Your goal should be to **build meaningful connections, not spam folders**. This playbook will help your team safely and effectively use contact data in your outreach workflows while product enhancements continue strengthening data quality at the source. *** ### Frequently Asked Questions #### Email Quality & Data Understanding
What quality checks does Reo run before showing email IDs to me? Reo.Dev runs three layers of quality checks on every email address: **1. Syntax Validation** We filter out emails with invalid syntax patterns (e.g., , abc.com, ). If our system detects such emails from any source—first-party form fills, website de-anonymisation, GitHub enrichment, or audience databases—we automatically rule them out. **2. Role-Based Email Classification** We identify and classify role-based emails (e.g., , ). Unlike syntax-invalid emails, we don't filter these out entirely. Instead, our system flags them with an icon in the UI so you can make informed decisions about whether to include them in your campaigns. **3. Email Verification via NeverBounce** We validate emails using [NeverBounce](https://www.neverbounce.com/) at two critical points: * **During data insertion** – When an email is first revealed in our platform from any source * **Upcoming Enhancement (will be live by mid-December 2025):**** At data export** – When you download CSVs, use our API, sync to CRM, trigger webhooks, use Zapier, or sync to Apollo.io, Outreach, or Salesloft This dual-verification approach ensures you're always working with the most accurate contact data.
How do I know if an email ID from Reo is valid or verified? All email addresses in Reo.Dev are automatically verified through [NeverBounce](https://www.neverbounce.com/) at two stages: 1. **During data insertion** – When the email is first captured in our system 2. **Upcoming Enhancement (will be live by mid-December 2025)**** At data export** – When you export contacts via CSV download, API, CRM sync, webhooks, Zapier, or our native integrations with Apollo.io, Outreach, or Salesloft (**Upcoming Enhancement - will be live by mid-December 2025)** \ \ When you export data, we also provide a detailed report showing: * Total number of emails exported * Number of emails excluded (and why) * Most common reason: The email is no longer valid This transparency helps you understand your list quality before launching campaigns.
Does Reo filter out role-based or catch-all email addresses? **Role-based emails**: We **do not filter out** role-based emails (e.g., , ). Instead, our system identifies and classifies them, displaying a flag icon next to these emails in the UI. This allows you to decide whether to include them based on your campaign strategy. **Syntax-invalid emails**: We **do filter out** emails with invalid syntax patterns (e.g., abc.com, ) to ensure list quality.
How fresh/recent are the email addresses provided by Reo? Reo.Dev performs periodic refreshes of developer profiles based on new activity captured in our system. **Refresh frequency varies by activity level**: * **High-activity developers**: Profiles can be refreshed within a month if the developer continues showing new activity (GitHub actions, doc visits, product interactions, etc.) * **Low-activity developers**: If a developer was identified a year ago (e.g., via a GitHub star) but hasn't shown additional activity since, we may not refresh that profile as frequently Our system continuously monitors for new signals and updates contact information accordingly, ensuring you have the most recent details for actively engaged developers.
What's the typical accuracy rate of email IDs from Reo? Reo.Dev maintains an email accuracy rate of **approximately 95%+**. However, actual deliverability can also depend on campaign execution factors: * List hygiene (removing unsubscribed or suppressed contacts) * Filtering out role-based emails * Email warm-up and sender reputation * Domain authentication (SPF/DKIM/DMARC) * Personalization and content quality Following the best practices outlined in this guide will help you achieve optimal deliverability rates with Reo's data.
*** #### Deliverability Issues
I ran a campaign and saw high bounce rates - why is this happening? High bounce rates typically result from a combination of factors, most of which are related to campaign setup and execution rather than data quality alone: **Common causes**: * **Sending from a cold or new domain** without proper warm-up * **Missing domain authentication** (SPF/DKIM/DMARC not configured) * **High send velocity on day 1** triggering ISP spam filters * **Not removing unsubscribed or suppressed contacts** from previous campaigns * **Including role-based or catch-all emails** without validation * **Targeting single-source signal contacts** who haven't engaged with your brand yet * **Using low-quality TLD domains** (.xyz, .top, .info, etc.) **How to fix it**: 1. Review the Pre-Send Checklist in this guide 2. Validate your list with a tool like [NeverBounce](https://www.neverbounce.com/) 3. Start with a smaller list (under 500 contacts) and gradually scale 4. Ensure proper domain warm-up using tools like [Instantly.ai](https://instantly.ai/) 5. Target multi-signal audiences who've already engaged with your brand
What bounce rate should I expect when using Reo's email data? Bounce rates can vary significantly based on your campaign setup and execution—ranging from **less than 1% to 10%+**. **Factors that influence bounce rates**: * Domain authentication and warm-up status * List hygiene and validation practices * Audience warmth (single-source vs. multi-source signals) * Whether you've removed role-based, unsubscribed, or suppressed contacts * Sender reputation and domain health * Email sending platform and throttling configuration **Best-case scenario**: Following all best practices outlined in this guide, our customers typically see bounce rates **under 2%**. **If your bounce rate exceeds 10%**, review your campaign setup against the Pre-Send Checklist and consider starting with a smaller, more targeted segment.
What deliverability rate can I expect from Reo's email data? When following all recommended best practices and conducting a manual list review before sending, Reo.Dev customers have achieved deliverability rates as high as **98%+**. **Deliverability depends on multiple factors**: * **Your sending infrastructure**: Domain reputation, warm-up status, authentication records * **Email platform**: Apollo.io, Outreach, Salesloft, or custom tools * **List quality**: Removing role-based, unsubscribed, and suppressed contacts * **Content quality**: Personalization, developer-friendly messaging, value-first approach * **Audience warmth**: Multi-source signals perform better than single-source * **Sending practices**: Gradual ramp-up, throttling, A/B testing The best approach is to start small, monitor performance, and scale gradually once you've validated your setup and messaging.
*** #### Campaign Setup & Technical Requirements
Do I need to validate emails from Reo before sending, or are they already verified? **Emails are already verified** in Reo.Dev using [NeverBounce](https://www.neverbounce.com/) during both data insertion and export (**upcoming enhancement - will be live by mid-December 2025)**. However, **we still recommend manual review** as a best practice before launching campaigns: **Manual verification checklist**: * Review and remove role-based emails (support@, contact@, info@) * Exclude unsubscribed or suppressed contacts from previous campaigns * Filter out catch-all email addresses if your campaign is highly targeted * Start with a small list (under 500 contacts) * Ensure you're sending from a high-reputation, warmed-up domain These additional checks significantly increase deliverability rates and ensure your emails land in the inbox rather than spam folders.
Can I use any email sending platform with Reo data? **Yes, you can use any email sending platform.** **Native integrations**: Reo.Dev has built-in integrations with: * Apollo.io * Outreach.io * Salesloft **Other platforms**: If you use a different email platform, you can connect it via: * **Zapier integration** – For workflow automation * **Webhooks** – For real-time data syncing * **CSV export** – Download contacts and upload to your platform manually * **API** – For custom integrations This flexibility ensures you can use Reo.Dev with your existing tech stack.
*** #### Scaling & Volume
How do I scale up my marketing campaigns for emails found from Reo? Scaling email campaigns successfully requires a methodical approach: **1. Start with clean, segmented lists** * Create segments of highly engaged developers (multi-source signals) * Remove unsubscribed, suppressed, and role-based contacts * Focus on recent activity and high intent **2. Personalize based on relevancy** * Tailor messaging to specific developer activities (GitHub stars, doc visits, etc.) * Reference account context and use cases * Lead with value, not sales pitches **3. Validate your setup** * Ensure all items in the Pre-Send Checklist are complete * Authenticate domains (SPF/DKIM/DMARC) * Warm up sending inboxes **4. Test with micro-campaigns first** * Run small campaigns (under 500 contacts) * Monitor positive response rates, meeting bookings, and engagement * Iterate on messaging and targeting **5. Scale gradually** * Only increase volume after proving campaign effectiveness * Add more sending domains/inboxes if needed * Continue monitoring domain health via [Google Postmaster](https://www.gmail.com/postmaster/) **Critical rule**: Don't scale campaigns that aren't working. Fix messaging and targeting first, then scale.
How many emails should I send in my first campaign? We recommend keeping your first campaign **under 500 contacts**. **Why start small?** * Allows you to test messaging and targeting without risking domain reputation * Helps you identify deliverability issues early * Provides statistically meaningful data on open rates, reply rates, and engagement * Protects your sender reputation while you validate your setup Once you've achieved positive results (high open rates, low bounce rates, positive replies), you can gradually scale to larger lists.
How quickly can I ramp up my sending volume? With the right infrastructure, you can ramp up sending volume within **2–3 weeks**.**How to scale quickly**: * Use multiple email inboxes and sending domains * Leverage email warm-up tools like Instantly.ai to accelerate reputation building * Follow a gradual ramp-up schedule (don't jump from 50 to 5,000 emails overnight) **Recommended resource**: [🔗 Instantly Cold Email Strategy Guide​](https://help.instantly.ai/en/articles/5975326-instantly-cold-email-strategy) This guide provides a detailed ramp-up schedule and best practices for scaling email volume safely.
What's the maximum number of emails I can send per day? There's **no hard cap** on daily email volume. It depends on your email sending infrastructure and list quality. **With a robust setup**, you can send **up to 2,100+ emails per day.** **Requirements for high-volume sending**: * Multiple warmed-up email inboxes * Proper domain authentication (SPF/DKIM/DMARC) * Clean, validated lists * Email sending infrastructure optimized for deliverability * Throttling and scheduling are configured properly **Recommended resource**: 🔗 [DIY Email Setup Guide by Instantly.ai](https://instantly.ai/blog/diy-email-setup/) **Important caveat**: Only scale volume after you've validated that your messaging resonates and drives positive response rates. High volume with poor messaging will damage your domain reputation.
How do I avoid getting my domain blacklisted when scaling? Follow these critical practices to protect your domain reputation: **Domain setup**: * Never send from your primary website domain—use a subdomain or separate domain * Authenticate all sending domains (SPF/DKIM/DMARC) * Use high-quality TLDs (.com, .io, .net—avoid .xyz, .top, .info) **List hygiene**: * Validate emails before sending * Remove bounced, unsubscribed, and suppressed contacts * Exclude role-based emails for cold outreach **Sending practices**: * Warm up inboxes before sending high volume * Gradually increase send volume (don't spike suddenly) * Throttle daily send limits per inbox * Monitor bounce and spam complaint rates **Content quality**: * Personalize messaging * Provide value, not just pitches * Include clear unsubscribe options * Avoid spammy language and excessive links **Monitoring**: * Set up [Google Postmaster Tools](https://www.gmail.com/postmaster/) for domain health tracking * Regularly audit deliverability metrics * Address issues immediately if bounce rates or spam complaints rise
*** #### Targeting & Segmentation
What are intent signals and how should they affect my campaigns? **Intent signals** are behavioral indicators that show a developer or account is actively interested in your product or solution. **Examples of intent signals in Reo.Dev**: * GitHub repository stars, forks, or contributions * Documentation page visits * Product usage or trial signups * Website visits and engagement * Docker Image installs * Community participation (Slack, Discord, forums) * Hiring for roles related to your product * Enterprise/pricing page visits **Why signal strength matters**: **Single-source signals** (e.g., only GitHub activity): * Indicates awareness but lower commitment * Best approach: Start with awareness campaigns (LinkedIn Ads, GDN) to warm them up * Can work for direct outreach if messaging is excellent and highly personalized **Multi-source signals** (e.g., GitHub + doc visits + product trial): * Indicates genuine interest and evaluation * Much higher likelihood of a positive response to direct outreach * These are your warmest leads—prioritize them for email and LinkedIn campaigns **Campaign strategy**: Match your outreach intensity to signal strength. Warmer signals = more direct outreach. Colder signals = nurture first, then reach out.
Should I email everyone in my Reo list or segment them first? **Always segment your lists before sending.** **Why segmentation matters**: * Enables personalized, relevant messaging based on specific behaviors and context * Improves open rates, reply rates, and overall engagement * Reduces spam complaints and unsubscribes * Protects sender reputation by targeting only receptive audiences **How to segment effectively**: * **By intent signal strength**: Multi-source signals vs. single-source * **By activity type**: GitHub users vs. doc visitors vs. product trial users * **By recency**: Active in the last 7 days vs. 30 days vs. 90+ days * **By account fit**: Company size, industry, tech stack, hiring signals * **By developer role**: Engineers vs. DevOps vs. Architects **Avoid spray-and-pray**: Sending generic emails to unsegmented lists damages deliverability and wastes opportunities to build genuine relationships with high-intent prospects.
What's the difference between single-source and multi-source signals? **Single-source signals** indicate a prospect has engaged with your brand through **only one channel or activity type**. **Examples**: * Only starred your GitHub repository * Only visited your documentation once * Only appeared in a hiring signal **Characteristics**: * Lower signal maturity—they're aware of you but not deeply engaged * Higher risk for cold outreach—may not recognize your brand yet * Best strategy: Nurture with ads or content before direct outreach *** **Multi-source signals** indicate a prospect has engaged through **two or more channels or activity types**. **Examples**: * Starred your GitHub repo AND visited your documentation * Visited docs multiple times AND signed up for a product trial * Engaged on GitHub AND participated in your community Slack **Characteristics**: * Higher signal maturity—demonstrates genuine interest and active evaluation * Warmer prospects—much more receptive to direct outreach * Best strategy: Prioritize for email and LinkedIn campaigns with personalized messaging **Key takeaway**: Multi-source signals indicate stronger buying intent and should be prioritized for direct outreach campaigns.
How do I prioritize which contacts to email first? **Prioritize contacts based on these three factors**: **1. Activity volume** * How many actions has the developer taken? (GitHub stars, doc visits, product usage, etc.) * Higher activity = stronger interest **2. Recency** * When was their most recent activity? * Activity in the last 7–14 days is significantly warmer than 90+ days ago **3. Signal diversity** * How many different channels have they engaged with? * Multi-source signals (GitHub + docs + product) indicate serious evaluation **Prioritization formula**: **Highest priority** = High volume + Recent activity + Multiple signal sources **Medium priority** = Moderate volume + Recent activity + Single signal source **Lower priority** = Low volume + Old activity + Single signal source **Pro tip**: Start by creating a segment in Reo.Dev that filters for developers with: * Activity in the last 14 days * At least 2 different signal sources * High activity scores These are your warmest, highest-intent leads—reach out to them first with highly personalized messaging referencing their specific activities.
*** **Need Help?** If you have questions about best practices, campaign setup, or optimizing your outreach strategy, reach out to our team at or through the in-app chat.