This guide walks you through adding multiple phone numbers and emails for a store and displaying them in your locator using the Template Customizer.

What This Does

By default, each store can have one phone and one email. If you need more than one of each, follow these steps:

• Create extra contact fields
• Enter the additional data
• Update your template to display the extra contacts

Step 1 — Create Additional Contact Fields

1. Go to ASL Settings > Manage Additional Fields in your WordPress admin.
2. Click Add New Field to create a second phone number field:
   • Label: Phone 2
   • Control Name: phone_2
3. Add another field for a second email:
   • Label: Email 2
   • Control Name: email_2
4. Click Save Fields.

Step 2 — Enter Additional Contact Data

1. Go to Stores and edit the store(s) where you want the extra contacts.
2. You will now see the new Phone 2 and Email 2 fields.
3. Enter the extra phone numbers and emails you want.
4. Save the store(s).

Step 3 — Update Your Template

To display the new contact fields:

1. Go to ASL Settings > Customizer.
2. Select the template you are using from the dropdown.
3. Click Load Template to load its HTML into the editor.

Locate the section where phone and email are output.

Version A — Each Contact on Its Own Line

If you want each phone/email on its own line with individual icons:

{{if phone}}
<li class="sl-phone">
    <i class="icon-mobile"></i>
    <a href="tel:{{:phone}}">{{:phone}}</a>
</li>
{{/if}}

{{if phone_2}}
<li class="sl-phone-2">
    <i class="icon-mobile"></i>
    <a href="tel:{{:phone_2}}">{{:phone_2}}</a>
</li>
{{/if}}

{{if email}}
<li class="sl-email">
    <i class="icon-mail"></i>
    <a href="mailto:{{:email}}">{{:email}}</a>
</li>
{{/if}}

{{if email_2}}
<li class="sl-email-2">
    <i class="icon-mail"></i>
    <a href="mailto:{{:email_2}}">{{:email_2}}</a>
</li>
{{/if}}

Version B — Phones Together, Emails Together (Single Icon Per Line)

If you want the phones on the first line with one phone icon and the emails on a second line with one email icon, use this:

{{if phone || phone_2}}
<li class="sl-phones">
    <i class="icon-mobile"></i>

    {{if phone}}
    <a href="tel:{{:phone}}" class="mr-2">{{:phone}}</a>
    {{/if}}

    {{if phone_2}}
    <a href="tel:{{:phone_2}}" class="mr-2">{{:phone_2}}</a>
    {{/if}}
</li>
{{/if}}

{{if email || email_2}}
<li class="sl-emails">
    <i class="icon-mail"></i>

    {{if email}}
    <a href="mailto:{{:email}}" class="mr-2">{{:email}}</a>
    {{/if}}

    {{if email_2}}
    <a href="mailto:{{:email_2}}" class="mr-2">{{:email_2}}</a>
    {{/if}}
</li>
{{/if}}

Step 4 — Save Your Template

After adding either version of the code:

1. Click Save Template.
2. Visit your store locator on the front end to confirm the new layout displays correctly.

At the moment, Agile Store Locator places one marker per exact latitude/longitude. If multiple stores share the same coordinates, the markers will overlap.

Recommended Solution: Slightly Adjust Store Position Manually

You can easily fix this by slightly offsetting one or more store locations directly from the store editor. This keeps the stores visually side by side on the map while still representing the same building.

Step-by-Step: Offset Store Markers in the Same Building

1- Open the Store Editor

• Go to Agile Store Locator → Manage Stores
• Edit one of the stores that shares the same address

2- Fully Zoom Into the Location

• In the map inside the store editor, zoom in as much as possible
• This gives you precise control over marker placement

3- Slightly Drag the Marker

• Click and drag the marker just a little away from its current position
• The movement should be very small — just enough to avoid overlap
• The store will still appear in the same building visually

4- Save the Store

• Click Save Store
• Repeat the same steps for other stores if needed

Result

• Store icons will appear side by side instead of overlapping
• Each store remains clickable and visually distinct
• Works perfectly with different marker icons
• No custom code or configuration required

Important Notes

