How to Activate Geolocation Service

Activating the Geolocation service in SellKit allows for more targeted customer interactions by utilizing location-based segmentation. This step-by-step guide will help you activate and implement the Geolocation service for your SellKit funnels.

Important Note:

For utilizing location-based conditions within your SellKit features, it's essential to have the Geolocation service activated. If this service is not enabled, the location-based segmentation and conditions will not function. Ensure that the Geolocation API Key is properly generated and implemented as outlined in the steps above to take full advantage of this feature.

Step 1: Accessing the Geolocation API Service

  1. Log in to your SellKit dashboard.
  2. In the side menu, click on SellKit to expand the options.
  3. Select Settings.
  4. Under Settings, click on the Geolocation API tab.

Step 2: Generating Your Geolocation API Key

  1. Click on Generate API Key link in the description
  2. You will be redirected to the SellKit API management portal.
  3. On the portal, you may need to log in again using your SellKit credentials.

Step 3: Creating the API Key

  1. On the API management portal, click on Create New API Key.

  1. A dialog box will appear prompting you to enter your Website URL. Make sure to include the complete URL, including the http:// or https:// prefix.
  2. After entering your Website URL, click on the Create button.
  3. Your new API Key will be generated and listed on the page.

Step 4: Implementing the API Key in SellKit

  1. Copy the newly created API Key from the portal.
  2. Return to your SellKit dashboard's Geolocation API settings page.
  3. Paste the API Key into the Geolocation API Key field.
  4. Save your settings by clicking any Save button available on the page.


After completing these steps, your SellKit account will be utilizing the Geolocation API service, allowing you to create more personalized and location-specific customer experiences.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.