# Tag Setup FAQ This article addresses frequently asked questions during the tag setup process. ## Q1: Can SPA pages be tracked? **Answer: Yes, they can!** SPA stands for "Single Page Application." SPAs are increasingly used to optimize content delivery speed and improve overall website performance. Ptengine can observe page status using the basic tag. However, if the page content changes without a URL change, special configuration is required. The solution is to manually configure the tag so that the Ptengine tag fires when the page content changes, sending updated page URL information to Ptengine for accurate tracking. Please refer to the following page for specific setup instructions. ## Q2: Does it affect page load time? Ptengine's tag does not significantly affect page load time. Page load speed primarily depends on the user's network speed. Through our CDN and proprietary algorithms, the Ptengine tag loads within tens of milliseconds under normal network conditions, and within 500 milliseconds even when delivering Experience campaigns (neither of which has a significant impact on user experience). However, please note that to achieve these load speeds, the basic tag must be placed directly within the `` tag of the page HTML. (Even if it must be placed within the ``, it will not significantly affect page load time.) ## Q3: Can tags be installed on multiple sites? **Answer: Yes!** To track accurately with Ptengine, you need to register the site's main domain in your project and install the basic tag on the target pages. With the Growth plan, there is no limit to the number of main domains you can register. Please refer to the relevant article if you want to add more sites to track. ## Q4: Notes on GTM trigger configuration When using tag management tools such as Google Tag Manager (GTM), if the delivery scope of the Ptengine tag is restricted and the configuration excludes URLs containing Ptengine-specific parameters, some Ptengine features may not work correctly. For example, if you configure a GTM trigger with "Some Page Views" and "Page URL equals," URLs containing parameters will be excluded. Therefore, when using "Some Page Views," we recommend changing the matching rule from "equals" to "contains" or "starts with." Depending on the GTM trigger configuration, unintended behavior or missed tag firings may occur. For this reason, Ptengine generally recommends using the "All Pages" trigger setting. Please note that we do not provide support for individual trigger configurations, so please exercise caution when setting them up. ## Q5: Why is tracking not working correctly even though the tag is installed? Common causes: **1. The tag is not installed correctly** The most common cause is an error in tag installation — such as a typo in the code or using a tag from a different project — which prevents the Ptengine tag from working properly and stops data collection. If data is still not visible after some time following tag installation, use "How to verify the tag is correctly installed" to check whether the tag is properly placed on the target page. If there is an issue, try reinstalling the tag. **2. The Ptengine tracking tag is missing from some pages** The tag must be installed on all pages you want to track. If you have restricted the tracking scope, please verify that the target pages are included. ## Q6: When can I see data after installing the tag? **Answer: Access data for sites with the tag installed is typically available approximately 30 minutes after the visit!** If you have any questions, feel free to contact us anytime! ※ Please note that we do not provide support for individual code configurations. Please exercise caution when making your own settings. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://helps.ptengine.com/en/faq/tracking-code/tag-setting-faq.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.