Hi @Vijayalakshmi_S, Sorry if this is not enough detail. The fields from the content fragment that is referenced in the page property will be used to render a sponsorship logo on the page and render various metatags in the page source for analytics and advertising purposes. We don't want to have to require an editor to drag on a content fragment component for every article beneath a certain area of the site - we want the articles to inherit the parents configuration. Does this make sense? I'm no...

more detail added, thanks for looking

Some more detail as requested...I think this diagram shows what we are trying to do: The fields inside the Sponsorship area are page properties of that page. A page can either define their own properties - and link to a content fragment - or when the page is built by the publisher it will look up the tree to find an ancestor page that has a value for the content fragment.