• This is a visual adjustment only — it does not affect store address data
• Best practice for:
  • Malls
  • Office buildings
  • Hospitals
  • Shared commercial locations
• The offset should be minimal to maintain accurate map representation

This ensures your stores appear correctly on the map—even when coordinates are missing from the source data.

When Do You Need This Feature?

You should enable coordinate fetching if:

• Your external API does not return latitude and longitude
• Your store records include address fields like:
  • Street
  • City
  • State
  • Postal Code
  • Country

Agile Sync uses these fields to generate accurate coordinates via Google Geocoding.

How Agile Sync Fetches Coordinates

When coordinates are missing:

1. Agile Sync sends the full address to Google Geocoding API
2. Google returns the latitude and longitude
3. The addon automatically saves those values with the store record

No manual intervention is required once configured correctly.

Required Configuration (Very Important)

Before enabling this feature, make sure both requirements below are met.

Google Server API Key Must Be Properly Configured

Your Google Server API Key must:

• Be enabled and active
• Have NO HTTP referrer restrictions
• Have Geocoding API enabled

If your key is restricted or misconfigured, coordinates will not be fetched.

Follow this step-by-step guide to fix it:
https://agilestorelocator.com/wiki/google-server-api-key-troubleshooting/

Do NOT Map Latitude & Longitude Fields

If your external API does not provide coordinates:

• Do not map lat or lng fields in the Agile Sync field mapping
• Leave latitude and longitude unmapped

This allows Agile Sync to detect missing coordinates and fetch them automatically.

Important Note for Existing Sync Jobs

If you already have an existing Agile Sync job, coordinate fetching may not run due to timestamp validation.

Why This Happens

If the “Last Modified” field is mapped:

• Agile Sync only updates records when the external API provides a newer timestamp
• Existing records without updated timestamps will not refresh coordinates

Recommended Solution (Clean Reset)

To ensure coordinates are fetched correctly:

1. Go to Agile Store Locator → Import / Export
2. Delete all existing stores
3. Delete the existing Agile Sync job
4. Create a new Agile Sync job
5. Ensure:
   • Latitude & longitude are not mapped
   • Google Server API key is properly configured
6. Run the new sync

This forces all records to be reprocessed and coordinates to be generated correctly.

Prerequisites

Before you begin, make sure:

• WordPress and WooCommerce are installed and activated
  
• Multi Store Addons for WooCommerce is installed and configured
  
• WePOS plugin is installed
  
• You have administrator access to WordPress

Step-by-Step Guide

Step 1: Enable the “WePOS Integration” Option on Multi Store Addons for WooCommerce

The first thing you will need to do is to enable the “WePOS Integration” option in Multi Store Addons for WooCommerce. To do this, please follow the steps below:

1. From the WordPress dashboard, go to the “A Store Locator” plugin and click on the “WooCommerce” tab
2. Go to the Inventory tab
   
3. Enable the “WePOS integration” option
   

Step 2: Install the WePOS Plugin

1. Log in to your WordPress Admin Dashboard
2. Navigate to Plugins → Add New
3. Search for WePOS
   
   
4. Click Install Now, then Activate
5. Once activated, you will see WePOS in the WordPress menu

WePOS enables point-of-sale functionality directly inside WooCommerce.

Step 3: Add An Outlet on WePOS

1. Go to WePOS → Outlets
2. Click on “Add Outlet”, fill in the information, and click on “Create Outlet”
   

Step 4: Assign a Counter and Cashier to Your Outlet

1. Next to the newly created outlet, click on the three-dot menu button, and click on “Add Counter”
2. Enter the counter name and number, and click on “Add Counter”
3. Next, click on the three-dot menu button, and click on “Add Cashier”
4. Select a Cashier and click on “Assign Cashier”
   
   

Now, a counter and cashier are assigned to the outlet you just created.

Counters represent physical POS terminals, while cashiers are the users operating them.

Step 5: Link a store with WePOS

The next step is to link one of your stores with WePOS. To do this, please follow the steps below:

1. Go to the WordPress dashboard, navigate to the Agile Store Locator plugin, and click on “Manage Stores”
2. Locate the store you want to link to WePOS and click on the “edit” icon
   
