Working prototype · by Thanh Nguyen (Holmes)

From sign‑up to pipeline

How one person moves through a weather API company's marketing stack, and how I check a campaign before it goes out. Made for my application to the Marketing Automation and Technology Specialist role at Vaisala Xweather.

Fictional people, companies and numbers. Not connected to, or endorsed by, Vaisala or Xweather. The free tier (15,000 accesses a month) and the €300 subscription come from xweather.com's public pricing page, checked 21 November 2026.

Part 1

Lifecycle replay

Each step shows what is sent, what each tool does with it, and what could break. Use the arrows or the step list.

    Data sent Segment calls · tracking-plan names

    Customer.io

    Salesforce via the team's sync

    What could break, or why it matters

    Part 2

    Preflight checker

    The checks I would run before any send, built as a tool the whole team can use. It reads the campaign set-up and the tracking plan, then tests every message. It opens on a campaign with planted errors. Edit the HTML or the subject and run it again.

    Preview with example data
    ResultWhereCheck

    Needs a person, not this script: tone and claims, whether the segment matches the intent, send time, rendering in real inboxes, and sign-off from the campaign owner. Link status checks run in the command-line version only.

    Sending domain check

    Looks up SPF, DMARC and a DKIM selector over DNS-over-HTTPS (dns.google). Only the domain name is sent.

    Run a check to see results. praised.co is my own project's domain.

    Behind it

    The working files

    What this is not: it has not run in Xweather's systems, and how their tools connect is unknown to me. The replay shows one reasonable design. These are the first things I would ask: where lead scoring lives, how product usage reaches Customer.io, and which sync writes to Salesforce.