Franchise/location-based campaign attribution via custom object

Outcome. A franchise or multi-location brand can see which physical location's campaign actually drove a given contact, instead of every lead looking like it came from one shared brand campaign.

Workflow map Enrollment, branches and actions at a glance marketing-ops-038

flowchart TD
    A[latest_location_touch changes] --> B[Custom code: match Location record, confirm association]
    B --> C{result_code ok?}
    C -->|Yes| D[Set attributed_location]
    D --> E[Set location_campaign_source]
    C -->|No| F[Notify marketing ops of attribution failure]

When to use it, when not to

• UseUse on a portal that already models locations as a custom object, a common franchise or multi-location pattern, where each location runs its own local campaigns (local paid social, local landing pages, in-store QR codes).
• UseUse when corporate marketing needs to report ROI by location, not only by campaign name.
• SkipDo not use if all campaigns are run centrally with no location-specific variant. Marketing Hub Enterprise's native Campaigns tool and marketing-ops-027's deal rollup already answer overall campaign ROI without a custom object.
• SkipDo not build the Location custom object from scratch as part of this fiche if your portal doesn't already model locations that way. That is a larger data-model project, out of scope here.