• Dynamically Switching Google Tag Manager containers

  MetaLocator supports Google Tag Manager installation by simply copying and pasting the Google Tag Manager container ID into the setting shown below: [](https://downloads.intercomcdn.com/i/o/yn1vvwtq/1226476591/19b6d2e89abf4151cd6afa9c8b1d/image.png?expires=1794512700&signature=0f980d6e971d48dddcc9ff4dd537eab3fe3c3de6ea19470d74303ed9afca14bd&req=dSIlEM15m4RWWPMW1HO4zbAwAEjURFew readers

• Using GA4 & MetaLocator

  MetaLocator tracks various events as part of its built-in analytics system. If you are using GA4 on your Web site, MetaLocator Analytics events can be automatically sent to your Google Analytics 4 property by specifying the GA4 Measurement ID in your Interface Settings as shown below: [![](https://storage.crisp.chat/users/helpdesk/website/-/c/0/d/6/c0d65eb6dcded800/9b4eb9c4-8059-470a-9f29-872ce3_18Few readers

• Using the Search Demand Heat Map

  Under the Analytics tab, an option called Heat Map displays a map that shows a point on the map for each search performed by your visitors. The point is located at the geographic center of the user's search term. This is typically the center of a postal code. To load the heat map, click Analytics > Heat Map [](https://downloads.intercomcdn.com/i/o/754690147/312c78fFew readers

• How to Investigate Unusual Spikes in Analytics

  This article describes features available to Enterprise users only. Have you noticed an unexpected spike in your MetaLocator analytics, such as a sudden increase in searches, click-to-call events, or other user interactions? ​ MetaLocator's Advanced Analytics Dashboard allows you to investigate these spikes by reviewing activity on a specific date, identifying where traffic originated, and examining individual visit logs. This can help you determine whether the increase was caused by legFew readers

• Introduction to MetaLocator Analytics

  MetaLocator tracks activity inside Interfaces to help our customers understand user behavior and overall performance and value. Users are greeted with a summary of analytics behavior on the MetaLocator dashboard. [](https://downloads.intercomcdn.com/i/o/539612732/def2aba6e9ded80f5b6815df/image.png?expires=1794512700&signature=8f564a7bd43e13a1209d6456503525430b1e6adeb2e925Few readers

• Analytics for Where to Buy

  The material contained in this document and any material or information disclosed during discussions of the contents represents the proprietary, confidential information pertaining to our services, methodologies and strategy. Disclosure of this information to any third party is strictly prohibited. Analytics Overview [![](https://metalocator.intercom-attachments-1.com/i/o/640207364/53d02ee29e46ec2d7e007082/analytics_overview-300x147.png?expires=1794512700&signature=e12df63405455ee3d0f073b48Few readers

• Using Adobe Analytics with MetaLocator

  MetaLocator can send analytics events to Adobe Analytics through the Adobe Data Layer on the host page where your MetaLocator interface is installed. This article explains how to enable Adobe Analytics event forwarding from MetaLocator to your website’s parent page. Overview MetaLocator interfaces are commonly embedded in a website using an IFRAME. Because Adobe Analytics is normally installed on the website page itself, analytics events should be sent from the host page, not directly fromFew readers

• Account Performance Report

  Applies To Enterprise accounts only Introduction The Account Performance Report is a monthly summary email sent automatically to Enterprise Administrators and Group Administrators. It provides insight into locator performance and lead activity over the previous 30 days. This report highlights changes in key engagement metrics such as Clicks to Call, Directions, and Leads, helping account managers quickly identify trends in user interaction and lead response. RFew readers

• Using Google Tag Manager and GA4 with MetaLocator

  To use GA4 and MetaLocator together simply, without involving Google Tag Manager, follow these instructions. MetaLocator and GA4 work well together, as both platforms track analytics events in an event-driven model. Older analytics platforms, like Universal Analytics, focus on Page Views. However, most actions in MetaLocator don't require a page load, such as a Click to Call event, or an Open Marker Window event, andFew readers

• Tracking internal conversion sources with Where to Buy

  Most MetaLocator customers use Where to Buy to display opportunities to purchase from third parties.  However, for some customers, they present themselves as a purchase option within the Where to Buy Interface alongside third party options. Tracking purchases that pass through the MetaLocator Where to Buy interface must be reportable in the Website's analytics as a segment, allowing our customers to see which users purchased through Where to Buy, as opposed to any other direct methods availableFew readers

• Analytics API

  Introduction MetaLocator tracks nearly all events that occur within the customer-facing software.  These events are tracked in our internal analytics platform and optionally in your Google Analytics. Authentication The Analytics API uses a token-based authentication method which is available to Enterprise accounts.  All requests must also include a "siteId" parameter.  To obtain these values, login as the account administrator, or a user with Analytics access.  Click Analytics, then OpeFew readers

• Exporting Analytcs

  Follow these simple steps to export your analytics data and analyze it or create your reports. Step 1: Navigate to Analytics In the left-hand menu, click on Analytics > Analytics to access the data you wish to export. Step 2: Select the Section to Export Browse through the available sections and select the one you would like to export. Hover over the section to reveal more options. Step 3: Export the Data Look for the export icon, which is an arrow coming out of a squaFew readers

• Tracking segmented analytics with MetaLocator

  MetaLocator allows you to track searches, clicks and other interactions on a per location and per Interface basis.  This guide explores the various methods for reporting usage in MetaLocator.  MetaLocator allows for tracking using our internal analytics, which is enabled by default, Google Analytics and Google Tag Manager.  To enable tracking for Google Analytics, check out this tutorial.  To view the internal analytiFew readers

• How to add and work with a widget in the Analytics Dashboard

  This article explains how to add a widget to the MetaLocator Analytics Dashboard. Further, this demonstrates how to adjust the date range for reporting, reviewing the report online and how to capture the report in a format suitable for Excel. MetaLocator analytics uses the well known Piwik/Matomo platform. The Analytics Dashboard is found under the MetaLocator tab labeled Analytics. This is included with every MetaLocator plan. [![](https://storage.crisp.chat/users/helpdesk/website/-/Few readers

• Tracking Location Impressions

  When a location is displayed in the search results, you may want to track that as a separate event. These events don't indicate any user interaction, but are often referred to "Impressions". To setup tracking for location impressions: Open the Interface Builder Under Analytics, set "Track Impressions?" to Yes. Under Results > Edit List > click Add Field and choose Impression Tracker from the Special Fields tab. This will insert an invisible tracker field into the results card. The imFew readers

• Debugging Google Analytics

  When MetaLocator events don’t appear in GA4, the issue is often related to how GA4 or Google Tag Manager has been installed in combination with MetaLocator's Interface Builder settings. Below are common reasons and troubleshooting paths. Some Reasons Why MetaLocator Events may not appear in GA4 The Interface Builder settings are not configured correctly for the GA4 installation scenario Google Tag Manager is installed on the host page, but is not listening to MetaLocator Events. DeFew readers

• Privacy FAQ

  On May 25, 2018, a new data privacy law called the General Data Protection Regulation(GDPR) came into force, impacting how businesses collect and process data from individuals in the EU. In preparation for the GDPR, MetaLocator updated its policies, practices and tools in accordance with these new regulations.  The provisions of the GDPR apply to any entity that processes personal data of individuals in the EuropeanFew readers

• Reporting Features

  MetaLocator has extensive reporting options.  We report metrics on all aspects of your data, visitors, searches and traffic directly in your MetaLocator account and/or Google Analytics. Our reporting features include: Integrated Analytics:  This dashboard includes hundreds of Web visitor analytics such as Visits, User Location, Visit Length, Referrer, Search Terms, Location Clicks, Link Clicks etc.  To see your integrated analytics, login to your account and click "Analytics" on the main toolbFew readers

• Confirmed conversion reporting timeline

  MetaLocator tracks confirmed conversions via affiliate programs and manual back-fills.  The timeline of when a given purchase will appear in the Analytics Dashboard can vary by retailer and affiliate program.  This article discusses the factors that influence the reporting timeline of confirmed conversions. Timeline elements: Transaction time - The date and time that a visitor purchased a product from a 3rd party retailer Reporting time - The date and time that the 3rd party retailer reporFew readers

• Using Google Tag Manager with MetaLocator

  MetaLocator supports installation of Google Tag Manager inside the IFRAME. We also support communication with the dataLayer on the host page. This article helps determine which strategy is best for your application. Google Tag Manager inside the MetaLocator iframe MetaLocator can load Google Tag Manager directly inside the embedded MetaLocator iframe. In this configuration, the locator has its own GTM container and its own dataLayer, separate from the parent website. ​ This means eventFew readers