Apollo.io Integration

The Store Leads database does not include any personal information, so customers often use other data vendors to find contact information for the stores in our database. Since this is such a common use case, we've started integrating with personal data vendors to make things easier. Our new Apollo.io integration lets you see Apollo.io contact data when using Store Leads. You can also manually create CRM contacts from Apollo.

Manual Creation of Salesforce Leads

It's now possible to manually create Salesforce leads from the generic email addresses in the Store Leads database. If you've already integrated Store Leads with Salesforce, simply open the Salesforce, simply visit the Salesforce tab for any domain in Store Leads to see new functionality. Create Salesforce Lead. You'll see the list of existing leads for the current domain (if any) as well as options to create new leads using the generic emails from the Store Leads database.

New Social Media API

We've just added a new Social Media API endpoint that returns details for a social media account. It doesn't work for any social media account but it supports any account linked to a store in our database. Here's an example response when looking up the Instagram account for Kylie Cosmetics (https://instagram.com/kyliecosmetics): {   "domain_names" : [     "www.kyliecosmetics.com"   ],   "details" : {     "followers_90d" : -63508,     "following" : 614,     "category" : "

Enrich Uploaded CSV Files

Let's say that you have a spreadsheet that contains a list of domains along with other information. And you'd like to enrich the file by adding data from the Store Leads database for each row. This has always been possible, but fairly complicated. You'd have to: create a CSV file that contained just a single column with the domain names import the file to a list export the matching domains then manually merge the export with your original file To make this easier, it's now possible to enrich an existing CSV file.

Import CSVs with Multiple Columns

In the past, when importing your own list of domains to Store Leads, the import file had to consist of a single column containing domain names. If you already had a spreadsheet with multiple columns, this required extra work to create a new CSV file with just a single column. We've just updated our CSV import tool to support files with multiple columns. If the file contains muliple columns, you will be asked which column contains the domain names.

Meta Keyword and Meta Description Search

Meta keywords and meta description tags are used to describe the content of a page to search engines. When we crawl a store, we capture the meta keywords and meta description tags from the store's home page. These values are used to improve our own search results. When you search for a store in Store Leads, the query matches against a variety of fields including the name of the domain, the name of the merchant, the meta keyword and description fields and others.

CRM Search Filter Continuous Updates

When we first introduced the ability to filter stores based on whether they already exist within your CRM, there was one drawback to the implementation: the search filter was only updated once a day. So, if you added a new company record to your CRM, it could have taken a full 24 hours for our search filters to update. We've just deployed a change that updates the search filters continuously.

CRM Contact Search

About 6 months ago, we added the ability to search for stores that exist as companies or leads in your CRM. That's proven to be one of most popular features for sales teams but there was one thing missing. Until today, it wasn't possible to search for stores associated with contact records in your CRM integrations. We've just added the ability to filter stores based on whether they have a contact record in your CRM.

Failed Webhooks Support Failure Notification Emails

Webhook notifications for workflows can now be configured with a failure notification email(s). Webhook Action. When the webhook cannot be delivered to the target URL, an email will be sent to the provided email(s) describing the reason for the delivery failure. This typically only happens when the target URL times out or returns a HTTP response with a status code greater than HTTP 200. In the past, webhook delivery failures were silent.

Workflow Emails Can Now Be Sent To Multiple Recipients

Workflow email actions can now be configured to deliver to multiple recipients. Just provide multiple email addresses, separated by commas when configuring the action. Create Workflow button.