Using DY Campaigns as a CMS
An idea that was tossed around on our team is using a single landing page on our site and then using DY experiences to show different content/product based on URL parameters.
For example: user goes to page with a param "utm_campaign=product1" and we replace several content pieces on the site for this product and then if the user goes to the page with "utm_campaign=product2" we load content for that product.
Then this strategy would be used for possibly 4+ products, with 6 different content sections to replace per product.
Does anyone have experience running something like this? Further, what downsides are there to running a personalized landing page like this?
-
Hi Jordan,
- Personalizing a (landing) page based on URL parameters is a pretty standard experience to create using DY.
- With regards to downsides, the question is what alternatives do you have... from my experience, doing it with DY is relatively easy and will save expensive time.
- 4-6 products should be OK to maintain - not anticipating issues. But there might be ways to scale this using recommendation widget workaround (include all the information in the data feed, and set the context of the page to "PRODUCT" will allow you to pull the information on the fly using DY.feedProperties)
- The pros of using this method -> having all the traffic landing on the same page is better in terms os SEO as far as I'm aware and also have shorter tests (traffic is not divided across different landing pages allowing faster significance)
- One last thing, you will have a report for every product and how the campaign performs in the light of this product.
BTW - a possible easy implementation can use the Multi Touch feature - every experience is a product with different touch points (content sections. )
Good Luck
Please sign in to leave a comment.
Comments
1 comment