Query parameters lost during CDN or dispatcher redirects Adobe Experience Manager
In Adobe Experience Manager as a Cloud Service, query parameters such as utm, gclid, and fbclid get removed during redirects. This behavior affects redirect logic and tracking when CDN strips parameters or redirects ignore the query string. To fix this issue, update CDN configuration and use correct redirect rules.
Description description
Environment
Adobe Experience Manager as a Cloud Service
Adobe Experience Manager Asset
Issue/Symptoms
- UTM parameters such as utm_source, utm_campaign, or gclid disappear after a redirect.
- Dispatcher redirect rules depending on %{QUERY_STRING} do not execute.
- CDN-level redirects drop all query parameters when using
reqProperty: path. - Redirects work locally or in AMS but fail in Cloud environments.
Resolution resolution
To fix this issue, follow these steps:
-
Identify whether query parameters are missing before reaching the Dispatcher or only lost during redirects.
-
Create or update the
cdn.yamlfile in your repository using the following structure:code language-none kind: "CDN" version: "1" metadata: envTypes: [ "dev", "stage", "prod"] data: requestTransformations: removeMarketingParams: false rules: [ ] -
If validation fails with a missing
rulesproperty, add an emptyrules: [ ]entry underrequestTransformations. -
Re-test and confirm that query parameters are preserved.
-
Check for conflicting redirect rules in both
cdn.yamland Dispatcher configuration. -
If using CDN redirects, set
reqProperty: urlinstead ofreqProperty: path. -
Confirm that match and transform rules apply to URLs that include query parameters.
-
Update Dispatcher redirect rules to preserve query parameters using
QSA:code language-none RewriteRule /path$ /target [ R=301,L,QSA]