AJO - Latency in Offer Display | Community
Skip to main content
New Participant
October 19, 2023
Solved

AJO - Latency in Offer Display

  • October 19, 2023
  • 1 reply
  • 1649 views

There seems to be a latency of about 10-15 minutes for a offer to display - in my use case, I have capping set to 1. Once the offer with the highest priority is displayed, it is being capped at 1 as expected, but it takes about 10-15 minutes for the offer with the next priority to be displayed. Anyone else experiencing this issue? Tried with both Edge and Batch audience segments/AEP Web SDK is applied on the website.

#AJO

#Offers

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by rntrp

We have verified all the above items. We are pursuing the issue with Adobe Support. 

1 reply

akshaaga
Employee
October 20, 2023

@rntrp ,

 

The issue you're experiencing with a delay of 10-15 minutes for the next-priority offer to display may be due to various factors related to your specific setup and the tools you're using. Here are a few things you could check or consider:

1. *Cache and CDN*: Some delay could be related to caching mechanisms or Content Delivery Networks (CDNs) that are in place. Cached content might take some time to expire or be updated.

2. *Configuration*: Review your offer display configuration, including the rules and conditions set for your offers. Ensure that there are no unintended delays introduced by your settings.

3. *Network Latency*: Network latency can sometimes cause delays in delivering content. Ensure your network infrastructure is optimized for quick delivery.

4. *Audience Segments*: Ensure that your audience segments are correctly defined and updated in a timely manner.

5. *AEP Web SDK*: Verify that the Adobe Experience Platform Web SDK is properly integrated and configured. Any issues with this SDK could impact how offers are delivered.

 

rntrpAuthorAccepted solution
New Participant
October 31, 2023

We have verified all the above items. We are pursuing the issue with Adobe Support.