Where is the developer token coming from in the Adobe Event Forwarding Google Ads Enhanced Conversions extension?

Question

I am using the CONCORD - Google Ads Enhanced Conversions extension in Adobe Event Forwarding. In the action code the header is set to a placeholder string like [[GOOGLE_ADS_DEVELOPER_TOKEN]] and I cannot find any function in the extension source that replaces it from settings, data elements, or secrets. But in Edge logs the outbound request shows a developer token header with a masked real value.

Is the developer token baked into the published extension build by the vendor, or injected at publish time, and is it expected that the vendor uses one developer token for all customers?

bjoern__koth · Answer

Hi ​@lnourany server-side forwarding happens through API endpoints which are secured and require tokens to access them and can be retrieved through e.g.Google Ads itself.You may need admin rights to generate these tokens though.I do not know the extension itself but typically, you can configure the token directly in the extension settings. Since API tokens are secrets, you may have to create them as secrets in Launch SSF first, and then create a data element that references the right secret per environment.

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded