Note that this information only applies to advertisers using code-based conversion events that use dynamic values for the name metadata.
What is the conversion name value?
The conversion name is a metadata value that is executed as part of the script that runs when a code-based conversion is triggered on an advertising website.
Every code-based conversion event reported by the Teads Pixel or Conversions API, must include a conversion type that matches one of the 9 accepted standard event types, and also a name that identifies the specific conversion separately from others in the same type/category. For more information on metadata implementation, see our dedicated article.
What is the potential issue with using dynamic values as name metadata?
Due to platform updates being introduced in H2 2026, Teads now requires a name for every conversion event. This name now acts as a critical identifier in TAM and directly impacts campaign optimization.
In addition, these changes also require advertisers that have been using the name metadata field in their code-based conversons, to include dynamic values like order IDs or product names in large catalogs, to update their implementation to use a newly introduced product_name metada field in the script.
How to check if an advertiser is affected?
Checking the TAM Events Manager is the easiest method to identify if an advertiser needs to make changes to their conversion events implementation ahead of a campaign launch:
Locate your advertiser's pixel en TAM Events Manager
Open the Pixel & Conversion activity report.
Review the conversion events that have been configured. If any of the events types show hundreds or thousands of names associated (as shown by the Purchase conversion with 37660 names in the screenshot below), the advertiser will need to update their code-based conversion implementation.
How to correct the issue?
Reminder: Only advertisers using code-based events with dynamic name metadata values are impacted.
Follow the steps that match your implementation method.
Using Google Tag Manager:
Update the Teads Advertiser Pixel template in Google Tag Manager to the latest version, and follow these steps:
Open the affected conversion tag
Extend the Advanced conversion tracking options
Move the dynamic metadata value from the "Conversion name" field, to the newly available "Product Name" field
Update the Conversion name field to a generic descriptor name for the conversion event (examples below)
Save the changes to the tag, and click publish from the main GTM interface to ensure the changes are implemented on the website.
Example:
Using a hardcoded conversion script:
Update the conversion tag script implemented on the website with the new metadata for the dynamic variable by following these steps:
Locate the name: field in the script, and update it from using a dynamic data layer value, to a generic conversion descriptor name, e.g. "Thank you page"
Relocate the dynamic data layer value to the new product_name: field in the code.
Example: Update the code script from this
<script>
window.teads_e.push({
name: "<DYNAMIC VALUE THE ADVERTISER IS USING>",
// price: value, // Optional, float (e.g., 39.90)
// currency: "value", // Optional, string ISO 4217 currency code (e.g., "USD")
conversionType: "Purchase"
});
</script>
to this:
<script>
window.teads_e.push({
name: "Thank you page",
product_name: "<DYNAMIC VALUE THE ADVERTISER IS USING>",
// price: value, // Optional, float (e.g., 39.90)
// currency: "value", // Optional, string ISO 4217 currency code (e.g., "USD")
conversionType: "Purchase"
});
</script>
Notice the code contains product_name, which is now being used to store the dynamic value that changes with each conversion (for example the product name or order id), and the value under the name: metadata is now used for the more generic conversion descriptor "Thank you page".
The price and currency metadata fields are still available for use when needed.