CloudPages development
Landing pages, preference centres and forms built on Marketing Cloud CloudPages, with server-side logic and security reviewed before launch.
CloudPages is the web layer of Marketing Cloud Engagement. Salesforce describes it as making web content for your campaigns simple to deliver, and it builds and hosts landing pages, microsites and MobilePush pages. Because CloudPages can read and write your marketing data, a careless page can expose that data. Our CloudPages development service builds pages that work, write the right data and hold up to a security review.
For scripting across emails and messages, see AMPscript development. To write and check AMPscript yourself, try our AMPscript Studio.
What's included
| Area | What we build |
|---|---|
| Landing pages and microsites | Campaign pages, event sign-ups and microsites hosted in CloudPages |
| Preference centres | Subscription and channel preferences that update data extensions and, where needed, CRM |
| Forms | Smart Capture forms for simple capture, or coded forms for validation and multi-step flows |
| Journey entry | Forms that start journeys through the CloudPagesForm Submit Event entry source |
| Server-side logic | AMPscript for lookups and personalisation, and SSJS only where AMPscript lacks a function |
| Security review | HTTPS, input validation, and how subscriber identity passes between email and page |
| Fixes | Diagnosis of pages that break or misbehave after publishing |
How we work
- 01
Discovery
Agree the page's purpose, the data it reads and writes, and who will maintain it.
- 02
Design
Design the page flow, data extension structure, identity handling and error states.
- 03
Build
Build markup, AMPscript or SSJS and form handling, with comments maintainers can follow.
- 04
Test
Test with real and malformed input, expired links and missing data, on mobile and desktop.
- 05
Launch
Publish, check the live page and journey entry, and confirm data lands as designed.
- 06
Support
Fix issues, update content and review scripts when platform behaviour changes.
Security considerations
- Salesforce advises using HTTPS connections only for CloudPages.
- Never let a page identify a subscriber from a value that can be guessed or edited in the URL, such as a plain email address.
- Validate and clean every form input before writing it to a data extension.
- Keep SSJS minimal. It runs on the server with no DOM and no external libraries, and Salesforce recommends Core library functions only where AMPscript lacks one.
- Protect public forms from automated submissions, and limit who can publish pages.
Prerequisites and licences
You need a Marketing Cloud Engagement account with CloudPages available and user roles that allow page publishing. AMPscript runs in emails, CloudPages, SMS and MobilePush, and is processed at the point where it appears. If you're on Marketing Cloud Next, preferences work differently. Consent is stored in Data 360 and Salesforce provides Preference Pages, so see consent and preferences in Marketing Cloud Next.
Who it suits
- Teams that need a preference centre linked to their email programmes.
- Event and campaign teams that launch landing pages often.
- Anyone with old CloudPages built by someone who has since left.
Common mistakes
- Building a preference centre that updates Marketing Cloud but not CRM, so the two drift apart.
- Copying SSJS snippets without understanding what they write.
- No error handling, so a failed lookup shows a blank or broken page.
- Testing only with perfect data.
Related reading
Building a preference centre with CloudPages
A worked example in AMPscript
→Self-service preference centre
The solution blueprint
→Troubleshooting published landing pages
Common faults and fixes
→AMPscript vs SSJS
When to use each
→Questions we hear
Should we use Smart Capture or a coded form?
Can a CloudPages form start a journey?
AMPscript or SSJS?
Can you fix pages someone else built?
Sources
Brief us on your page
Describe what the page needs to do and what data it touches. We'll reply with an approach and any security questions.
