Skip to main content

Declare conversion names for Legacy code-based conversions

Follow the steps in this article to correctly declare conversion names for your Legacy code-based conversions so they can be used for campaign measurement and optimization.

As of August 31, 2026, conversion events without a name can no longer be used for optimization or retargeting in new Performance campaigns in TAM.

If your advertiser's pixel has Legacy code-based conversion events that are receiving signals in Events Manager, but you cannot find these events when configuring line item optimization or website retargeting, follow the steps below to declare their conversion names in Events Manager.

Before you start

Before declaring conversion names in Events Manager, check that none of the existing Legacy event types associated with your pixel contain an unusually high number of name variations.

Note: A maximum of 100 conversion names can be declared across all event types associated with a pixel ID.

A large number of name variations typically indicates that the conversion implementation is using dynamic metadata values. These implementations must be corrected before you can proceed with declaring conversion names.

Steps to declare a name for a Legacy code-based event

  1. Open the pixel's activity page in Events Manager.

  2. From the View pixel activity page, locate the code-based conversion that does not currently have a name.

    Conversions without a declared name will display an Undeclared status.

  3. In the Action column, click + Declare for the relevant event.

    Only declare conversions that meet the following criteria:

    • The event displays a generic event type name, such as Search, ViewContent, or AddToCart. These generic event names are case-sensitive and contain no spaces.

    • The event has a descriptive name, such as Complete Purchase, based on the name used in the conversion implementation. Refer to Collect conversion event metadata for more information.

  4. The Name field on the next screen should be automatically populated with the conversion name associated with the event being declared, for example ViewContent, Purchase, or Thank you page.

  5. Click Save to confirm the conversion name.

    The event status should immediately change from Undeclared to Active.

Did this answer your question?