Does anyone know the best way to perform a profile lookup from web/app directly? There is a third-party (3P) tag on the website that needs to determine in real-time if a visitor is a known customer in AEP. If the customer is not known to AEP, only then does the 3P tag need to identify the visitor. Please note that the web SDK implementation is not yet available. UPS API is not an option here as these API calls will be directly made from client-side.
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Hi @monsxp ,
One option is to use the real-time customer profile API indirectly from the client side. You can achieve this by writing an Adobe IO action that interacts with the real-time customer profile API. The client side would call the Adobe IO endpoint, which in turn calls the profile API and retrieves the response.
In Adobe IO, you can parse the response and apply logic (such as checking if the profile has a CRM ID) to return a true or false value to the client.
This approach keeps the internal processing and API credentials hidden from the client. Additionally, you can cache the response in Adobe IO for a specified duration (from minutes to hours) to avoid repeated calls to the profile API.
This is just one example of a potential solution. You can also consider using other tools instead of Adobe IO.
Thanks,
Arpan
Very interesting Requirement -
May be we can mimic the logic implemented in Same-page personalization
@bitunsen-2022 pls advice
Views
Replies
Total Likes
Hi @monsxp ,
One option is to use the real-time customer profile API indirectly from the client side. You can achieve this by writing an Adobe IO action that interacts with the real-time customer profile API. The client side would call the Adobe IO endpoint, which in turn calls the profile API and retrieves the response.
In Adobe IO, you can parse the response and apply logic (such as checking if the profile has a CRM ID) to return a true or false value to the client.
This approach keeps the internal processing and API credentials hidden from the client. Additionally, you can cache the response in Adobe IO for a specified duration (from minutes to hours) to avoid repeated calls to the profile API.
This is just one example of a potential solution. You can also consider using other tools instead of Adobe IO.
Thanks,
Arpan
Thanks @arpan-garg
We are thinking to use Adobe I/O runtime, however peak traffic volume and live hits on experience platform API is what we need to factor in (either using Adobe Runtime or any other middle-ware) - using cache as you mentioned as well. However Adobe has clearly told us that there are no guardrails / performance metrics or guarantees against these API load performance. Therefore without these metrics it is difficult to design any middle layer.
Views
Likes
Replies
Views
Likes
Replies