> For the complete documentation index, see [llms.txt](https://docs.relevant-digital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.relevant-digital.com/technical/integration/javascript-api/relevantdigital.auction.registerimpressionbyadid.md).

# relevantDigital.Auction.registerImpressionByAdId()

Manually register instream video impressions for header-bid analytics using an ad ID.

Use `relevantDigital.Auction.registerImpressionByAdId()` to record an impression manually.

Use it when the Relevant Yield JavaScript cannot detect the impression automatically.

This commonly applies to instream video integrations using the **Google IMA SDK**.

{% hint style="info" %}
Use this method only when automatic impression detection is unavailable.
{% endhint %}

### Parameters

#### `id`

The creative ad ID. For instream video, use the ID from the VAST `<Ad>` element.

### Return value

Returns `true` when a matching bid response is found.

An impression must not have been registered for that response previously.

### Related guide

For the general setup, see [Instream video with HBM and GAM](https://docs.relevant-digital.com/technical/integration/formats-and-channels/instream-video-with-hbm-and-gam.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.relevant-digital.com/technical/integration/javascript-api/relevantdigital.auction.registerimpressionbyadid.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
