Last verified: September 11, 2026
What You Can Now Do
Context Memo page events now carry campaign origin, a targeting snapshot, and ad identity alongside the standard interaction data. Before this, an event on a landing page told you that someone scrolled, clicked, or converted, but not which ad put them there or who the advertiser thought they were talking to. You will now see each event annotated with the platform, campaign, ad group or ad set, and creative reference as they existed at click time, the audience definition the click was served against (interest or lookalike segment, geography, device class, placement), and the platform-native ad ID and variant. The task this changes: you no longer reconstruct attribution from a UTM string weeks after the fact. Campaigns get renamed, ad sets get duplicated, creatives get swapped mid-flight, and utm_content=v3 eventually points to an asset that no longer exists. The context is persisted at event time instead.
Where It Is in Context Memo
The new fields live in the AI traffic attribution area, on the page event stream for any memo or landing page you have instrumented. Open an individual event and the campaign origin, targeting snapshot, and ad identity appear as their own grouped fields under the interaction data you already had. Filters and grouping on the event list read from the same fields, so audience segment, device class, and placement are available as breakdowns rather than something you parse out of a query string.
How to Use It
- Open the page event stream for one paid landing page and inspect a recent event. Confirm the campaign origin and ad identity fields are populated. If they are empty, the click predates the release or arrived from a destination URL without recognized platform parameters.
- Group the event list by audience segment and compare scroll depth against form fills. This surfaces the segments that read to 75% and leave, which is a content problem, versus segments that bounce early, which is a targeting problem.
- Filter to a single creative reference and split by device class and placement. You will see whether one asset performs differently on mobile placements than in desktop feeds, with the same creative held constant.
- Filter to your retargeting audiences and compare conversion events against cold prospecting audiences on the same page. This tells you whether the page is converting intent you already built or genuinely persuading new prospects.
- Use the platform-native ad ID, not the campaign name, when you export events for a join against your ad platform reporting. The ID survives renames; the name does not.
- Change one element of the page for the segment that underperforms, publish, then re-run the same grouped view after the next flight. Because ad identity sits in the event stream, the content change is testable against a defined audience instead of against blended traffic.
Why We Built It
The complaint we heard repeatedly: "The ad platform says the campaign converted. Our page analytics say people scrolled. Nobody can tell me which audience the page is actually working for." Ad platforms report conversions inside their own reporting, page analytics report behavior, and the only join between them was a UTM string that decayed the moment someone duplicated an ad set. The cost was real work thrown away, teams rewriting landing page copy on instinct because the data could not say which segment was failing, and creative decisions defended with numbers that pointed at assets nobody could find six weeks later.
What It Does Not Do Yet
- Events recorded before this release do not carry the new fields, and we cannot backfill them. Historical comparisons start from your first event after the update.
- Spend and cost data stay in your ad platform. Context Memo attaches origin, targeting, and ad identity to behavior, so cost-per-outcome math still happens wherever your spend lives.
- Fields populate only when the destination URL carries parameters we recognize from the platform. Hand-built links without them will still record the interaction, minus the ad context.
- This is event-level attribution inside Context Memo, not a replacement for your CRM or CMS reporting. Those systems remain more capable for pipeline stages and content management, and the HubSpot integration is the path for pushing this context toward revenue records.
