[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fnwBV3tEOOwXDWLeJRV8_fakQjH90uUlwf7EzsAU-rl8":3},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":11,"num_ratings":11,"last_updated":13,"tested_up_to":14,"requires_at_least":15,"requires_php":16,"tags":17,"homepage":23,"download_link":24,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27,"vulnerabilities":28,"developer":29,"crawl_stats":26,"alternatives":34,"analysis":124,"fingerprints":201},"tag-scout","Tag Scout","1.0.1","zemraplugins","https:\u002F\u002Fprofiles.wordpress.org\u002Fzemraplugins\u002F","\u003Cp>Tracking scripts can hide in many places — plugins, themes, and custom code.\u003Cbr \u002F>\nTag Scout shows you exactly where each tracking code originates.\u003C\u002Fp>\n\u003Cp>It scans any URL on your site and detects:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>Google Analytics 4 (GA4)\nUniversal Analytics (legacy)\nGoogle Tag Manager (GTM)\nMeta Pixel\nHotjar\nMicrosoft Clarity\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Tag Scout searches your WordPress installation for matching fragments in:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>wp_options (option values)\u003C\u002Fli>\n\u003Cli>wp_posts (post content across all post types, including Code Snippets CPT)\u003C\u002Fli>\n\u003Cli>wp_postmeta (meta values: page builders, ACF, etc.)\u003C\u002Fli>\n\u003Cli>Legacy Code Snippets table ({prefix}snippets), if present\u003C\u002Fli>\n\u003Cli>Key theme files: header.php, footer.php, functions.php in parent and child themes\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Results are shown as clean cards with:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>Provider name (GA4, UA, GTM, etc.)\nID (Measurement ID, UA property, GTM container, etc.)\nSnippet preview\n“Found in…” list (options, posts, postmeta, Code Snippets, theme files)\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Tag Scout is read-only. It never changes your database or files — it just helps you find where to fix things.\u003C\u002Fp>\n\u003Cp>Tag Scout does not connect to any third-party APIs or services. It only requests your own site’s URL using wp_remote_get() and scans that HTML for known tracking patterns.\u003C\u002Fp>\n","Find out where your tracking code is installed. Tag Scout scans your front-end HTML and shows where tracking scripts live in your WordPress install.",0,149,"","6.9.4","5.8","7.4",[18,19,20,21,22],"debugging","scripts","tag-manager","tags-analytics","tracking","https:\u002F\u002Fzemraplugins.com\u002Ftag-scout\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ftag-scout.1.0.1.zip",100,null,"2026-03-15T10:48:56.248Z",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":30,"total_installs":11,"avg_security_score":25,"avg_patch_time_days":31,"trust_score":32,"computed_at":33},1,30,94,"2026-04-04T15:23:26.821Z",[35,52,72,91,109],{"slug":36,"name":37,"version":38,"author":39,"author_profile":40,"description":41,"short_description":42,"active_installs":25,"downloaded":43,"rating":11,"num_ratings":11,"last_updated":44,"tested_up_to":14,"requires_at_least":45,"requires_php":16,"tags":46,"homepage":49,"download_link":50,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":51},"tracking-for-divi","Tracking for Divi","1.1.1","Kuba Serafinowski","https:\u002F\u002Fprofiles.wordpress.org\u002Fkubawtf\u002F","\u003Cp>Ever wanted to track the built-in contact form from Divi? If you tried using Google Tag Manager’s built-in form submit events to do it you probably noticed an inflated number of events flowing.\u003C\u002Fp>\n\u003Cp>This is because the form submission event is triggered even if there are form validation errors or the server returns another error.\u003C\u002Fp>\n\u003Cp>Since Divi doesn’t provide any JavaScript events to hook into there is no straightforward way to find out if a message has actually been sent.\u003C\u002Fp>\n\u003Cp>To get around this, this plugin listens to the network communication that is happening underneath. It’s based on the same mechanism Divi itself uses.\u003C\u002Fp>\n\u003Cp>There are three options now:\u003C\u002Fp>\n\u003Col>\n\u003Cli>a \u003Ca href=\"https:\u002F\u002Fdevelopers.google.com\u002Ftag-platform\u002Ftag-manager\u002Fdatalayer\" rel=\"nofollow ugc\">dataLayer\u003C\u002Fa> event\u003C\u002Fli>\n\u003Cli>a \u003Ca href=\"https:\u002F\u002Fsupport.google.com\u002Fanalytics\u002Fanswer\u002F12229021\" rel=\"nofollow ugc\">Google Analytics 4 event\u003C\u002Fa> (using gtag.js)\u003C\u002Fli>\n\u003Cli>a \u003Ca href=\"https:\u002F\u002Fsupport.google.com\u002Fgoogle-ads\u002Fanswer\u002F1722022\" rel=\"nofollow ugc\">Google Ads conversion\u003C\u002Fa> (also using gtag.js)\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>You can use either one of them or event all of them together.\u003C\u002Fp>\n\u003Cp>You’ll be able to customize the dataLayer variable if you’re \u003Ca href=\"https:\u002F\u002Fdevelopers.google.com\u002Ftag-platform\u002Ftag-manager\u002Fdatalayer#rename_the_data_layer\" rel=\"nofollow ugc\">not using the standard naming\u003C\u002Fa>, and the event names, separately for dataLayer and gtag.\u003C\u002Fp>\n\u003Ch4>Data layer reporting\u003C\u002Fh4>\n\u003Cp>The structure of the object pushed to the dataLayer is the following, with the default naming:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>{\n  event: \"contact_form_submit\",\n  formId: string,\n  postId: number,\n  formData: {\n    name: string,\n    email: string,\n    message: string,\n  },\n  allFormData?: Record\u003Cstring, unknown>, \u002F\u002F when \"Include all form data\" is enabled\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>It’s up to you to use or discard the form data.\u003C\u002Fp>\n\u003Ch4>Google Analytics 4 reporting\u003C\u002Fh4>\n\u003Cp>The Google Analytics event is sent with flattened parameters:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>gtag(\n  \"event\",\n  \"contact_form_submit\",\n  {\n    form_id: \"divi\u002Fcontact-form-0\",\n    name: \"John\",\n    email: \"john@example.com\",\n    message: \"Hello\",\n    \u002F\u002F additional fields when \"Include all form data\" is enabled\n  }\n);\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Form data (name, email, message) is included by default. When “Include all form data” is enabled, all form fields are flattened into the event parameters.\u003C\u002Fp>\n\u003Cp>\u003Cem>This will only work if you have a \u003Ca href=\"https:\u002F\u002Fsupport.google.com\u002Fgoogle-ads\u002Fanswer\u002F11994839\" rel=\"nofollow ugc\">Google Tag\u003C\u002Fa> already deployed on the website i.e. the \u003Ccode>gtag()\u003C\u002Fcode> function is available.\u003C\u002Fem> Otherwise, you will see a warning in your console like this:\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>Tracking for Divi: gtag event failed, gtag is not defined\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Ch4>Google Ads conversion reporting\u003C\u002Fh4>\n\u003Cp>The Google Ads conversion is sent like so:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>gtag(\n  \"event\",\n  \"conversion\",\n  {\n    send_to: \"\u003Cconversion_id>\u002F\u003Cconversion_label>\",\n  }\n);\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>There is no default for \u003Ccode>conversion_id\u003C\u002Fcode> and \u003Ccode>conversion_label\u003C\u002Fcode> as they are always created individually in Google Ads.\u003C\u002Fp>\n\u003Cp>\u003Cem>This will only work if you have a \u003Ca href=\"https:\u002F\u002Fsupport.google.com\u002Fgoogle-ads\u002Fanswer\u002F11994839\" rel=\"nofollow ugc\">Google Tag\u003C\u002Fa> already deployed on the website i.e. the \u003Ccode>gtag()\u003C\u002Fcode> function is available.\u003C\u002Fem> Otherwise, you will see a warning in your console like this:\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>Tracking for Divi: Google Ads conversion event failed, gtag is not defined\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cp>\u003Cstrong>Note:\u003C\u002Fstrong> This plugin hasn’t been thoroughly tested with Divi forms that redirect to a success page. The tracking works just as well, however the redirect could interrupt the tracking flow e.g. if Google Tag Manager has a lot of logic and doesn’t trigger the tags in time. The tags themselves these days \u003Ca href=\"https:\u002F\u002Fsupport.google.com\u002Fanalytics\u002Fanswer\u002F9964640#event-batching\" rel=\"nofollow ugc\">use the beacon API\u003C\u002Fa> (see \u003Ca href=\"https:\u002F\u002Fdeveloper.mozilla.org\u002Fen-US\u002Fdocs\u002FWeb\u002FAPI\u002FBeacon_API\" rel=\"nofollow ugc\">MDN\u003C\u002Fa> for reference) so the requests shouldn’t be interrupted as long as they are fired before website unload.\u003C\u002Fp>\n","Track successful Divi contact form submissions with dataLayer events, Google Analytics, and Google Ads conversions.",209,"2026-03-04T19:33:00.000Z","5.3",[47,48,20,22],"datalayer","divi","https:\u002F\u002Fgithub.com\u002Fzizzfizzix\u002Ftracking-for-divi","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ftracking-for-divi.1.1.1.zip","2026-03-15T15:16:48.613Z",{"slug":53,"name":54,"version":55,"author":56,"author_profile":57,"description":58,"short_description":59,"active_installs":60,"downloaded":61,"rating":25,"num_ratings":30,"last_updated":13,"tested_up_to":62,"requires_at_least":63,"requires_php":64,"tags":65,"homepage":70,"download_link":71,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"tracking-code-for-google-tag-manager","Tracking Code for Google Tag Manager","1.0.0","Clayton Collie","https:\u002F\u002Fprofiles.wordpress.org\u002Fclaytoncollie\u002F","\u003Cp>Tracking Code For Google Tag Manager is a simple, lightweight WordPress plugin for inserting your Google Tag Manager tracking code. The plugin does one thing and one thing only; prints the standard Google Tag Manager tacking script to the \u003Ccode>\u003Chead>\u003C\u002Fcode> of your website. To insert your container ID, navigate to Settings > General and then scroll to the bottom of the page.\u003C\u002Fp>\n\u003Ch3>Composer\u003C\u002Fh3>\n\u003Cpre>\u003Ccode>composer require claytoncollie\u002Ftracking-code-for-google-tag-manager\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch3>Filters\u003C\u002Fh3>\n\u003Cp>If you want to set the container ID without using the wp-admin user interface, use the filter below.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>add_filter(\n    'tracking_code_for_google_tag_manager_id',\n    \u002F**\n     * Set Google Tag Manager container ID.\n     *\n     * @param string $container_id Container ID.\n     *\n     * @return string\n     *\u002F\n    function ( $container_id ) {\n        return 'GTM-7654321';\n    }\n);\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch3>Contributing\u003C\u002Fh3>\n\u003Cp>While the purpose of this plugin is to be very tightly scoped, issues and pull requests are welcome, but I do not guarantee that everything will be merged or support will be given.\u003C\u002Fp>\n\u003Cp>https:\u002F\u002Fgithub.com\u002Fclaytoncollie\u002Ftracking-code-for-google-tag-manager\u003C\u002Fp>\n","Simple, lightweight solution for inserting your Google Tag Manager Universal tracking code.",20,1362,"6.6.0","5.2","5.6",[66,67,68,20,69],"container","google","google-tag-manager","tracking-code","https:\u002F\u002Fgithub.com\u002Fclaytoncollie\u002Ftracking-code-for-google-tag-manager","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ftracking-code-for-google-tag-manager.1.0.0.zip",{"slug":73,"name":74,"version":55,"author":75,"author_profile":76,"description":77,"short_description":78,"active_installs":60,"downloaded":79,"rating":25,"num_ratings":30,"last_updated":80,"tested_up_to":81,"requires_at_least":82,"requires_php":13,"tags":83,"homepage":88,"download_link":89,"security_score":90,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":51},"ultimate-conversion-tracking-code","Ultimate Conversion Tracking Code","asanabria11","https:\u002F\u002Fprofiles.wordpress.org\u002Fasanabria11\u002F","\u003Cp>\u003Cstrong>Add Adwords, Facebook pixel or any Conversion Tracking scripts using variables like product ID, post id, title or custom ones.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>This plugin lets you insert any marketing script anywhere you want, before the head element closes, after the body or even before the body tag closes.\u003C\u002Fp>\n\u003Cp>Also you can use custom variables to share between scripts like conversion id or Facebook pixel id. as well as dynamic ones like product id.\u003C\u002Fp>\n\u003Cp>Also you can set your scripts to show in specific pages or events like right when somebody completes an order or when they are in a product page in case you are using Woocomerce.\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>\u003Cstrong>Premium version\u003C\u002Fstrong>\u003Cbr \u002F>\n  With the premium version you have no limits in variables or scripts and you get much more options, you can check out here if you want more power to your marketing scripts:\u003Cbr \u002F>\n  \u003Ca href=\"http:\u002F\u002Fwww.ultimateconversiontrackingcode.com\u002F\" rel=\"nofollow ugc\">http:\u002F\u002Fwww.ultimateconversiontrackingcode.com\u002F\u003C\u002Fa>\u003C\u002Fp>\n\u003C\u002Fblockquote>\n","Add Adwords, Facebook pixel or any Conversion Tracking scripts using variables like product ID, post id, title or custom ones.",2744,"2015-11-16T17:47:00.000Z","4.3.34","3.0",[84,85,86,22,87],"adwords","adwords-scripts","conversion","woocomerce","http:\u002F\u002Fwww.ultimateconversiontrackingcode.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fultimate-conversion-tracking-code.zip",85,{"slug":92,"name":93,"version":55,"author":94,"author_profile":95,"description":96,"short_description":97,"active_installs":98,"downloaded":99,"rating":25,"num_ratings":30,"last_updated":100,"tested_up_to":101,"requires_at_least":102,"requires_php":13,"tags":103,"homepage":107,"download_link":108,"security_score":90,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":51},"cc-sentry","CC-Sentry","Clearcode","https:\u002F\u002Fprofiles.wordpress.org\u002Fclearcodehq\u002F","\u003Cp>This plugin can report PHP errors to \u003Ca href=\"https:\u002F\u002Fsentry.io\u002F\" rel=\"nofollow ugc\">Sentry\u003C\u002Fa>. You need only set Sentry DSN and select Error Levels in plugin settings.\u003C\u002Fp>\n","This plugin integrates your WordPress site with Sentry error logging system.",10,2477,"2017-09-26T12:42:00.000Z","4.8.28","4.8.2",[18,104,105,106,22],"diagnostics","errors","sentry","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fcc-sentry","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcc-sentry.zip",{"slug":110,"name":111,"version":55,"author":112,"author_profile":113,"description":114,"short_description":115,"active_installs":98,"downloaded":116,"rating":11,"num_ratings":11,"last_updated":117,"tested_up_to":118,"requires_at_least":119,"requires_php":120,"tags":121,"homepage":13,"download_link":123,"security_score":90,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":51},"error-tracker","Error Tracker","tsquare17","https:\u002F\u002Fprofiles.wordpress.org\u002Ftsquare17\u002F","\u003Ch3>Don’t wait for users to tell you about errors.\u003C\u002Fh3>\n\u003Cp>This plugin allows you to track errors in PHP and JavaScript using Sentry, or track JavaScript errors and view sessions with LogRocket. This plugin only handles the integration of these services. You must sign up with Sentry or LogRocket and enter the appropriate information in the settings page in order to begin tracking errors.\u003C\u002Fp>\n\u003Ch4>This plugin makes use of 3rd party services.\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Once configured, this plugin will allow data to be collected by these services for the purposes of error tracking and debugging.\u003C\u002Fli>\n\u003Cli>You may need to update your privacy policy for regulatory compliance.\u003C\u002Fli>\n\u003Cli>View Sentry’s privacy policy at \u003Ca href=\"https:\u002F\u002Fsentry.io\u002Fprivacy\u002F\" rel=\"nofollow ugc\">https:\u002F\u002Fsentry.io\u002Fprivacy\u002F\u003C\u002Fa>, and terms of service at \u003Ca href=\"https:\u002F\u002Fsentry.io\u002Fterms\u002F\" rel=\"nofollow ugc\">https:\u002F\u002Fsentry.io\u002Fterms\u002F\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>View LogRocket’s privacy policy at \u003Ca href=\"https:\u002F\u002Flogrocket.com\u002Fprivacy\u002F\" rel=\"nofollow ugc\">https:\u002F\u002Flogrocket.com\u002Fprivacy\u002F\u003C\u002Fa>, and terms and conditions at \u003Ca href=\"https:\u002F\u002Flogrocket.com\u002Fterms-and-conditions\u002F\" rel=\"nofollow ugc\">https:\u002F\u002Flogrocket.com\u002Fterms-and-conditions\u002F\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n","Error Tracker is a super lightweight plugin that allows you to easily integrate LogRocket and\u002For Sentry error tracking software into WordPress.",1328,"2019-05-25T14:23:00.000Z","5.2.24","3.0.1","5.4",[18,105,122,106,22],"logrocket","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ferror-tracker.zip",{"attackSurface":125,"codeSignals":151,"taintFlows":160,"riskAssessment":195,"analyzedAt":200},{"hooks":126,"ajaxHandlers":141,"restRoutes":148,"shortcodes":149,"cronEvents":150,"entryPointCount":30,"unprotectedCount":11},[127,133,136],{"type":128,"name":129,"callback":130,"file":131,"line":132},"action","admin_menu","register_admin_page","includes\\class-ts-plugin.php",9,{"type":128,"name":134,"callback":135,"file":131,"line":98},"admin_enqueue_scripts","enqueue_admin_assets",{"type":128,"name":137,"callback":138,"file":139,"line":140},"plugins_loaded","tagsc_bootstrap_plugin","tag-scout.php",40,[142],{"action":143,"nopriv":144,"callback":145,"hasNonce":146,"hasCapCheck":144,"file":131,"line":147},"tagsc_scan_url",false,"handle_scan_request",true,11,[],[],[],{"dangerousFunctions":152,"sqlUsage":153,"outputEscaping":156,"fileOperations":30,"externalRequests":30,"nonceChecks":30,"capabilityChecks":30,"bundledLibraries":159},[],{"prepared":154,"raw":11,"locations":155},14,[],{"escaped":157,"rawEcho":11,"locations":158},2,[],[],[161,185],{"entryPoint":162,"graph":163,"unsanitizedCount":30,"severity":184},"handle_scan_request (includes\\class-ts-plugin.php:66)",{"nodes":164,"edges":181},[165,170,174],{"id":166,"type":167,"label":168,"file":131,"line":169},"n0","source","$_POST",80,{"id":171,"type":172,"label":173,"file":131,"line":169},"n1","transform","→ fetch_html()",{"id":175,"type":176,"label":177,"file":178,"line":179,"wp_function":180},"n2","sink","wp_remote_get() [SSRF]","includes\\class-ts-scanner.php",21,"wp_remote_get",[182,183],{"from":166,"to":171,"sanitized":144},{"from":171,"to":175,"sanitized":144},"medium",{"entryPoint":186,"graph":187,"unsanitizedCount":30,"severity":184},"\u003Cclass-ts-plugin> (includes\\class-ts-plugin.php:0)",{"nodes":188,"edges":192},[189,190,191],{"id":166,"type":167,"label":168,"file":131,"line":169},{"id":171,"type":172,"label":173,"file":131,"line":169},{"id":175,"type":176,"label":177,"file":178,"line":179,"wp_function":180},[193,194],{"from":166,"to":171,"sanitized":144},{"from":171,"to":175,"sanitized":144},{"summary":196,"deductions":197},"The Tag Scout plugin v1.0.1 demonstrates a generally good security posture with several key strengths.  The static analysis reveals that all identified entry points, including the single AJAX handler, have appropriate authentication checks.  Crucially, all SQL queries are executed using prepared statements, mitigating the risk of SQL injection.  Output escaping is also consistently applied, and a nonce check and capability check are present, further bolstering security.  The vulnerability history is clean, with no recorded CVEs, which suggests a strong track record of security awareness and maintenance by the developers.\n\nHowever, a notable concern arises from the taint analysis. Two flows were analyzed, and both were found to have unsanitized paths. While no critical or high severity issues were identified in these flows, the presence of unsanitized paths is a potential vector for vulnerabilities, especially if they interact with user-supplied input. The plugin also performs one file operation and one external HTTP request, which, while not inherently insecure, represent areas that require careful scrutiny to ensure they are implemented securely and do not expose the system to risks such as arbitrary file access or insecure external communication. \n\nIn conclusion, Tag Scout v1.0.1 is built on a foundation of good security practices, particularly regarding database interactions and output handling. The absence of historical vulnerabilities is a positive indicator. Nevertheless, the presence of unsanitized paths in taint flows warrants attention and potential remediation to proactively address any latent risks.",[198],{"reason":199,"points":98},"Unsanitized paths in taint analysis","2026-03-17T05:44:33.662Z",{"wat":202,"direct":211},{"assetPaths":203,"generatorPatterns":206,"scriptPaths":207,"versionParams":208},[204,205],"\u002Fwp-content\u002Fplugins\u002Ftag-scout\u002Fassets\u002Fcss\u002Fadmin.css","\u002Fwp-content\u002Fplugins\u002Ftag-scout\u002Fassets\u002Fjs\u002Fadmin.js",[],[205],[209,210],"tag-scout\u002Fassets\u002Fcss\u002Fadmin.css?ver=","tag-scout\u002Fassets\u002Fjs\u002Fadmin.js?ver=",{"cssClasses":212,"htmlComments":213,"htmlAttributes":214,"restEndpoints":215,"jsGlobals":217,"shortcodeOutput":219},[],[],[],[216],"\u002Fwp-json\u002Ftagsc_scan_url",[218],"window.TagScout",[]]