3. Go to the WooCommerce tab
4. Assign an outlet to this store using the “WePOS Outlet” field
5. Click on “Update Store”
   

Once this is done, the WePOS outlet will be linked to the store you assigned it to.

Now you can go to the POS interface and manage the products that are assigned to this store.

Step 6: Go to View POS

1. Navigate to WePOS → View POS
   
   
2. Log in using the outlet and counter credentials you created earlier
   
   

This will open the WePOS interface, where sales transactions are processed.

This step ensures that sales, stock, and pricing data sync correctly with the chosen outlet.

Step 7: Change Product Prices and Stock via CentralStock

1. Go to A Store Locator Plugin → Central Stock
   
2. Locate the product you want to change the price and/or inventory for
3. Click on “update” next to the correct store location
   
4. Update:
   
   • Product prices
   • Stock quantities
     
5. Click on “Update Inventory” to save the changes
   
   

Once you make changes to the product price and inventory, all updates will automatically reflect in:

• WePOS
• WooCommerce product listings
• Assigned store/outlet inventory

Result

After completing the above steps:

• WePOS is fully linked with Multi-Store Addons for WooCommerce
  
• Product prices and stock are managed from one central location (Central Stock Section)
  
• POS transactions update inventory in real time across all outlets

Order Summary

Once you complete a transaction using WePOS, you can view the transaction details by following the steps below:

1. Go to the WordPress dashboard
2. Head over to the WooCommerce plugin, and click on “Orders”
3. Open the latest transaction and view the transaction details
   

Video

For a more detailed demo on how to link WePOS with Multi Store addons for WooCommerce, and how to update product prices and stock using the central stock section, please see the video below.

Step-by-Step Instructions

1. Open the page in Elementor
   • Go to Pages → All Pages in WordPress.
   • Click Edit with Elementor on the page where you want to display the store locator.
2. Search for the Shortcode widget
   • In the Elementor left panel (Widgets section), search for “Shortcode”.
3. Add the Shortcode widget to the page
   • Drag and drop the Shortcode widget into your page layout.
4. Insert the Agile Store Locator shortcode
   • In the shortcode field, paste the following: [ASL_STORELOCATOR]
5. Update / Publish the page
   • Click Update (or Publish) to save your changes.
   • View the page on the frontend to confirm the store locator is loading correctly.

Important Notice About Elementor HTML Widget

• Since Elementor version 3.33.5, the HTML widget is no longer supported for Agile Store Locator.
• Using the HTML widget can break the store locator UI due to how Elementor now processes inline HTML and scripts.
• Always use the Shortcode widget to embed [ASL_STORELOCATOR].

1. Data API level (WordPress filter) – removes Phone/Email from the store data output globally. Agile Store Locator WordPress Plugin
2. Template level (Customizer) – removes (or edits) the Phone/Email markup from the List/InfoBox templates. Agile Store Locator WordPress Plugin

Method 1: Remove Phone/Email at the Data API Level (Recommended)

This method removes the values from the dataset before the Store Locator renders, so Phone/Email won’t appear anywhere the template tries to print them. This uses the plugin’s WordPress hooks/filters system. Agile Store Locator WordPress Plugin

Add this code to your theme’s functions.php (or a custom plugin):

function remove_asl_phone_email_data($all_stores) {

  foreach($all_stores as $store) {

    $store->phone = '';
    $store->email = '';
  }

  return $all_stores;
}

add_filter('asl_filter_stores_result', 'remove_asl_phone_email_data');

Notes

• This is a global approach (affects list + infobox + anywhere the store data is used).
• Best when you want Phone/Email removed site-wide without editing templates. Agile Store Locator WordPress Plugin

Method 2: Remove Phone/Email from the Template (Customizer)

This method removes Phone/Email from the rendered HTML by editing the template in the Store Locator Customizer. Agile Store Locator WordPress Plugin

Remove from the Store List Template

1. Go to ASL Settings → Customizer. Agile Store Locator WordPress Plugin
2. Select the Template you’re using.
3. Select the List Section.
4. Find and remove the Phone/Email blocks (example below), then Save.

