@Shailiza In first scenario. it would be considered as returning visitor and in the second scenario as the user has cleared the cookie, it would be considered as new user.        

Hi @Shailiza    Kindly refer to this experience league post.   https://experienceleaguecommunities.adobe.com/t5/adobe-target-questions/new-vs-returning-visitor/m-p/242076#:~:text=If%20the%20user%20is%20inactive,those%2030%20minutes%20of%20inactivity. 

@Ronnie09 This can be handle in two steps.   First, you would need to assign your local host a domain name  https://ecompile.io/blog/localhost-custom-domain-name    Second, add a redirect rule in the dispatcher   RewriteRule "^/learn$" "https://%{SERVER_NAME}/content/sample-project/us/en.html" [R,L]...

Hi @Ameen_Dev ,    It's a kind of weird issue. Let's try something different.   Can we create a new page and copy the entire content which exists on the page which has the vanity URL issue. Once it's done, check whether the new page is having the same vanity URL issue. If it's working, delete the ol...

@ChaoXiong Would you please provide more details like   1. Is this issue happening on your local instance instance or on any specific environment? 2. Try installing the latest 6.5 service pack and  WCM core component packages on your instance and check if the issue still persists. 3. Have you done a...

Hi @vignesh_bhat    Have you done the following steps mentioned in the document? Also what's the product profiles are you using?   Open the Adobe Admin Console: https://adminconsole.adobe.com Navigate to Products (top toolbar), then select Adobe Target - <your-tenant-id> (from the left panel). Se...

@ChaoXiong Would you please check error.log and let us know what's the error trace you are getting after hitting the form submit CTA.

Hi @sheejo    Yes, it's possible to query to AEP using API calls. Refer to the following documentation that will guide you in using the query service.   https://developer.adobe.com/experience-platform-apis/references/query-service/  https://experienceleague.adobe.com/docs/experience-platform/query/a...

@Ameen_Dev It means the issue is with the publisher not dispatcher. If you have system console access on publisher, go to the configuration and search for Apache Sling Resource Resolver. Simply edit and save the configuration. Try and let me know the result.

@Ameen_Dev Have you tested hitting the vanity URL directly on publisher? Is the vanity redirect still happening on Publisher?