Overview
Integrating your Convertr campaigns with Apollo (Apollo.io) allows you to enrich leads with additional contact and company data — such as job titles, addresses, LinkedIn URLs, and company details — enabling more precise targeting and improved conversion outcomes.
In this guide, we’ll walk through setting up a Universal Connector job to query data from Apollo, match and append it to your existing leads, and then deliver the enriched leads to your marketing platforms.
Please note:
- Get in touch with our support team to enable the Universal Connector feature on your account.
- Apollo integration is offered as a bring-your-own-license solution — you’ll need to provide your own Apollo API key.
Creating Your Apollo Account
Where: In Apollo
Apollo offers free credits when you sign up, allowing you to test integration without needing to contact their sales or support teams. If you don't yet have an account, visit the Apollo signup page and follow the instructions to create one.
Please note: You may need to contact Apollo to extend your API usage limits if you plan to enrich a large volume of leads.
Configuring Your Apollo Account
Where: In Apollo
You’ll need an API key to access Apollo API. It will be used later when configuring the Universal Connector.
Follow these steps to generate your API key:
- Go to Apollo API keys management page.
- Click 'Create new key'.
- Enter a name of your choice in the 'Name' field (e.g. 'Convertr Universal Connector').
- Enable the ‘Set as master key’ toggle to grant access to all APIs.
- Click 'Create API key'.
- In the list of API keys, click the copy icon to copy the API key.
Adding Universal Connector Integration
Where: In Convertr
Now that we’ve completed all the prerequisites, we’ll add the Universal Connector job to integrate with Apollo contact enrichment.
To speed up the setup, we’ll use a sample JSON configuration.
1. Prepare JSON Configuration
First, we’ll prepare the JSON configuration to quickly set up a Universal Connector job in the next step.
- Download the sample JSON configuration file.
- Open the file.
- Replace '<Your Apollo.io API key>' with your Apollo API key.
2. Add Universal Connector Job
Next, we’ll add the Universal Connector job and configure it using the JSON from the previous step. In this example, we’ll map all columns from the sample table to lead fields and add a validation step to ensure that Apollo returns a record.
- Go to Processr > Quality Assurance tab in your Convertr campaign.
- Click ‘Add’.
- Select 'Universal Connector' from the 'Job' dropdown.
- Click ‘Import from JSON’.
- Paste the JSON configuration.
- Click ‘Save’.
Please note:
- In this example, we only append LinkedIn URL, country, and company name from Apollo.
- You can find the full list of available enrichment fields in the ‘Response’ section of the Apollo API documentation:
In a real integration, after importing the JSON:
- Adjust the ‘Result Mapping’ section to add any other fields from Apollo response.
- Customize the ‘Validation Conditions’ section to meet your specific needs.
For example, if you'd like to append job title as 'Job Title (Apollo.io)' and primary phone number of a company as 'Company Phone (Apollo.io)', your mapping should look like this:
Another example: if you want to check that the job title is present in the Apollo result, update the validation conditions as follows:
Configuring Delivery to Your Marketing Platform
Where: In Convertr
As with any lead data, enriched data can be delivered to your marketing platform (e.g., Marketo, Salesforce) or sent to your email address as a CSV file.
To set this up:
- Go to the Processr > Integration tab of your campaign
- Click 'Add' to create a new integration, or 'Edit' to modify an existing one.
- In the 'Mapping' section, add the following field mappings:
- Apollo.io LinkedIn URL: job_data[1173][core.data.0.Apollo.io LinkedIn URL]
- Apollo.io Company: job_data[1173][core.data.0.Apollo.io Company]
- Apollo.io Country: job_data[1173][core.data.0.Apollo.io Country]
- Click 'Save'.
In a real integration, map your actual field names using the 'job_data[1173][core.data.0.<field name>]' pattern. Replace '<field name>' with the exact lead field name from the 'Result Mapping' section of your Universal Connector configuration. The rest of the pattern—including the number 1173—will remain the same across all campaigns.
Please note: You may need to adjust your marketing platform configuration to accept the new fields.
Testing Your Configuration
Now that all elements of your integration are in place, let’s test it.
1. Submit Lead
Submit a lead with a real email.
For initial testing, submit a lead with the 'tim@apollo.io' email address that Apollo provides as a working example in their public API documentation. This way, we will make sure Apollo has relevant data, decreasing potential problems.
You can submit leads with your real lead email addresses for further testing.
2. Check Lead Data
- Go to the Leads tab of your campaign.
- Click 'View' on the submitted lead.
- Expand the Universal Connector section.
You should see enriched data similar to the following:
Please note: If the Universal Connector section appears empty, try collapsing and expanding it again. The information should load correctly—this is a known issue.
3. Check Marketing Platform Data:
- Go to your connected marketing platform (e.g., Marketo, Salesforce).
- Verify that the enriched fields are present in the lead data.
Please note: You may need to adjust your marketing platform’s configuration to display or accept the new fields properly.
Troubleshooting Your Configuration
If the Universal Connector section of your lead doesn’t display correct information, or your marketing platform is missing the enriched information, it’s likely due to a configuration issue, restricted access to the Apollo API, or Apollo missing information for the provided lead email address.
1. Check Universal Connector Logs
- Go to the Leads tab of your campaign.
- Click 'View' on the lead.
- Click the 'Provider Logs' tab.
- Check the Universal Connector provider logs:
- Check the 'request' step logs:
- If the URL in the message isn't similar to 'https://api.apollo.io/api/v1/people/match?...', verify that the correct URL is provided in the API section of the Universal Connector job.
- If the last part of the URL doesn't match '?email=<lead email>', where <lead email> is the email address of the submitted lead, verify that the Mapping section of the Universal Connector includes the following line:
- email: email
- email: email
- If the request records are missing, check that the Universal Connector job is enabled.
- Check the 'response' step logs for any errors returned by Apollo.
- Check the 'request' step logs:
2. Check Delivery Logs
- Go to the Leads tab of your campaign.
- Click 'View' on the lead.
- Click the 'Provider Logs' tab.
- Check the 'request' and 'response' logs for the delivery provider that you configured in the Processr > Integration tab of your campaign to identify any potential errors.
Conclusion
With the configuration above, any lead submitted to your campaign will be matched and enriched using Apollo data.
The enriched data will appear in the Universal Connector section of the lead view in Convertr.
It will also be delivered to your connected marketing platforms, enabling more informed decision-making.