{{if phone}}
    <li class="sl-phone">
        <i class="icon-mobile"></i>
        <a href="tel:{{:phone}}">{{:phone}}</a>
    </li>
{{/if}}
{{if email}}
    <li class="sl-email">
        <i class="icon-mail"></i>
        <a href="mailto:{{:email}}">{{:email}}</a>
    </li>
{{/if}}

Remove from the InfoBox Template

Repeat the same steps but open the Infobox Section in the Customizer and remove the Phone/Email markup there as well. Agile Store Locator WordPress Plugin

Notes

• This approach is best when you want more control (hide in list, but keep in infobox, etc.).
• Template changes are purely frontend display changes. Agile Store Locator WordPress Plugin

Convert Phone into a CTA Button Without Showing It

If you want to hide the phone text but still provide a “Call Now” button, you can do it in the List Section template.

1. Go to ASL Settings → Customizer
2. Select your template
3. Open the List Section
4. Remove the Phone <li> block and place a CTA button inside the action buttons container.

Use this pattern (keep it inside the action buttons container):

<div class="sl-act-btns mt-3">
    <a class="btn btn-asl s-direction">[Directions]</a>

    {{if phone}}
    <a target="_blank" href="tel:{{:phone}}" class="btn btn-asl">[Call Now]</a>
    {{/if}}

    {{if link}}
    <a target="{{:target}}" class="btn btn-asl btn-asl-outline s-visit-website" href="{{:link}}">[Website]</a>
    {{/if}}

    {{if dist_str}}
    <div class="sl-miles">
        <span class="s-distance">{{:dist_str}}</span>
    </div>
    {{/if}}
</div>

With GTM, you can send key user interactions from your store locator directly to Google Analytics 4 (GA4) or any other connected service—without modifying your core website code.

What This Integration Does

By following this guide, you’ll track the following events in GTM:

• Search events
• Store selection (map/marker clicks)
• Store selection (sidebar/list clicks)
• Direction clicks
• Email link clicks (available since v4.11.19)
• Phone link clicks (available since v4.11.19)

Each event automatically pushes relevant store details into GTM’s dataLayer, so you can analyze user interactions in Google Analytics.

How It Works

Agile Store Locator exposes a JavaScript event hook called asl_event_hook. You can add this function to your site to automatically push event data to GTM’s dataLayer.

When a visitor performs an action—like searching, selecting a store, or clicking email/phone links—your custom asl_event_hook will send structured data to GTM.

You then configure GTM to trigger Google Analytics events based on these pushes.

Step 1 – Add the Google Tag Manager Snippet

First, ensure the GTM container code is installed on your site. Google Tag Manager provides you with code like:

<!-- Google Tag Manager -->
<script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':
new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],
j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=
'https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);
})(window,document,'script','dataLayer','GTM-XXXXXXX');</script>
<!-- End Google Tag Manager -->

<!-- Google Tag Manager (noscript) -->
<noscript><iframe src="https://www.googletagmanager.com/ns.html?id=GTM-XXXXXXX"
height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>
<!-- End Google Tag Manager (noscript) -->

Replace GTM-XXXXXXX with your container ID.

Add this above the closing </head> tag and immediately after the opening <body> tag of your site.

Step 2 – Add the ASL Event Hook Script

Next, add the following JavaScript to your site. You can place it in your theme’s footer, or enqueue it via your CMS or plugin.

This script listens for ASL events and pushes them to dataLayer for GTM:

