• Importing data from Google Places

  MetaLocator can import data from multiple sources, including Google Places. The Google Places API is only available for Enterprise accounts. Google Places can be used to enrich the data existing your MetaLocator. For example, to import location hours, photos or to correct names and so forth. Important: The Google API is not free. Google charges a [variable fee per API](https://developers.google.com/maps/documentation/places/web-service/usage-and-billFew readers

• MetaLocator SFTP import job

  SFTP Data Import Setup To enable automated, background SFTP imports on a recurring basis, you must contact the MetaLocator Help Desk. This functionality requires both the Backgrounding add-on and an Enterprise subscription. Before You Begin Provide the Help Desk with your public SSH key[.](https://support.metalocator.com/en/articles/10355654-instrucFew readers

• Connecting to MetaLocator SFTP

  To upload files in a secure manner to MetaLocator, we provide SFTP access to our Enterprise clients.  The helpdesk must create SFTP credentials for you upon request.  The helpdesk will provide a username, a hostname and a private key.  These are shared securely via LastPass. We cannot share SFTP credentials via email for security reasons. To connect to the SFTP repository, an SFTP client must be used. Ensure you have shared the IP address from which youFew readers

• Displaying related records

  Relational data can be useful when displaying a parent-child relationships in MetaLocator. For example: Doctors at hospitals Products at stores Staff at locations Agents at brokerages In these examples, the doctors, products, staff and agents are example of related records. The hospitals, stores, locations and brokerages are all locations, where one location can have many related records. In database jargon this is typically called a many-to-many relationship. In MetaLocator, you mustFew readers

• Manually adding and editing data

  You can add and edit data one record at a time from MetaLocator using the Record Editor.  To get started, go to Data, then All Records and click the name of the record you want to edit. To create a new record, click New as shown below. [](https://downloads.intercomcdn.com/i/o/238497072/54de456e49a09f1e8a5e076e/image.png?expires=1794511800&signature=4d5886c8caccda25f32a9adeFew readers

• Configuring the DocuSign Integration in MetaLocator

  The MetaLocator DocuSign integration allows MetaLocator to automatically generate and send documents for electronic signature using DocuSign templates. This article explains how to: Generate the required DocuSign Configuration Values Create and configure a DocuSign template Configure DocuSign settings inside MetaLocator Before Getting Started Before configuring the integration, ensure the following items are available: A DocuSign developer account A DocuSign production accoFew readers

• Importing data from Microsoft Dynamics 365

  MetaLocator can connect directly to Microsoft Dynamics to extract your partner data for direct inclusion in your locator. To import data from Microsoft Dynamics, choose Import, then Microsoft Dynamics to bring up the connection screen: [](https://downloads.intercomcdn.com/i/o/1089576849/f96a31d691d0a2c624d832f3/image.png?expires=1794511800&signature=9ff2fc988a151bfdceccaeFew readers

• Introduction to Exporting Data

  You can quickly export your data from MetaLocator into a spreadsheet format.  The process is quite simple, and begins by logging into the MetaLocator Control Panel, choosing Data, then Export. ​ [](https://downloads.intercomcdn.com/i/o/90150697/21eb1af9754070d9e2c19b54/image.png?expires=1794511800&signature=421890ac7ec1b23e3200b34c7fd2d0d8f231e3f37883a14ba154a7e1Few readers

• Email verification

  MetaLocator includes the capability to bulk verify the email addresses attached to your locations in the email field. To launch the bulk verification process, click Data > All Records, then select Validate Email Address as shown below: [](https://downloads.intercomcdn.com/i/o/98256429/64745443cf504b9bc1525453/image.png?expires=1794511800&signature=6bc8561ed5cFew readers

• Importing relational data in a single file

  If you are using MetaLocator's multi-dimensional features you might know that relational data can be imported in 3 files, a locations file, a related data file and a linking file.  This can constitute a lot of spreadsheet management in the long term. This 3-import file structure roughly mirrors MetaLocator's internal table structure for related data.  However, there is a simplified data file format that allowsFew readers

• About All Records

  The All Records screen is where most data management occurs. Here you can edit, delete, publish and categorize your data directly from within MetaLocator. By default, the All Records screen shows all of your data ordered by it's MetaLocator-assigned ID number. [](https://downloads.intercomcdn.com/i/o/238498244/22b0aec4aba6a08b1d8d4092/image.png?expires=1794511800&signaturFew readers

• Importing Data from Salesforce

  Import location records from Salesforce into MetaLocator using the Salesforce connector. You can run a single import or, if your account includes background importing, keep your location data updated on a schedule. The connector reads Salesforce data and imports it into MetaLocator. It does not write any changes back to Salesforce. Before you begin You will need: A MetaLocator account with permission to import data. A Salesforce administrator to create an External Client App. A SaleFew readers

• Changing the Google Account associated with a MetaLocator User Account

  Clients with established data feeds from Google Sheets may occaisionally need to change the Google Account associated with the user that is importing data from Google Sheets. To change the Google account associated with an existing MetaLocator user: Login to MetaLocator as the MetaLocator user that needs the Google Account changed. Click My User Profile as shown below: [![](https://storage.crisp.chat/users/helpdesk/website/-/5/d/f/9/5df9fd67572b8800/17Few readers

• Reserved column names

  When creating custom fields, some field names are already in use by MetaLocator, in that they have special meaning.  This article summarizes those special field names.  These field names should also not be used after removing the underscore, for example, user_id implies that user_id and userid should not be used in your custom fields. id keyword limit radius limitstart tags tag component task location_id layout priority tmpl view cmd framed value option titleFew readers

• Introduction to importing data

  Importing data commonly starts with preparing your data in a spreadsheet format.  To view a sample spreadsheet, right click this link and choose Save as.  This file will open in Excel, Google Spreadsheets and OpenOffice.  MetaLocator highly recommends that you work in the CSV UTF-8 file format.  Other formats can introduce formatting and other non-data elements that can confuse the importer. For tipsFew readers

• Importing Data via Copy & Paste

  +MetaLocator supports importing data via copy and paste. The pasted data should follow the same format as any other data import and should include column headings. (See a sample spreadsheet). Watch this video for an example: To import data via Copy & Paste, Click Data (or Locations) on the main navigation. Click Import Click **Copy/PasteFew readers

• Publishing and unpublishing results

  Records in MetaLocator include a "Published" state that allows our users to quickly enable and disable locations across all Interfaces. When a location is unpublished it will be effectively hidden across all public-facing MetaLocator components including Interfaces, APIs and add-ons. Unpublishing a single record To manage the published state of a location, login to MetaLocator and under "All Records", first identify the location by searching for the record from the dashboard. Click the PublFew readers

• Importing locations and reviews from Ratings.MD

  Its easy to import locations and reviews from Ratings.MD into MetaLocator. Before you import from Ratings.MD, be sure to configure an External Key which contains the NPI. The NPI or "National Provider Identifier" is a standard manner of identifying a healthcare provider. MetaLocator also uses it to ensure we don't import the same physician twice, apply updates and reviews to the correct physician. Once an NPI External KFew readers

• Multiple Brand Guide

  MetaLocator is commonly used for dealer locators, store locators and other scenarios where we find the following requirements: Our customer manages one or more brands Those brands have different locations, products and services Our customer may manage different Websites, sometimes one for each brand. Additionally, our customers may have multiple countries, teams, languages and other requirements. This guide describes the best practices in data and category management, account setup aFew readers

• Bulk actions and selections

  Once your data is imported, there are a few operations you may need to perform on one or more records.  The Bulk Actions menu provides a few essential functions to help you operate on more than one record at once. There are two steps to using the Bulk Actions feature: first, you must create a selection, and second execute a bulk action against those selected records. Creating a Selection There are two ways to select records.  First, you can manually select records by checking the box adjacFew readers

• Updating the SalesForce WSDL for an existing job

  To update or change the WSDL associated with your existing SalesForce import jobs, login to MetaLocator and click the Background Processes icon in the toolbar: [](https://downloads.intercomcdn.com/i/o/722960727/346a49752fcd7face7e11cb2/image.png?expires=1794511800&signature=5a91b64ba001011af06cf28b960056934538b66834b187c6c3b920ba9ad54076&req=cyIlH89%2BmoNYFb4f3HP0gCpUiu3VCXFew readers

• Importing data from Google Drive

  MetaLocator supports multiple data sources including spreadsheets, text files, SalesForce and now Google Drive. This integration allows you to import Google Sheets stored in Google Drive just as you would a CSV or spreadsheet from your computer.  This allows you easily share access to the Google Sheet that contains your data with multiple contributors via Google Drive's existing [shaFew readers

• Importing Location Data from Yext

  To import data from Yext, choose Data, then Import and choose Yext from the available options as shown below: [](https://downloads.intercomcdn.com/i/o/104426261/a21676aa65ffd3690f94e722/image.png?expires=1794511800&signature=dda426f60c8660e45c8e3ba0621fd51023642d434b7f6866266baadc580ed764&req=dSAjEst4n4deFb4f3HP0gFGNNwjrvnXWHUrcX1Q%2B6LSjChEcdTf448gwnpVa%0AtTNYAH6x1wn7Xyi0KFew readers

• Keeping MetaLocator data in sync with Zapier

  MetaLocator has a plethora of import, export and synchronization options that are majority focused on bulk imports, e.g. managing changes of hundreds or thousands of records at a time. However, in some cases a real-time, change-by-change integration is preferred. MetaLocator can integrate with external systems using Zapier in a model where each individual change that occurs in an external system is "pushed" to MetaLocator as it occurs based on a Zapier Trigger. GeneralFew readers

• Updating your SalesForce password for existing import jobs

  When a user's password in SalesForce is changed, or their SalesForce Security token expires, MetaLocator may loose access to SalesForce. You may receive an email notice containing a message accordingly as follows: An error occurred while importing data from SalesForce. Below are details regarding the problem. Last Request: Request content hidden, contained password. INVALID_LOGIN: Invalid username, password, security token; or user locked out. To provide the updated credentials, fFew readers

• Importing from Azure Blob Storage

  MetaLocator supports importing location data directly from Microsoft Azure Blob Storage. This allows you to store your CSV data files in an Azure Storage container and import them into MetaLocator either on-demand or on a recurring schedule. [](https://downloads.intercomcdn.com/i/o/yn1vvwtq/2271245324/baad2e1087e466fcb37c25f29217/image.png?expires=1794511800&signature=a56eFew readers

• Exporting a Selection of Records

  When you need to export only a subset of your data—such as published records or a specific group of locations—MetaLocator allows you to create a selection and export just those records. This helps you manage and analyze focused data sets without exporting your entire database. 1. Navigate to All Records In the MetaLocator under Data or Locations, select All Records. Locate the search bar at the top of the records list. Click the down arrow (▾) next to the searcFew readers

• Integrating with Google My Business

  Google My Business (GMB) is a platform provided by Google for multi-location businesses to promote and manage local business listings on Google Search, Google Maps and more. Synchronizing data with Google My Business helps ensure the data is consistent between MetaLocator and Google. MetaLocator supports bulk listings import and export with GMB. This allows you to export data from MetaLocator in a format ready for import into GMB, and also we can import data directly from GMB into MetaLocator.Few readers

• Custom Export Formats

  When exporting data from MetaLocator, the system creates a single CSV file which can be opened in Excel or similar database programs.  Occasionally it can be helpful to customize the column names and ordering to align with an external system. When exporting data, a list of Export Formats is available.  These formats are a collection of Field Mapping Rules which instruct MetaLocator how to assemble the export file. [![](https://storage.crisp.chat/users/helpdesk/website/-/a/b/1/b/ab1b31227796180Few readers

• Integrating with Zapier

  MetaLocator provides various endpoints which can trigger events in Zapier based on events in MetaLocator. For example, MetaLocator can trigger a Slack message when a Lead is received, or insert a new row into a Google Sheet, or send an email to a manager or any of thousands of creative actions available in Zapier. If the MetaLocator trigger or action is Invite Only, please contact support to request an invitation. Available TriggersFew readers

• Importing data from Airtable

  MetaLocator can import location data directly from an Airtable base. This allows you to use an Airtable table as the source for your MetaLocator location records. This article explains how to create an Airtable Personal Access Token and configure the Airtable import connection in MetaLocator. Before You Begin You will need: Access to the Airtable account that owns or can access the base you want to import Permission in Airtable to create a Personal Access Token Access to the MetaLocFew readers

• Updating an Import Job

  When a new field is added to your data source, the column mapping for the associated job must be updated. This process also allows you to modify import options such as "Update Existing & Insert New." Follow these steps to update the import settings: Navigate to the Jobs Menu Go to the Jobs menu located in the upper right corner of the screen. Select the Job to Edit Find the job you want to update and open the Actions dropdown menu. [![](https://storage.crisp.chat/usFew readers

• Importing from Amazon S3

  Follow the below steps to import a CSV data file from an Amazon S3 Bucket into MetaLocator. The first step is to ensure your CSV files are ready and available in an Amazon S3 bucket. Creating and Configuring the Amazon S3 Bucket AWS recommends using IAM permissions and least-privilege policies for this type of access, and access keys are used for programmatic access to AWS resources. Goal Create credentials that can: List the contents of one specific S3 bucket. Download files frFew readers

• Importing Products by location

  Use this method when your data contains over 100 products and the inventory varies by location. Use categories when you are managing brands or product categories by location. Also, if you have fewer than 100 products consider using our category system to create a product finder to avoid the overhFew readers

• Preparing your data for import into MetaLocator

  A common challenge when getting on board with MetaLocator is the proper collection and formatting of location data.  The import process and the Data Quality Dashboard will warn of any issues found in incoming data, but it is best to know what the system is looking for, so the process goes as smoothly as possible. The objective of this article is to create a spreadsheet thatFew readers

• Importing custom field text Information with multiple lines

  This article is for customers having data best displayed as a multiple lines. This could be a bullet list or just a simple set of multiple lines such as shown below. [](https://metalocator.intercom-attachments-1.com/i/o/284161535/9d2f809d6e04641410d616ea/10.jpg?expires=1794511800&signature=3ba2f3e899480da9a571e2b0d9e7951fe385385440287e151c299c2d9f8ee7d8&req=digjF89%2FmIJaFbFew readers

• Background Importing

  When you have data that needs to be imported into MetaLocator on a regular basis, you can manually import that data as many times as you need. However, having that process automated frees up your time and avoids costly mistakes. MetaLocator provides a background importing service that can pull data from Google Drive, SalesForce, SFTP or any other supported integration on a regular basis. Not all accounts have access to background importing, view the [Plan Comparison](https://www.metalocator.comFew readers