Last updated on MARCH 06, 2017
Applies to:Oracle Commerce Guided Search / Oracle Commerce Experience Manager - Version 11.0 and later
Information in this document applies to any platform.
Is there a way to find out what location triggers (search terms, dimension value refinements, user segments, etc.) triggered the current content item or rule returned in the Assembler using the Assembler API?
We would like to send only those content items/triggers that caused the page to fire back to the front end, so that we can eliminate those request parameters that did not contribute to the triggering from our caching strategy.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms