Salesforce Marketing Cloud Engagement Developer

AMPscript is the language of personalization in an email. You write blocks, declare variables, branch with conditions and use string, date and formatting functions so one template can speak to many people.

• Inline and block syntax
• Variables and data types
• Conditions with IF and IIF
• String, date and number functions
• Looking up a single value
• Reading errors in a preview

You build A template that greets, formats dates and branches by subscriber attributes.

Real personalization pulls from tables. You read and write data extension rows from a send, loop over several rows, bring in content blocks and write defensive code so one bad row never stops a send.

• Lookup and LookupRows
• Looping over a rowset
• Inserting and updating rows during a send
• Pulling in content blocks by key
• Guarding against empty and missing data
• Troubleshooting with test sends

You build An email that lists a subscriber’s recent orders from a data extension.

When logic outgrows AMPscript, server-side JavaScript takes over. You write SSJS in script activities and pages, use the platform’s libraries to work with data extensions, and handle errors and logging so automations fail loudly.

• SSJS syntax and the Platform object
• Loading the core library
• Working with data extensions in SSJS
• Using WSProxy for SOAP objects
• Try, catch and logging
• SSJS compared with AMPscript for a task

You build A script activity that cleans a data extension and logs what it changed.

CloudPages let you build pages that read and write Marketing Cloud data. You create forms, process submissions with code, personalize a page by subscriber, and protect those pages from abuse.

• Landing pages and microsites
• Handling a form post in code
• Personalizing a page by subscriber
• Writing submissions to a data extension
• Securing pages and validating input

You build A preference page that reads and updates a subscriber’s choices.

Every integration starts with access. You create an installed package, request tokens with OAuth, scope what the integration may touch, and choose between REST and SOAP for each job.

• Installed packages and API integrations
• Requesting and refreshing an access token
• Scoping permissions for an integration
• REST and SOAP compared
• Endpoints, authentication URLs and subdomains
• Handling token errors

You build A small client that authenticates and makes a first successful call.

With access in hand, the APIs drive the platform from outside. You send one-to-one messages, fire journeys from events, and read and write data extension rows, choosing the call that suits volume and timing.

• Transactional messaging requests
• Triggered sends through SOAP
• Firing a journey with the event API
• Reading and writing data extension rows
• Synchronous and asynchronous calls
• Handling API failures and retries

You build A service that sends a transactional message and writes the result to a data extension.

Campaigns depend on clean, current data. You create data extensions with the right keys and retention, import and export files, and write SQL queries that shape audiences and join tracking data.

• Creating data extensions with keys and retention
• Sendable and non-sendable tables
• Imports and exports with file transfer
• SQL query activities and their limits
• Data views for sends, opens and clicks
• Scheduling data work in Automation Studio
• Overwrite, append and update

You build An automation that imports a file, runs a query and refreshes a sendable audience.

A good model makes every campaign easier. You design attribute groups and relationships in Contact Builder, choose keys that identify a person across sources, and decide where each kind of data should live.

• Contacts, keys and attribute groups
• One-to-one and one-to-many relationships
• Choosing a primary key
• Modeling orders and preferences
• Sendable relationships
• Testing a model with real queries

You build A data model diagram and a populated Contact Builder model for a retail scenario.

Marketing data is personal data. You apply roles and permissions, protect credentials and API access, encrypt sensitive fields and keep code from exposing subscribers’ details.

• Roles and permissions for developers
• Least privilege for API integrations
• Protecting credentials and tokens
• Encrypting sensitive fields
• Avoiding data exposure in pages and scripts

You build A security review of one integration, with each finding fixed.

Combine every skill in one build. You model the data, personalize the message with code, trigger it through an API and automate the data work behind it, then test and troubleshoot the whole chain.

• Scoping the campaign and its data
• Building the data model and imports
• Writing the personalization
• Triggering and monitoring through the API
• Testing and troubleshooting the chain

You build A triggered, personalized campaign with its data model, code and automations.