Salesforce Marketing Automation Intern

Sign up for a free Developer Edition org, which includes Campaigns.

Design the campaign structure.

Define the marketing activities your business runs, such as events, email sends, referral drives, and digital advertising, and decide which belong together under a parent campaign.

Explain why a hierarchy matters when reporting on a multi-activity push.

Configure campaigns in your org.

Create a parent campaign with at least three child campaigns, each with its type, start and end dates, planned cost, and expected response.

Now define member status values per campaign type, since the stages of an event attendee differ from those of an email recipient.

Write what each status means and the evidence for setting it.

Add members.

Create at least forty leads and contacts and add them across your campaigns with varied statuses, including people in more than one campaign, because overlap is what makes attribution difficult and realistic.

Then build the basic reporting.

Create a report showing members by status per campaign and another showing campaign cost against responses, and compute cost per response.

Finally, write a note on what your structure cannot tell you, such as which touch mattered most for someone in three campaigns.

Submit the structure design, campaign configuration screenshots, member status definitions, the member data, both reports with cost per response, and the limitation note.

Marketing generates volume; scoring decides what sales touches first.

Design the scoring model.

Decide what makes a lead worth pursuing for your business, separating who they are from what they have done, and assign points to each factor with a written justification.

State the threshold at which a lead passes to sales and why that line, since an arbitrary threshold floods or starves the sales team.

Configure capture.

Set up Web-to-Lead, generate the form, and capture the fields your scoring needs.

Submit at least twelve leads with deliberately varied profiles so your scoring has range to work with.

Build the scoring.

Implement it with formula fields, Flow, or a combination, and record which you chose and why.

Make the score recalculate when a relevant field changes, then prove it by editing a lead and showing the score move.

Set up handoff.

Build automation routing leads above the threshold to a sales queue or owner and leaving the rest in nurture.

Prove both paths with test leads.

Now validate the model against outcomes.

Convert some leads and mark others dead, then report on score against outcome to see whether high scores actually converted.

Where they did not, adjust the model and record what you changed, because a scoring model never checked against outcomes is guesswork.

Submit the scoring model with justifications, capture configuration, the twelve leads, scoring implementation with recalculation evidence, routing evidence, and the validation with adjustments.

Leads not yet ready to buy need structured follow-up rather than being forgotten.

Design the nurture journey.

Map a sequence for leads below your scoring threshold: what happens on day one, what happens if they engage, what happens if they do not, and when they leave the sequence.

Define the exit conditions explicitly, because automation without exits is how people receive nurture emails after becoming customers.

Build it in Flow.

Create automation handling the sequence using record-triggered and scheduled flows together, with decision elements branching on engagement.

Use tasks, field updates, and status changes to represent each step, since Developer orgs limit outbound email volume.

Now test every path.

Create leads that engage, leads that do not, and leads that qualify mid-sequence.

Confirm each follows the intended route and, critically, that the qualifying lead exits nurture rather than continuing.

Screenshot each path.

Test the wrong path deliberately.

Construct the case where your automation would do something unwanted, such as nurturing a converted lead or an opted-out contact, and show what currently happens.

Then add the guard and prove it works.

Document it for whoever maintains it.

For each flow, record its purpose, trigger, entry and exit conditions, and what to check before modifying it.

Finally, write a note on respecting the recipient, covering how you would honour an opt-out and what frequency you consider excessive.

Submit the journey map with exit conditions, the flows, evidence for every path, the wrong-path case with its guard, maintenance documentation, and the recipient note.

Attribution is the question marketing is always asked and rarely answers well.

Build the revenue chain.

Convert a portion of your campaign members into opportunities and close some won and some lost, ensuring the campaign link is retained through conversion so the chain holds end to end.

Understand the models.

Research first touch, last touch, and multi touch attribution, and write what each would conclude about the same deal.

Identify which of your records has multiple campaign touches and state what each model would credit.

Configure what the platform offers.

Set up Campaign Influence, record which model your org applies by default, and build a report showing campaign influenced revenue.

Now compute return.

Build reporting bringing campaign cost together with the revenue attributed to it, and calculate return per campaign.

Rank your campaigns by return.

Then challenge your own numbers.

For your top campaign, examine whether it genuinely caused the revenue or merely touched deals that would have closed anyway.

State what evidence would settle it and what you cannot prove, since confident attribution from thin evidence is the most common marketing reporting failure.

Build the dashboard with at least four components for a marketing manager, and write one line per component.

Finally, write a 500 word summary for the business owner stating which activity to spend more on, which to stop, and how confident you are in each recommendation.

Submit the revenue chain evidence, the attribution model comparison, Campaign Influence configuration, the ROI report with rankings, your causation critique, the dashboard, and the owner summary.