<script type="text/javascript">
function asl_event_hook(_event) {
  if (!_event || !_event.type) return;

  // 1- SEARCH EVENT
  if (_event.type === 'search') {
    var active_filters = (asl_view.featureFilter.array_ || []).map(function(cat) {
      return cat.name_;
    }).join(',');

    dataLayer.push({
      'event': 'asl_search_event',
      'search_type': 'Address',
      'search_filters': active_filters,
      'address_searched': _event.data.search_text
    });
  }

  // 2- SELECT EVENT (Store list / marker click)
  else if (_event.type === 'select') {
    var store = _event.data || {};
    var category_names = (store.categories || []).map(function(cat) {
      return cat.name;
    }).join(',');

    dataLayer.push({
      'event': 'asl_store_selected',
      'store_id': store.id,
      'store_title': store.title,
      'store_street': store.street,
      'store_city': store.city,
      'store_state': store.state,
      'store_postal_code': store.postal_code,
      'store_country': store.country,
      'store_lat': store.lat,
      'store_lng': store.lng,
      'store_phone': store.phone,
      'store_email': store.email,
      'store_website': store.website,
      'store_categories': category_names,
      'store_link': store.link
    });
  }

  // 3- LIST CLICK SELECT EVENT
  else if (_event.type === 'asl_store_select_click') {
    var store = _event.data || {};
    var category_names = (store.categories || []).map(function(cat) {
      return cat.name;
    }).join(',');

    dataLayer.push({
      'event': 'asl_store_select_click',
      'store_id': store.id,
      'store_title': store.title,
      'store_city': store.city,
      'store_state': store.state,
      'store_country': store.country,
      'store_phone': store.phone,
      'store_email': store.email,
      'store_categories': category_names
    });
  }

  // 4- EMAIL CLICK EVENT (available since v4.11.19)
  else if (_event.type === 'asl_email_click') {
    var store = _event.data || {};

    dataLayer.push({
      'event': 'asl_email_click',
      'store_id': store.id,
      'store_title': store.title,
      'store_email': store.email
    });
  }

  // 5- PHONE CLICK EVENT (available since v4.11.19)
  else if (_event.type === 'asl_phone_click') {
    var store = _event.data || {};

    dataLayer.push({
      'event': 'asl_phone_click',
      'store_id': store.id,
      'store_title': store.title,
      'store_phone': store.phone
    });
  }

  // 6- DIRECTION CLICK EVENT
  else if (_event.type === 'direction') {
    var store = _event.data || {};

    dataLayer.push({
      'event': 'asl_direction_click',
      'store_id': store.id,
      'store_title': store.title,
      'store_street': store.street,
      'store_city': store.city,
      'store_state': store.state,
      'store_postal_code': store.postal_code,
      'store_country': store.country,
      'store_lat': store.lat,
      'store_lng': store.lng
    });
  }
}
</script>

Step 3 – Set Up Google Tag Manager

Once the asl_event_hook is on your site, Google Tag Manager will receive events in its dataLayer.

You can now configure GTM to send these events to Google Analytics 4.

3.1 – Create Data Layer Variables

In GTM:

1. Go to Variables
2. Click New > Data Layer Variable
3. Create variables for:

• store_id
• store_title
• store_street
• store_city
• store_state
• store_postal_code
• store_country
• store_lat
• store_lng
• store_phone
• store_email
• store_website
• store_categories
• store_link
• search_type
• search_filters
• address_searched

These variables let GTM pull data from the dataLayer pushes.

3.2 – Create Custom Event Triggers

Next, create a Custom Event Trigger for each ASL event type:

Event Names to use:

• asl_search_event
• asl_store_selected
• asl_store_select_click
• asl_email_click (available since v4.11.19)
• asl_phone_click (available since v4.11.19)
• asl_direction_click

1. Go to Triggers
2. Click New > Trigger Type: Custom Event
3. Enter the Event Name (e.g. asl_search_event)

Repeat for each event.

3.3 – Create GA4 Event Tags

For each trigger:

1. Go to Tags
2. Click New > Tag Type: Google Analytics: GA4 Event
3. Select your GA4 Configuration Tag
4. Enter an Event Name (e.g. locator_search, store_selected, etc.)
5. Add Event Parameters from your Data Layer Variables

Example for asl_email_click:

• Event Name: store_email_click
• Parameters:
  • store_id
  • store_title
  • store_email

Example for asl_search_event:

• Event Name: locator_search
• Parameters:
  • search_type
  • search_filters
  • address_searched

Link the appropriate Custom Event Trigger to each Tag.

3.4 – Publish Your Container

1. Click Submit in GTM
2. Add a Version Name (e.g. “ASL Events Integration”)
3. Click Publish

Your site is now tracking ASL events via GTM!

Important Disclaimer

Agile Store Locator’s Google Tag Manager integration only pushes event data into the website’s dataLayer.

