The Lyftron Provider for Google Search offers the most natural way to access Google Search data from Lyftron with ease and also enables to connect with BI, MDM & ML tools, Data warehouses, Databases and other SAAS based applications with zero code and zero infrastructure requirements. The provider wraps the complexity of accessing Google Search data into easy-to-integrate relational fully managed ANSI Sql format. Make faster and better business decisions with Lyftron’s Google Search data provider and automatically build your data migration pipelines in minutes, not months
The provider hides the complexity of accessing data and provides additional powerful security features, smart caching, batching, socket management, and more.
- Comprehensive Delta load mechanism.
- Real-time access to Google Search.
- Comprehensive full support of ANSI Sql to query data with ease.
- Collaborative query processing.
The user must have credentials for Google Search, Lyftron and your destination data warehouse, lake or database to perform the data pipeline operation with Lyftron
Connecting to GoogleSearch
To establish a connection to GoogleSearch provide a CustomSearchId and APIKey.
To search with a Google custom search engine, you need a CustomSearchId and APIKey.
To obtain the CustomSearchId, sign into Google Custom Search Engine and create a new search engine.
To obtain the APIKey, you must enable the Custom Search API in the Google API Console.
For more information on obtaining values for these properties, refer to Connecting to GoogleSearch.
Creating a Custom Search Engine
To start searching websites through the provider, follow the steps below:
- Sign into the Google Custom Search Engine site.
- Click New Search Engine and add a site to focus the search on.
- Click Edit Seach Engine, select your search engine in the menu, and then click Setup.
- In the Details section, click Search Engine Id to retrieve the search engine Id used as the CustomSearchId in the connection string.
- In the Sites to Search section, you can additionally select the Search the Entire Web but Emphasize Included Sites option in the menu.
Getting the API Key
To authenticate requests to the Custom Search API, follow the steps below:
- Log into the Google API console and select a project.
- In the side bar under APIs & Services, click Library and then select the Custom Search API. Click Enable.
- In the side bar, click APIs & Services -> Credentials.
- Click Create Credentials -> API Key.
- Select the API Key to restrict the key to your platform.
Establishing a Connection with Lyftron's Quickstart Steps
Create your Google Search connection with Lyftron by following the 5 easy steps show below:
Step1. Add your connection
Click on Connect section on the left panel → Click on Add Connection button
Step2. Select your connector
In the connector selection panel, search and click Google Search for your connection
Step3. Enter your connection details
In the Connection String section enter the values of the below parameters. The following connection string is required to establish Google Search connection with Lyftron.ApiKey=[your_apikey];CustomSearchID=[your_customer_search_ID];
|Connection Name||Enter your connection details||Required|
|Logfile**||Use the logfile option to debug your job and provide your connection name to generate the log file. [ConnectionConfigurationPath]\Connection_name_log.tx||Optional|
|Verbosity**||Choose verbosity 1-5 based on the severity of debugging||Optional|
** For more information, check the Lyftron logging and debugging section.
If you want more detailed information about how to establish a connection with Lyftron, click on Lyftron Connection Quick Start guide.
Step4. Test your connection
Once you are done entering your connection details, simply click on the Test Connection button to test the connectivity. In case your connection fails, add Logfile and Verbosity parameters and check the Lyftron logging and debugging section, to debug the error.
Step5. Save your connection
Views are composed of columns and pseudo columns. Views are similar to tables in the way that data is represented; however, views do not support updates. Entities that are represented as views are typically read-only entities. Often, a stored procedure is available to update the data if such functionality is applicable to the data source.
Queries can be executed against a view as if it were a normal table, and the data that comes back is similar in that regard. To find out more about tables and stored procedures, please navigate to their corresponding entries in this help document.
|ImageSearch||Views||Query Google custom search engines for images.|
|WebSearch||Views||Query the web on Google.|