# November 17, 2025

## Marketing Intelligence

### Define Goals using Campaign Parameters

You can now define pageview goals based on the exact Ad Network and Campaign a visit comes from, rather than relying solely on UTM parameters.

<div data-full-width="true"><figure><img src="/files/DgrSPrbKJ47YK65bIEse" alt=""><figcaption></figcaption></figure></div>

## Account Intelligence

### Company Page Improvements

We’ve upgraded the Journeys experience to make it clearer, richer, and more actionable. You’ll now see more intuitive icons, helpful explanatory text, and—by popular demand—the full list of pages a company viewed, not just the first and last touchpoints.

<figure><img src="/files/T4H7PQXKIpdVEGAZ2zbW" alt=""><figcaption></figcaption></figure>

### Scoring Categories

You can now break your scoring logic into clear, weighted categories instead of relying on one large prompt. This gives you more control, more transparency, and ultimately much smarter scoring.

<figure><img src="/files/QyC1Bh4QG3g1IZFGuI1q" alt=""><figcaption></figcaption></figure>

## Platform

### Bing Auto-Tagging

Auto-tagging lets HockeyStack automatically identify the exact ad your visitors came from—without UTMs or any manual setup. Previously available for Google and LinkedIn ads, it now also supports Bing ads.

### Pull Leads Object from HubSpot

HubSpot’s newer **Leads** object is now fully supported and can be pulled into HockeyStack.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.hockeystack.com/release-notes/2025/november-17-2025.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
