{"id":3124,"date":"2026-03-30T11:39:10","date_gmt":"2026-03-30T11:39:10","guid":{"rendered":"https:\/\/easyfinder.ai\/?post_type=docs&p=3124"},"modified":"2026-05-13T09:47:35","modified_gmt":"2026-05-13T09:47:35","password":"","slug":"how-to-capture-easyfinder-events-in-google-tag-manager","status":"publish","type":"docs","link":"https:\/\/easyfinder.ai\/nl\/docs\/how-to-capture-easyfinder-events-in-google-tag-manager\/","title":{"rendered":"EasyFinder events vastleggen in Google Tag Manager"},"content":{"rendered":"

Every time someone sees search results on your site, EasyFinder sends an event with useful info: what they searched for, how many results came back, and how many filters they used. With a little setup in Google Tag Manager (GTM), you can capture all of it and forward it to the tools you use, like Google Analytics, Meta Pixel, or any other tag.<\/p>\n

 <\/p>\n

What EasyFinder Sends<\/h3>\n

Each time a search result page is shown, EasyFinder pushes this event to the data layer:<\/p>\n

\/\/ Example event from EasyFinder\r\n{\r\n  event: \"view_search_results\",\r\n  search_term: \"running shoes\",\r\n  ef_total_exact_results: 24,\r\n  ef_total_relaxed_results: 8,\r\n  ef_search_method: \"search\",\r\n  ef_total_active_filters: 2,\r\n  ef_source: \"easyfinder\"\r\n}\r\n<\/pre>\n
Here’s what each field means:<\/p>\n\n\n\n\n\n\n\n\n\n\n
Field<\/th>\nWhat it tells you<\/th>\n<\/tr>\n<\/thead>\n
search_term<\/code><\/td>\nThe word or phrase the user searched for.<\/td>\n<\/tr>\n
ef_total_exact_results<\/code><\/td>\nNumber of results that exactly match the search.<\/td>\n<\/tr>\n
ef_total_relaxed_results<\/code><\/td>\nExtra results found through smart (semantic) matching.<\/td>\n<\/tr>\n
ef_search_method<\/code><\/td>\nWhich part of EasyFinder triggered the search (for example search<\/code> or widget<\/code>).<\/td>\n<\/tr>\n
ef_total_active_filters<\/code><\/td>\nHow many filters the user had active at that moment.<\/td>\n<\/tr>\n
ef_source<\/code><\/td>\nAlways easyfinder<\/code>. Handy to separate these events from other search events.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
 <\/p>\n
Step 1. Open Google Tag Manager<\/h3>\n
Log in to tagmanager.google.com<\/strong> and open the container connected to your website.
\nIf you don’t have GTM installed yet, set that up first by following Google’s quick-start guide.<\/p>\n
 <\/p>\n
Step 2. Add the EasyFinder Fields as Variables<\/h3>\n
GTM needs to know which fields to read from the event.
\nGo to Variables<\/strong> \u2192 New<\/strong> \u2192 Data Layer Variable<\/strong>.
\nCreate one variable per field. For each one, fill in the Data Layer Variable Name<\/strong> exactly like this:<\/p>\n
    \n
  • search_term<\/code><\/li>\n
  • ef_total_exact_results<\/code><\/li>\n
  • ef_total_relaxed_results<\/code><\/li>\n
  • ef_search_method<\/code><\/li>\n
  • ef_total_active_filters<\/code><\/li>\n
  • ef_source<\/code><\/li>\n<\/ul>\n
    Give each variable a clear name (e.g. DLV - search_term<\/code>) and save.<\/p>\n
     <\/p>\n
    Step 3. Create a Trigger<\/h3>\n
    Now tell GTM when to react.
    \nGo to Triggers<\/strong> \u2192 New<\/strong> \u2192 Custom Event<\/strong>.
    \nFill in:<\/p>\n
      \n
    • Event name:<\/strong> view_search_results<\/code><\/li>\n
    • This trigger fires on:<\/strong> All Custom Events<\/li>\n<\/ul>\n
      Save it as CE - view_search_results<\/code>.<\/p>\n
       <\/p>\n
      Step 4. Create a Tag<\/h3>\n
      Now build the tag that sends the event to the tool of your choice. The most common setup is a Google Analytics (GA4) tag.
      \nGo to Tags<\/strong> \u2192 New<\/strong> \u2192 Google Analytics: GA4 Event<\/strong>.
      \nFill in:<\/p>\n
        \n
      • Measurement ID:<\/strong> your GA4 ID (looks like G-XXXXXXX<\/code>)<\/li>\n
      • Event Name:<\/strong> view_search_results<\/code><\/li>\n<\/ul>\n
        Under Event Parameters<\/strong>, add a row for each field:<\/p>\n\n\n\n\n\n\n\n\n\n\n
        Parameter Name<\/th>\nValue<\/th>\n<\/tr>\n<\/thead>\n
        search_term<\/code><\/td>\n{{DLV - search_term}}<\/code><\/td>\n<\/tr>\n
        ef_total_exact_results<\/code><\/td>\n{{DLV - ef_total_exact_results}}<\/code><\/td>\n<\/tr>\n
        ef_total_relaxed_results<\/code><\/td>\n{{DLV - ef_total_relaxed_results}}<\/code><\/td>\n<\/tr>\n
        ef_search_method<\/code><\/td>\n{{DLV - ef_search_method}}<\/code><\/td>\n<\/tr>\n
        ef_total_active_filters<\/code><\/td>\n{{DLV - ef_total_active_filters}}<\/code><\/td>\n<\/tr>\n
        ef_source<\/code><\/td>\n{{DLV - ef_source}}<\/code><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
        Under Triggering<\/strong>, pick the CE - view_search_results<\/code> trigger. Save the tag.<\/p>\n
        Using a different tool like Meta Pixel or a custom HTML tag? You can still use the same trigger and variables. Just pick the tag type that fits your tool.<\/div>\n
         <\/p>\n
        Step 5. Test and Publish<\/h3>\n
        Click Preview<\/strong> in GTM and open your site. Do a search and check that the event fires and all values look correct.
        \nWhen everything looks good, click Submit<\/strong> and publish your container.<\/p>\n
        If the tag doesn’t fire, check that the event name matches view_search_results<\/code> exactly. It’s case-sensitive.<\/div>\n
        That’s it. Your EasyFinder events are now flowing through Google Tag Manager and ready to be used in any tool you connect.<\/p>\n
        If you’re sending these events to Google Analytics, there’s one more step on the GA4 side to make the ef_*<\/code> fields visible in your reports. Check out our guide on capturing EasyFinder events in Google Analytics.<\/div>","protected":false},"excerpt":{"rendered":"
        Every time someone sees search results on your site, EasyFinder sends an event with useful info: what they searched for, how many results came back, and how many filters they used. With a little setup in Google Tag Manager (GTM), you can capture all of it and forward it to the tools you use, like […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"inline_featured_image":false,"footnotes":""},"doc_category":[14],"doc_tag":[],"class_list":["post-3124","docs","type-docs","status-publish","hentry","doc_category-integrations"],"year_month":"2026-09","word_count":620,"total_views":0,"reactions":{"happy":0,"normal":0,"sad":0},"author_info":{"name":"admin","author_nicename":"hassan","author_url":"https:\/\/easyfinder.ai\/nl\/author\/hassan\/"},"doc_category_info":[{"term_name":"Integrations","term_url":"https:\/\/easyfinder.ai\/nl\/docs-category\/integrations\/"}],"doc_tag_info":[],"_links":{"self":[{"href":"https:\/\/easyfinder.ai\/nl\/wp-json\/wp\/v2\/docs\/3124","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/easyfinder.ai\/nl\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/easyfinder.ai\/nl\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/easyfinder.ai\/nl\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/easyfinder.ai\/nl\/wp-json\/wp\/v2\/comments?post=3124"}],"version-history":[{"count":11,"href":"https:\/\/easyfinder.ai\/nl\/wp-json\/wp\/v2\/docs\/3124\/revisions"}],"predecessor-version":[{"id":3368,"href":"https:\/\/easyfinder.ai\/nl\/wp-json\/wp\/v2\/docs\/3124\/revisions\/3368"}],"wp:attachment":[{"href":"https:\/\/easyfinder.ai\/nl\/wp-json\/wp\/v2\/media?parent=3124"}],"wp:term":[{"taxonomy":"doc_category","embeddable":true,"href":"https:\/\/easyfinder.ai\/nl\/wp-json\/wp\/v2\/doc_category?post=3124"},{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/easyfinder.ai\/nl\/wp-json\/wp\/v2\/doc_tag?post=3124"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}