LogoLogo
API DocsChangelogPlaybooksLoginBook a Demo
  • Getting Started
    • Introduction to Reo.Dev
    • For Users
      • Step 1: Find active accounts to target
      • Step 2: Track developer activity on your target accounts
      • Step 3: Identify developers engaging with your product
      • Step 4: Build custom segments that are most likely to convert
      • Step 5: Use filters to spot high-intent leads
    • For Admins
      • Step 1: Identify active accounts to target
      • Step 2: Track developer activity on your target accounts
      • Step 3: Find developers engaging with your product
      • Step 4: Create custom segments that are most likely to convert
      • Step 5: Integrating data sources with Reo.Dev
      • Step 6: Integrate Slack and set up notifications
      • Step 7: Add Customer Fit Criteria
  • Accounts
    • Account Lifecycle Stage
    • Custom CRM Stages
    • Developer Funnel Stages
    • Account Activity Score
    • Tags
    • Customizing Tags
    • Custom Lists
    • Using the Lists API in Reo.Dev
    • Managing CRM Owners in Reo.Dev
    • Follow an Account
    • How to Set Up Notification Alerts for Accounts, Developers & Segments in Reo.Dev
    • Flag incorrect data
  • Developers
    • Interpreting Intel on the Developer view page
    • Developer Activity Score
    • How to Find Inbound Developers in Reo.Dev
  • Segments
    • Creating Segments
    • Basic & Advance Segments
    • Filters 101
    • Segment Actions
    • My Segments
    • Shared Segments
    • Magic Segments
    • Favourite Segment
    • Add notes for better collaboration and context
    • CSV Exports for Segments
    • 10 Advanced Segments to create to spot high-intent opportunities
  • Buyers
    • Find Buyer Contact
    • How to Find, Segment & Engage Decision-Makers in Reo.Dev’s Buyer Section
    • Buyer Persona Configuration in Reo.Dev
  • Enrichment
    • Enrichment
  • Audiences
    • Buyer Audience
  • Integrations
    • Connect GitHub repositories
    • Reo.Dev Zapier Integration Guide
    • Webhooks
    • Developer Docs
      • Docusaurus
      • GitBook
    • CRM
      • HubSpot
      • Salesforce
      • Pipedrive
      • Zoho
      • Freshworks
      • Leadsquared
    • Tracking Beacon
      • Install JavaScript for Documentation
      • Install JavaScript for Product
      • Install JavaScript in Website
      • Install JavaScript in Local Product
      • Track Code Interactions
      • Install JavaScript for Documentation through Google Tag Manager
      • Reo.Dev JavaScript Cookies and Consent Guide
    • Product Usage API
      • Overview
      • How to Configure Product Usage Metrics in Settings
      • Telemetry Data
      • Product API
      • Examples of Product Usage Metrics
      • Data Collected for Product Usage
    • Communities
      • Open Communities
      • Owned Communities
        • Slack
        • LinkedIn Company Page
    • Email
      • Apollo.io
      • How to Integrate and Use Outreach.io with Reo.Dev
      • How to Integrate and Use Salesloft with Reo.Dev
    • Website Tracking
      • RB2B
  • Analytics
    • Impact Dashboard
  • Campaigns
    • Run bulk email campaigns
    • Testing Your Email Integration with Reo.Dev
  • Settings
    • Add Customer Fit Score Criteria
    • Add Firmographic and Technographic Filters
    • Configure Slack & Email Notifications
  • Account and Contact Usage Limit
    • Manage Account and Contact Limit Usage
  • User Management
    • Invite a teammate to Reo.Dev
    • Manage CRM Permissions
    • Roles and Permissions: Admin vs User
    • What Happens to Data When a User Is Deleted in Reo.Dev?
  • FAQs/Troubleshooting
    • How to Exclude Competitors from My Segments in Reo.Dev?
    • How to Sync a Segment to Salesforce/HubSpot?
    • Why Is the 'Sync to CRM' Button Greyed Out?
    • I Synced My Accounts, But They Are Not Showing in My CRM – What to Do?
    • Why Am I Seeing More Accounts in CRM Than I Synced?
    • Why Can't I Find My Account in the Dashboard Search Bar?
    • Resolving Caching Issues in Reo.Dev
    • Understanding Score Discrepancies Between Account and Developer Activity Score
    • Reo.Dev Credit-Based Pricing: FAQs
Powered by GitBook
LogoLogo

Resources

  • Changelog
  • Playbooks
  • DevGTM Conversations
  • Support
  • API Docs

Company

  • Blog
  • Contact Us
  • Book a Demo

