Campaign Operations Specialist

This is an on-site position at Ground Floor Shop 1 Robinsons Cyber Sigma, Lawton Avenue, Taguig City.

IMPORTANT NOTE:

Copy and Paste the Link below in the browser to generate the application form:

How to Apply:

Copy and Paste the Link below in the browser to generate the application form:

Rate: $7/hr and earn up to PHP 69,000+/month

Schedule: Monday - Friday: 9:00 AM - 5:30 PM BST

Campaign Operations Specialist (On-Site Cyber Sigma, Taguig)

Mission: Execute high‑quality, on‑time marketing campaign builds in Adobe Marketo Engage via a ticket‑based workflow. Own day‑to‑day build, QA, and deployment for emails, webinars, nurtures, and list imports—continuously tweaking the inherited Jira intake/process to keep pace with CloudBees' needs while adhering to governance and compliance.

Must Have Qualifications:

• Experience: 1–3 years in Campaign/Campaign Operations or Marketing Ops with hands‑on Adobe Marketo Engage production.
• Marketo proficiency: Cloning/building programs; tokens/snippets; Smart Campaign logic; Engagement Programs; email/LP editing; basic dynamic content; program statuses.
• Ticketing: Working knowledge of Jira for intake, status updates, comments, and SLA awareness (inherit and tweak, not implement).
• List hygiene: Confident with CSV handling, dedupe checks, segmentation, and permission flags.
• QA & deliverability basics: Rendering checks, link/UTM validation, form testing, and awareness of unsubscribe/preference mechanics.
• Collaboration & organization: Clear written updates in tickets, dependable time management, attention to detail.

Good To Have Qualifications:

• Basic HTML for email tweaks
• Experience with webinar connectors (e.g., Goldcast) as configured by the team
• Familiarity with accessibility best practices.

Responsibilities

• Ticket execution (Jira): Triage assigned tickets, clarify requirements, set expectations, and update status notes; suggest small workflow tweaks as needs evolve (no new system build required).
• Marketo builds:

1. Emails & Landing Pages using governed templates, tokens, snippets, and - dynamic content.

2. Webinars/Events: Create Marketo programs, member statuses, confirmation/reminder emails; manage connectors as pre‑configured by the team.

3. Nurture/Engagement Programs: streams, transition rules, cadence/scheduling, and QA.

4. Smart Campaigns & Assets: Filters/flows, program status updates, alerts, and scheduling.

• List operations: Import & hygiene for CSVs (format validation, dedupe checks, segmentation, permission/compliance flags); manage static/smart lists.
• QA & compliance: Run pre‑flight checklist (rendering, links/UTMs, forms, PMPF, accessibility basics); honor opt‑out/preferences; follow regional send policies (e.g., EMEA).
• Governance adherence: Apply naming conventions, program foldering, and UTM taxonomy; maintain documentation and close tickets with clear notes and links to assets.
• Reporting cadence: Provide weekly counts, on‑time rates, and defect summaries; surface blockers early.

Success metrics

• SLA adherence: ≥ target on‑time % for all standard and complex ticket categories as defined by Campaign Ops.
• Quality: Launch error rate at or below target (based on defect log); minimal post‑launch fixes.
• Throughput: Consistent completion of assigned ticket volumes while maintaining quality and documentation standards.
• Process discipline: ≥ target % of requests processed via Jira with complete fields; checklists attached to tickets.

(Note: Specific numeric targets use our published Campaign Ops SLAs and quality thresholds.)

Immediate impact (30/60/90)

30 days

• Ramp on CloudBees' Marketo architecture, templates, naming, segmentation, and QA checklist.
• Inherit the Jira ticketing workflow; align on SLAs, definitions of "standard" vs. "complex" requests, and routing.
• Deliver first campaign builds (email + LP + form, simple webinar, basic list import) under supervision.
• Begin maintaining the defect log and run pre‑flight checks (rendering, links, UTMs, form behaviors).

60 days

• Handle the majority of standard tickets end‑to‑end (build → QA → schedule/launch) with minimal oversight.
• Propose incremental tweaks to Jira fields, checklists, and templates to reduce rework and improve clarity.
• Launch first nurture (Engagement Program) using existing frameworks; coordinate webinar program setup.
• Publish weekly SLA & quality snapshot (ticket volumes, on‑time %, defects resolved).

90 days

• Independently manage a full ticket load while meeting or exceeding published SLAs.
• Maintain low error rates through disciplined QA; proactively identify recurring issues and suggest fixes.
• Keep template library current (tokens/snippets), retire stale assets, and document best practices.
• Contribute to quarterly process improvements (updated intake forms, refined statuses, playbooks).

Job Type: Full-time

Pay: Php402.20 per hour

Expected hours: 40 per week

Work Location: In person