If I understand correctly, number of targeted profile attribute and experiences mapped to them are too many, and that is why you are not comfortable driving these variations with dedicated audience. If you are not building dedicated audience, you can create single qualifying audience and put the variation logic in the modal code itself. Bunch of IF ELSE blocks.But this will turn out to be a nightmare for you from a manageability standpoint. Second Option is to externalize the Modal Functionality...

Can you provide some expected issues that we might run into.

@evolytics_brian Intent is to send data to two different set of reporting suites in two different org's. One currently in place, implemented via Launch is focused towards tracking experience on the web property only. There is another parent exp (lets called is Exp A), from which the user can navigate to this exp (lets called is Exp B). Exp A also uses AA (different ORG), and is implemented through Tealium. Intent is to follow the customer journey from Exp A to Exp B, in real time. This is where ...

You were right, value for Auth was not correct. Fixed it, and was able to connect. Thanks for your help !!

I did create a namespace and was able to download the config file. Updated the ".wskprops" as shown in the attached screenshot. But still, continue to get the same error

Katuk, you have mentioned google app engine, whereas question was about google cloud. I would be surprised if AEM cannot be hosted on AEM cloud as it wouldn't be any different from any other cloud service provider.Since google cloud is a relatively new player in the cloud business, it might not have been explored enough by Adobe to support it and that would be understandable.

Still no luck with get resource as well.String shortURL =resourceResolver.map("/content/myapp/en_us/home");Resource res = resourceResolver.getResource(shortURL);resource object is still null.

You can also mark the links as valid by using x-cq-linkchecker=“valid”property in your tag. In this case Link Checker will check the link but always mark as valid.If you also use x-cq-linkchecker=“skip”, Link checker will not check the link and mark as valid.After updating the code you would have to clear the linkchecker by deleting node /var/linkchecker from crx/de lite.