Meta CAPI content_name parameter

We’ve upgraded how AnyTrack populates Facebook Conversions API content_name so it carries real context by default. When your integration doesn’t provide content_name, we now use brand, then product, then offer—whichever is available.

What's New

• Removed the old default of “Product” and the ecom-only item name behavior.
• New fallback order: brand name → product name → offer name.
• If an integration (e.g., Unbounce) sends content_name, we pass it through unchanged.
• If you use the custom integration postback and you pass brand_name, we'll forward it to Meta CAPI in the content_name parameter.

Impact

• More reliable triggers for custom conversions and richer audience building.
• Cleaner event payloads reduce generic values that hurt optimization and ROAS.
• Backward compatible: no changes required unless you previously depended on the old default.

Get Started

• Review your Facebook destination mappings in the AnyTrack dashboard and confirm expected values in Events Manager.
• If you rely on content_name rules for custom conversions, validate the new values on recent events.
• Optionally override content_name at the integration level or via mapping rules if you need a custom convention.