We do not configure, debug, or manage your Google Tag Manager container, triggers, or Google Analytics setup.

If your GTM or Google Analytics environment does not receive or record these events as expected, it is your responsibility to:

1. Ensure your GTM container is correctly installed on your website
2. Verify that your triggers, variables, and tags are properly configured
3. Debug GTM using built-in tools like the Preview mode

Agile Store Locator support does not include customizing or troubleshooting Google Tag Manager or Google Analytics implementations.

Our plugin guarantees only that it will send the event data to the dataLayer in a standard format.

Important Note:
This guide does not apply to Agile Store Locator, which is sold exclusively on CodeCanyon (Envato Market).
For renewing Agile Store Locator, please log into your Envato account and extend support or re-purchase the license from there.

What Are You Renewing?

Yearly License Renewal

With a Yearly License, your license and support are valid for one year. After expiry:

• You lose access to updates and support.
• Renewing restores both.

How to Renew:

1. Log in to your AgileLogix account.
2. Go to the All Downloads section.
3. Locate the expired license.
4. Click Renew and complete checkout.

Support Renewal for Lifetime License

Lifetime Licenses never expire, but support lasts 1 year. After that:

• You still receive plugin updates.
• You lose access to customer support unless renewed.

Renew Support for $30:

1. Log into AgileLogix.
2. Go to All Downloads.
3. Locate the Lifetime license with Support Expired.
4. Click Renew Support.
5. Complete checkout. Your support will extend 1 year.

How to Check Your Plan

From your AgileLogix account dashboard:

• License Type: “Lifetime” or “Yearly”
• Support Expiry: Shown below each license key

Lost Access to Your Account?

If you no longer have access to your AgileLogix account:

• You can purchase a new license directly from AgileLogix.com.
• After purchase, you can register the new license on your existing site using the plugin’s License Activation panel.

Your plugin and settings will remain intact — you’re simply linking it to a new license key.

Need Help?

Email us: support@agilelogix.com

We’re happy to assist with renewals and support questions!

<li class="pol-lg-4 pol-md-6 pol-sm-12 sl-item" data-id="{{:id}}" tabindex="0" accesskey="{{:id}}">

If you’d like to customize the number of columns, you can easily do this by modifying the Bootstrap column classes.

Steps to Customize:

• Go to ASL Settings > Customizer.
• Select Template 4 from the dropdown.
• Click the “Load Template” button to load the template HTML.
• In the List Section, locate the <li> element that looks like:

<li class="pol-lg-4 pol-md-6 pol-sm-12 sl-item" ...>

Replace the pol-lg-4 class to adjust the number of columns:

• Use pol-lg-3 for 4 columns
• Use pol-lg-6 for 2 columns
• Use pol-lg-12 for 1 column

Example (4-column layout):

<li class="pol-lg-3 pol-md-6 pol-sm-12 sl-item" ...>

• Click Save Template after making changes.

This allows you to tailor the grid layout to better fit your design preferences or available screen space.

• Transform API responses
• Modify endpoints and headers
• Handle pagination
• Map external data into the Agile Store Locator format

Use these filters to customize your synchronization logic when working with platforms like Salesforce, Google Sheets, and REST APIs.

Filters

1. asl_sync_data_row_mapping

Transform each data record before it’s saved into the store database.

add_filter('asl_sync_data_row_mapping', function ($store_inst, $data_row) {
    // Convert "yes" to true boolean
    if (isset($store_inst['is_disabled'])) {
        $store_inst['is_disabled'] = (strtolower($store_inst['is_disabled']) === 'yes') ? 1 : 0;
    }

    // Example: build Facebook URL
    if (isset($data_row['facebookVanityUrl'])) {
        $store_inst['custom-facebook_url'] = "https://www.facebook.com/" . esc_attr($data_row['facebookVanityUrl']) . "/";
    }

    return $store_inst;
}, 10, 2);

Params:

• $store_inst: The processed store data array.
• $data_row: The original raw API data row.

Set the marker_id via hook.

add_filter('asl_sync_data_row_mapping', function ($store_inst, $data_row) {
    
		$store_inst['marker_id'] = 153;

    return $store_inst;
}, 10, 2);