Policies

  • Privacy Policy
  • Terms of Service

© 2025 All rights reserved Reo.Dev

On this page
  • Why Traditional Testing Methods Won’t Work
  • Recommended Way to Test Apollo.io & Outreach.io Integration with Reo.Dev
  • Validating Your Setup with Apollo.io & Outreach.io
  • Final Validation Before Going Live

Was this helpful?

  1. Campaigns

Testing Your Email Integration with Reo.Dev

When integrating Apollo, Outreach or Salesloft with Reo.Dev, it’s crucial to verify that profiles from your segments are correctly syncing into the chosen sequence. This ensures your outreach campaigns function as expected before launching them at scale.

However, testing these integrations comes with nuances that require a structured approach. Below, we outline common challenges, the recommended testing method, and how to validate your setup before going live.


Why Traditional Testing Methods Won’t Work

🚫 Internal Employee Test Lists Won’t Work

A common way to test email sequences is by adding internal employee emails and running a test campaign.

Why this doesn’t work in Reo.Dev:

  • When configuring your domain, Reo.Dev automatically hides all internal employee data from the UI and backend to maintain data cleanliness.

  • This means internal employees won’t appear in segments, even if they engage with product assets.

  • You won’t be able to add them to a sequence, making this method ineffective.

🚫 Personal Email Lists Have Limitations

Another common approach is using personal email IDs (e.g., Gmail, Yahoo) to test sequences.

Challenges with this approach:

  • Reo.Dev only displays personal email addresses if they were captured via a first-party source (e.g., sign-up forms, product logins).

  • If testing bulk email campaigns, personal emails must meet the segment criteria, which is difficult to control without unintentionally capturing other profiles.

  • Most prospects in your dataset will have business emails, making personal email testing unreliable.


Recommended Way to Test Apollo.io & Outreach.io Integration with Reo.Dev

To ensure your integration is working without sending unintended emails, follow this structured approach:

Step 1: Create a Test Sequence in Apollo.io or Outreach.io

  1. Log in to your Apollo.io or Outreach.io account.

  2. Navigate to Sequences and create a new sequence named: "Test Sequence for Reo.Dev"

  3. Modify sequence settings to:

    • Disable all automated email steps (No auto-sends, no scheduled emails).

    • Ensure the sequence allows adding contacts dynamically or via manual upload.

  4. Save the sequence and ensure it remains inactive except for testing.

Step 2: Use This Test Sequence in Reo.Dev

  1. In Reo.Dev, navigate to Campaigns or any workflow where you add prospects to sequences.

  2. Select your Test Sequence for Reo.Dev from Apollo.io or Outreach.io.

  3. Run the process to sync profiles.

Step 3: Verify Syncing in Apollo.io or Outreach.io

  1. Open your Apollo.io or Outreach.io dashboard.

  2. Navigate to the Test Sequence for Reo.Dev you created.

  3. Check if the profiles from Reo.Dev have been successfully added to the sequence.

  4. If the profiles appear correctly, your integration is working as expected.


Validating Your Setup with Apollo.io & Outreach.io

Once your test sequence is set up and profiles are syncing correctly, the next step is to verify that:

  • Emails are formatted correctly

  • Personalization variables (e.g., first name, company) populate correctly

  • Email previews match expectations before sending

Both Apollo.io and Outreach.io offer built-in features to test and preview emails before launching sequences.

🔗 Apollo.io: Testing Email Templates & Variables

Apollo.io allows you to preview and test email templates before launching sequences. You can:

  • Preview how emails will look for each prospect.

  • Ensure variables like {{first_name}} and {{company}} populate correctly.

  • Send test emails to an internal inbox for final review.


🔗 Outreach.io: Previewing & Sending Test Emails

Outreach.io provides tools to preview emails and verify variables before sending. You can:

  • Preview emails for any prospect in a sequence.

  • Send a test email to yourself or a colleague.

  • Ensure merge fields and dynamic content work as expected.


Final Validation Before Going Live

Before launching real outreach campaigns, always:

  • Send a test email to yourself or a colleague

  • Check for missing or incorrect variables

  • Ensure formatting, links, and CTA buttons render correctly

By following these steps, you can confidently launch sequences with properly formatted, personalized emails that reach the right audience.


Need Further Help?

PreviousRun bulk email campaignsNextSettings

Last updated 12 days ago

Was this helpful?

Checkout Apollo.io’s official guide on Sequences: 🔗

Follow Outreach.io’s official guide: 🔗

Apollo.io Sequences
Outreach.io Sequences

If you need assistance with the implementation, contact your Customer Success Manager via the Slack channel or email us at

support@reo.dev