This can be done by checking the source code of the website or by asking the website owners directly. To verify that the Adobe Analytics tag code is in production, it is important to make sure that the latest version of the tag code is present in the website source code. Reference: https://www.adobe.com/content/dam/acom/en/devnet/analytics/analytics-developer-professional-study-guide.pdf

This technique is used to send data over HTTP to a web server when the useBeacon variable is enabled. According to the Adobe Analytics Developer Professional study guide (page 8-9), the navigator.sendBeacon() method is a modern way of sending data to a web server in the background that is asynchronous and does not interfere with the user's experience. For more detailed information, please refer to the study guide

Create a tag property
In this lesson, you will create your first tag property.
A property is basically a container that you fill with extensions, rules, data elements, and libraries as you deploy tags to your site.
Prerequisites
In order to complete the next few lessons, you must have permission to Develop, Approve, Publish, Manage Extensions, and Manage Environments in tags. If you are unable to complete any of these steps because the user interface options are not available to you, reach out to your Experience Cloud Administrator to request access. For more information on tag user permissions, see the documentation.
NOTE
Adobe Experience Platform Launch is being integrated into Adobe Experience Platform as a suite of data collection technologies. Several terminology changes have rolled out in the interface which you should be aware of while using this content:
Platform Launch (Client Side) is now tags
Platform Launch Server Side is now event forwarding
Edge configurations are now datastreams
Learning Objectives
At the end of this lesson, you will be able to:
Log into the Data Collection user interface
Create a new tag property
Configure a tag property
Go to the Data Collection interface
To get to Data Collection
Log into the Adobe Experience Cloud


You should now see the Tags Properties screen (if no properties have ever been created in the account, this screen might be empty):

Create a Property
A property is basically a container that you fill with extensions, rules, data elements, and libraries as you deploy tags to your site. A property can be any grouping of one or more domains and subdomains. You can manage and track these assets similarly. For example, suppose that you have multiple websites based on one template, and you want to track the same assets on all of them. You can apply one property to multiple domains. For more information on creating properties, see "Companies and Properties" in the product documentation.
To Create a Property
Click the New Property button:

Name your property (e.g. Luma Tutorial or Luma Tutorial - Daniel)
As the domain, enter enablementadobe.com since this is the domain where the Luma demo site is hosted. Although the "Domain" field is required, the tag property will work on any domain where it's implemented. The main purpose of this field is to pre-populate menu options in the Rule builder.
Expand the Advanced Options section and check the box to Run rule components in sequence Click the Save button


Next "Add the Embed Code" >

A datalayer is an object that contains the data that needs to be communicated to digital analytics and reporting servers. It is typically a JavaScript object that contains key-value pairs that represent the different data points that need to be sent to the reporting server. For more information, please refer to the Adobe Analytics Developer Professional study guide.

According to the Adobe Analytics Developer Professional study guide, query string parameters are used in the Adobe Experience Platform to identify search terms on a retail website. Query string parameters are the portion of a URL that follows the question mark (?) and contains key-value pairs that provide additional information about the request. For example, a URL containing a query string parameter might look like this: www.example.com/search?term=shoes. In this example, the query string parameter is "term=shoes", which indicates that the search term being used is "shoes".