Adobe Analytics records the literal campaign placeholder

An analyst finds em_{dynamic_campaign_parameter} in Adobe Analytics Tracking Code. The email platform says it replaces the token at send time, and publishing teams say they use clean landing URLs. A direct/none referrer does not identify the sender. The concrete fact is that at least one hit carried the unresolved value after the Analytics implementation captured it.

Separate link creation from data capture

Adobe documents that the Campaign variable usually reads a URL query parameter, but the organization chooses the mapping. Confirm which cmp or other parameter populates marketing.trackingCode, data.__adobe.analytics.campaign, or s.campaign in this implementation. Check Data Collection rules and Processing Rules for fallback logic that could manufacture or preserve the token. Save an example hit with timestamp, landing URL, report suite, and campaign value. Avoid treating a report dimension alone as a complete request trace.

Reproduce the bad URL without guessing its source

Generate a test email through the same template and send path. Inspect the final HTML link before click, the redirect chain, and the landing URL after click. Repeat for each send variant, including a preview, test send, and production send. Search known link shorteners, copied campaign assets, and archived messages for the literal token. If the token exists in a landing URL, the web rule may be faithfully recording a bad input; if it does not, the variable mapping needs closer inspection.

Protect the metric while you investigate

Create a report or segment for literal brace tokens and quantify affected hits by date, page, and channel. Add validation to the email launch checklist that rejects unresolved placeholders before send. If a sanitization rule is considered, retain the raw URL in an accessible diagnostic log and document the change to attribution. Ask the owner to produce a trace from template through Analytics hit, rather than a statement that the platform “should replace” the token.

Adovo’s view

Attribution is a chain of custody for a URL. When a placeholder reaches a metric, the honest answer is to trace each handoff, not to guess which team broke it. The fix is complete when the launch process makes the bad link impossible to send again.