2. asl_sync_prepare_endpoint

Customize or append query parameters to the API endpoint before the request is sent.

add_filter('asl_sync_prepare_endpoint', function ($endpoint_url) {
    $endpoint_url .= '&filter={"meta.folderId":{"$eq":"112810"}}';
    return $endpoint_url;
});

3. asl_sync_logo_url

Update or override the logo URL used during the sync process.

add_filter('asl_sync_logo_url', function ($logo_url, $handler) {
    return str_replace('http://', 'https://', $logo_url);
}, 10, 2);

4. asl_sync_endpoint

Modify the final API endpoint using full sync config context.

add_filter('asl_sync_endpoint', function ($endpoint, $config) {
    return $endpoint . '?apikey=' . $config['sync_key'];
}, 10, 2);

5. asl_sync_request_data

Alter the request payload (body) before it is sent to the API.

add_filter('asl_sync_request_data', function ($data, $config) {
    $data['region'] = 'Middle East';
    return $data;
}, 10, 2);

6. asl_sync_request_headers

Customize or add headers to the outgoing API request.

add_filter('asl_sync_request_headers', function ($headers, $config) {
    $headers['Authorization'] = 'Bearer ' . $config['bearer_token'];
    return $headers;
}, 10, 2);

7. asl_sync_api_request_params

Modify the full set of parameters used in the request.

add_filter('asl_sync_api_request_params', function ($params) {
    $params['timeout'] = 30;
    return $params;
});

8. asl_sync_raw_response

Filter or log the raw response before it’s parsed or mapped.

add_filter('asl_sync_raw_response', function ($response, $params) {
    error_log(print_r($response, true));
    return $response;
}, 10, 2);

9. asl_sync_request_pagination

Add logic to recursively fetch all pages from a paginated API.

add_filter('asl_sync_request_pagination', function ($responseData, $apiClient, $params) {
    $all = $responseData['response']['entities'];
    $max = 10;

    while (isset($responseData['response']['pageToken']) && $max-- > 0) {
        $params['endpoint'] .= '&pageToken=' . $responseData['response']['pageToken'];
        $responseData = $apiClient->makeApiRequest($params);

        if (isset($responseData['response']['entities'])) {
            $all = array_merge($all, $responseData['response']['entities']);
        }
    }

    $responseData['response']['entities'] = $all;
    return $responseData;
}, 10, 3);

10. asl_sync_completed_event (Action)

Run custom logic after a sync completes.

add_action('asl_sync_completed_event', function ($sync_key, $settings) {
    // Send admin notification or log sync summary
});

11. asl_sync_skip_data_row

To create a criteria to skip certain rows from import based on condition.

add_filter('asl_sync_skip_data_row', function ($should_skip, $row, $sync_id) {

	// Skip if the Sync_To_Store_Listing__c flag is missing or not true
	if (!isset($row['Sync_To_Store_Listing__c']) || strtolower($row['Sync_To_Store_Listing__c']) !== 'true') {
			return true; // Skip this record
	}

	return false; // Sync this record
}, 10, 3);

12. asl_sync_validate_timestamp (New in v1.0.6)

Control whether a data row should be blocked by timestamp validation during sync. Returning false from this filter bypasses the “updated_on vs last_exec_time_stamp” check so the row will be processed even if its timestamp is not newer.

Example: One-time backfill (bypass only once)

Use a static flag to ensure the bypass happens once per run (recommended to avoid reprocessing every row repeatedly).

/**
 * One-time bypass to force a backfill on the first row only.
 * Version: v1.0.6+
 */
function asl_force_sync_timestamp_bypass_once( $validate, $row, $sync_id, $row_ts, $last_ts ) {
 
    return false; // bypass timestamp validation ONCE
}
add_filter( 'asl_sync_validate_timestamp', 'asl_force_sync_timestamp_bypass_once', 10, 5 );

Developer Notes

• Use filters inside a custom plugin or your theme’s functions.php.
• Always validate and sanitize external data before saving.
• Test filters with a manual sync run using the “Run Sync Now” button.

Need Help?

For custom integration support or additional hooks, reach out at support@agilelogix.com