There are two ways to serve up a landing page:
Server side for me mostly, but depends on the LP type, so I'm using both approaches at times.
Not being a techie, I'm not really understanding the difference.
I store my landers on a dedi server, and use a CDN to pull from the dedi to cache on the CDN which is what is served to visitors.
So am I using both your options?
BTW it's nice to see a post from you @jennatalia - it's been a while!
Amy
Hosting is probably the wrong term.
Rendering might be a better way to describe it.
The biggest difference between the two methods is
1) Server side rendering can change the webpage before it's downloaded by the end user. This is useful for personalization of content based on some profile of the user. Using PHP, you could readily manipulate the webpage based on attributes you can detect about the user using their request.
2) Client side rendering downloads a template and makes additional requests to "build" the webpage using the user's browser.
Most tech companies are adopting option 2, and the part I don't fully understand is why the normally cutting edge affiliate marketing world isn't--or at least doesn't visibly show it.
Sent from my S3_Pro using Tapatalk
Depends from your tech setup and requirements.
For example if your setup requires a cloaker on the server side, there is a reason to use VPS over CDN.
Otherwise I'm a big fan of CDN's with their global coverage.
For landers, EU and US dedicated servers with geo load balanced DNS to route users to the closest instance.
Mainly running like this because we rotate landing pages using no redirect style tracking
- CDN infrastructure isnt always as great as their marketing makes out, a lot dont even use SSD drives...
- We tested and a surprising amount of people have ancient, shit phones that Option 1 e.g. ReactJS doesnt play well with. Old iPads were a nightmare.
- We dynamically serve resized images in a format (WebP etc) suitable for the device from a CDN
- Scripts CSS, JS etc served from CDN