Google Analytics
Requirements: Any paid subscription
Also see:
Add a Responsive Interface to Your Site
To set up an interface to send activity tracked on Bullseye's Searches By Location Report to Google Analytics using GA4, refer to the video below. You may also refer to the rest of this article for written instructions, instructions on implementing tracking with Google Tag Manager, and more details about the metrics offered in the Searches By Location Report.
The following video and instruction is accurate as of the time of the writing of this article. Google may make slight changes from time to time.
With a subscription, You can configure your interfaces to send captured data from the Searches By Locations Report to Google Analytics using GA4 measurement IDs. Data tracked in Google Analytics includes the following:
Google Analytics Events Actions
| Name | Description | Parameters |
| click_contact_link | This event is triggered by clicking the contact link that is not configured for lead capture. | location_id Location_name eventcategory |
| click_map_pin | This event is triggered by clicking the map pin on the map. | location_id Location_name search_request_id |
| click_open_lead_form | This event is triggered by clicking on a Bullseye integrated lead form link. | location_id Location_name search_request_id |
| click_social_facebook | This event is triggered by clicking on a Facebook icon on a local page. | location_id Location_name eventcategory |
| click_social_instagram | This event is triggered by clicking on an Instagram icon on a local page. | location_id Location_name eventcategory |
| click_social_pinterest | This event is triggered by clicking on a Pinterest icon on a local page. | location_id Location_name eventcategory |
| click_social_twitter | This event is triggered by clicking on an X icon on a local page. | location_id Location_name eventcategory |
| click_social_yelp | This event is triggered by clicking on a Yelp icon on a local page. | location_id Location_name eventcategory |
| directions_click | This event is triggered by clicking the directions link. | url_link location_id location_name search_request_id |
| email_click | This event is triggered by clicking the Email link. | location_id location_name search_request_id |
| event_url_click | If the interface is configured to display events, this event is triggered by clicking the Event link. | search_request_id |
| click_favorite | If the interface is configured to display favorites, this event is triggered when a location is "favorited". | location_id location_name search_request_id |
| bullseye_form_lead_submitted | This event is triggered by submitting a Bullseye integrated lead form. | form_id locations lead_source |
| generate_lead | This event measures when a lead has been generated. This event is not Bullseye's own, it is a Google event. | Google Analytics Generated event. Link to the event documentation |
| location_url_click | This event is triggered by clickin the Website link. | url location_id location_name search_request_id |
| locator_search | This event is triggered when a search is performed by a user. This event occurs when the locator is first loaded if autosearch is enabled, as welll as when a manual search occurs. Note: If autosearch is enabled, page refreshes will increase this count. | city postalcode keyword radius state countryname category_filter search_type autocomplete_selection search_term |
| locator_search_result | This event triggered when an auto or manual search occurs. This event sends a count of locations that have been returned from the search. | distance location_id location_name search_request_id |
| more_info_click | If the interface is configured with local pages, this event is triggered by clicking the More Info link. | eventCategory location_id location_name |
| view_phone_click | If the interface has the "Display as link" option enabled, this event is triggered by clicking the "View phone number" button to reveal the phone number. | phone location_id location_name search_request_id |
| phone_number_click | This event is triggered by clicking the phone number button in order to attempt to dial the number. | phone location_id location_name search_request_id |
| promotion_url_click | If the interface is configured to display promotions, this event is triggered by clicking the Promotion link. | promotion_name search_request_id |
| select_location | This event is triggered by clicking on the location in the results list in order to display the location detail above the corresponding pin on the map. | location_id location_name search_request_id |
| click_unfavorite | If the interface is configured to display favorites, this event is triggered when a location is "unfavorited". | location_id location_name search_request_id |
If your locator is configured to display standard landing pages, the following Event Actions are also available and link to activity taken on the Landing page:
- Landing page email clicks
- Landing page website clicks
- Landing page contact clicks
- Landing page phone number clicks
In Google Analytics, the Event count by Event name section on the Realtime Report shows the metrics for any Events that have occurred during the currently selected timeframe:
Click on any metric to see more imformation about it. For example, click on location_url_click, then location_name to see the location that was clicked.
Configuring GA4 Analytics in Your Bullseye Interface
To find the Measurement ID in GA4:
- Sign in to your Analytics account.
- Click Admin.
- Select an account from the menu in the ACCOUNT column.
- Select a property from the menu in the PROPERTY column.
- Under PROPERTY, click Data Streams
- Select a Data Stream
The Measurement ID is at the top of the page:
Copy the Tracking or Measurement ID exactly as it is in Google Analytics, including the "G" and any dashes.
Next, log in to your Bullseye account, and navigate to the Interfaces page. Select Edit on the appropriate interface. You will need to enter the code along with the Host URL on the General tab of the Options page of the interface builder:
- Google Analytics Code: Paste or enter the code provided by your Google Analytics account.
- Host URL: Enter the exact URL of the page where the interface is going to be IFramed. The complete URL must be provided including "http/https". NOTE: This URL will also be used for the breadcrumbs to return to the interface from City or Local Page if they're used with the interface.
If you are enabling Google Analytics for the first time, or upgrading from GA3 to GA4, you will need to re-implement the Bullseye Iframe code on your site. You can find the updated code in the Publish tab in the interface builder. Just copy the code and paste into your website.
The new code is necessary because GA4 doesn't have a mechanism for store third-party cookies , so our iframe embed code now includes a "listener" script that sends events from the iframe to the host page, and lets the host page send the events to Google Analytics. This is what it looks like:
Configure GA4 Analytics with Google Tag Manager
Configure Google Tag Manager to recognize events
Sign in to your Tag Manager account. In the console, select the Account and Container you want to configure, then go to the Admin menu
Go to the import section of the Google Tag Manager admin
Download the Bullseye template file (JSON) or import directly from the public URL:
Select whether to import the file into a new or exiting container, and whether to Overwrite or Merge the imported tags with existing tags.
We recommend that you import into a New workspace, or use the “Merge” method to avoid accidentally deleting a variable or TAG. If merging, it is unlikely that you will have any conflicting tags, as they are all uniquely names and prepended with "bullseye".
Check to ensure that the following elements are imported:
- 23 Tags
- 24 Triggers
- 24 Variables
Click Confirm to import the file.
Next, find the variable called "Bullseye - MeasureID".
Click the Bullseye - GA4 MeasureId to open the variable, then click the pencil icon to edit the Measurement ID. Update the value of the variable by pasting the Measurement ID from Google analytics here.
Be sure to Submit the new or updated container before the next step:
In the next step we'll configure the interface in Bullseye Locations with the GTM ID and host URL. You can find the GTM ID in Google Tag Manager at the top of the page in the console:
Copy the GTM ID exactly as it is in Google Tag Manager.
Next, log in to your Bullseye account, and navigate to the Interfaces page. Select Edit on the appropriate interface. You will need to enter the code along with the Host URL on the General tab of the Options page of the interface builder:
- GTM ID: Paste or enter the code provided by your Google Tag Manager account.
- Host URL: Enter the exact URL of the page where the interface is going to be IFramed. The complete URL must be provided including "http/https". NOTE: This URL will also be used for the breadcrumbs to return to the interface from City or Local Page if they're used with the interface.
If you are enabling Google Tag Manager for the first time, or migrating from Google Analytics to GTM, you will need to re-implement the Bullseye Iframe code on your site. You can find the updated code in the Publish tab in the interface builder. Just copy the code and paste into your website.