Welcome to the Adobe Advertising Community! Connect with peers to ask questions, share best practices, explore release updates, and contribute ideas that shape the future of Adobe Advertising.
Recently active
How can a portfolio have higher revenue model coverage than cost model coverage?
My group is interested in showing ads only on finance websites. Is there a specific RTB source that I should be choosing to show up on finance sites?
I have search campaigns on Google, Microsoft and Baidu. Can I put all those campaigns in one Portfolio?
I have mainly Search cmapaigns and a few Content campigns. Can I have all of them in one Portfolio? Or should I create seperate Portfolios for Search and Content?
Do simulations reflect revenue by click date or by transaction date?
I am currently in the process of setting up a Search Portfolio. I have two main objectives (leads and revenue) and all the campaigns lead to both those objectives. Should all those campaigns be in 1 Portfolio? Or should I restructure my campaigns so there is 1 clear objective for the campaigns? At the most basic level, I am asking if its better to have more campaigns in a Portfolio or less? Also, is it recommended that I have only 1 metric in the Objective?
Currently this requires a consultant to enable the semgent in AdLens. Sould be automatic once the destination is set on the AAM side.
The reverse feed that gets fed into SiteCatalyst includes specific information from SearchCenter/AMO. Currently, Ad Destination URL is being sent over but Keyword Destination URL is not.If your not setting the destination URL's at the Keyword level, your not following best practices. As a use case, this information (keyword/destination url) is commonly shared between the paid search team and the merchandising team, which are those that build landing pages. The merchandisers need insight into what landing pages are associated to paid keywords. Currently they can't get this data out of SiteCatalyst. A simple fix would be to add keyword destination URL to the reverse feed. A great enhancement for ALL AMO users.
It would be great if there was an easier way to delete dependencies on a given segment, trait or model. It's tedious tracing each item and deleting.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
