ENG-3193: Add utm params to brand links

[eastandwestwind]

Ticket https://ethyca.atlassian.net/browse/ENG-3193

Description Of Changes

• Adds UTM tracking parameters (utm_source, utm_medium, utm_campaign, utm_term) to all outbound Ethyca brand/attribution links across both fides-js and privacy-center
• The existing "Powered by Ethyca" brand links (logo-style) now point to https://ethyca.com/?utm_source=fides_consent&utm_medium=referral&utm_campaign=cmp_backlinks&utm_term=home
• The newer "Consent powered by Ethyca" attribution link default URL now points to https://www.ethyca.com/janus?utm_source=fides_consent&utm_medium=referral&utm_campaign=cmp_backlinks&utm_term=janus

Code Changes

• Updated href from https://ethyca.com/ to include UTM params (utm_term=home) for both fides-js and privacy center brand link components (this is for the ethyca logo itself which is present when new attribution is both enabled and disabled)
• Updated DEFAULT_ATTRIBUTION_DESTINATION_URL from https://www.ethyca.com/janus to include UTM params (utm_term=janus)

Steps to Confirm

1. With FIDES_PRIVACY_CENTER__ATTRIBUTION_ENABLED=false confirm that both the fides-js modal and privacy center include brand links that point to https://ethyca.com/?utm_source=fides_consent&utm_medium=referral&utm_campaign=cmp_backlinks&utm_term=home

2. With FIDES_PRIVACY_CENTER__ATTRIBUTION_ENABLED=true confirm that both the fides-js modal / banner and privacy center include brand links that point to https://www.ethyca.com/janus?utm_source=fides_consent&utm_medium=referral&utm_campaign=cmp_backlinks&utm_term=janus

Pre-Merge Checklist

• Issue requirements met
• All CI pipelines succeeded
• CHANGELOG.md updated
  • Add a db-migration This indicates that a change includes a database migration label to the entry if your change includes a DB migration
  • Add a high-risk This issue suggests changes that have a high-probability of breaking existing code label to the entry if your change includes a high-risk change (i.e. potential for performance impact or unexpected regression) that should be flagged
  • Updates unreleased work already in Changelog, no new entry necessary
• UX feedback:
  • All UX related changes have been reviewed by a designer
  • No UX review needed
• Followup issues:
  • Followup issues created
  • No followup issues
• Database migrations:
  • Ensure that your downrev is up to date with the latest revision on main
  • Ensure that your downgrade() migration is correct and works
    • If a downgrade migration is not possible for this change, please call this out in the PR description!
  • No migrations
• Documentation:
  • Documentation complete, PR opened in fidesdocs
  • Documentation issue created in fidesdocs
  • If there are any new client scopes created as part of the pull request, remember to update public-facing documentation that references our scope registry
  • No documentation updates required

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
fides-plus-nightly	Ignored	Preview	Mar 30, 2026 1:02pm
fides-privacy-center	Ignored		Mar 30, 2026 1:02pm

[kruulik]

👍