The Workflow Library

Library / Marketing ops / marketing-ops-040

Paid social (Facebook/LinkedIn/Google) campaign membership auto-tagging

Marketing opsContactMarketing Hub ProfessionalSimple~20 min to buildFull spec

Outcome. A contact who converts through a paid social or paid search ad gets tagged with which platform drove them, automatically, without a person cross-checking the ad platform's own reporting.

Workflow map Enrollment, branches and actions at a glance marketing-ops-040
flowchart TD
    A[Ad source property changes] --> B{Facebook?}
    B -->|Yes| C[Set paid_social_platform = Facebook]
    B -->|No| D{LinkedIn?}
    D -->|Yes| E[Set paid_social_platform = LinkedIn]
    D -->|No| F{Google paid?}
    F -->|Yes| G[Set paid_social_platform = Google]
    F -->|No| H{Other paid channel?}
    H -->|Yes| I[Set paid_social_platform = Other paid]
    H -->|No| J[No action]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse on any portal running paid ads through the native Facebook, LinkedIn, or Google Ads integrations, or through UTM tagging for a platform without a native integration, where sales or marketing wants a quick, visible tag on the record.
  • UseUse as a lightweight companion to full attribution reporting, not a replacement for it.
  • SkipDo not use if your ad platform integration already writes a fully equivalent property natively. Check your existing ad-source properties before building a second one.
The preview ends here. Six sections are in the library. counted, not blurred
PrerequisitesEvery property with its label, internal name, type and options, plus the assets the workflow needs before you start.2 items
EnrollmentThe trigger, the criteria exactly as they are ticked in the UI, the re-enrollment rule and the suppression list.4 parts
StepsEach action in order with its parameters, its branches and its delays, written as you tick them.6 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.4 pitfalls
Test plan, variants and build specHow to prove it works in a test portal, where to look when it does not, the variants for other objects or tiers, and the YAML build spec.3 variants, 3 sections
FilesThe properties JSON creates the fields in one API call, the workflow JSON documents the build.PDF, Markdown, JSON
Install1 click. The installer creates the properties this spec declares and the workflow itself, switched off, then opens a task for the prerequisites that are assets rather than properties, such as a team, a static list or a marketing email. What it created is listed on the install page.1 click, switched off
Unlock the full library, 149 EUR

or the marketing ops pack, 39 EUR

One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.