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.
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]

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.
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.





