Repository navigation
Conversation
Colombia ATDC needs a stable AMP client id on each ad request. Register AMP_ECID_COLOMBIA and forward context.clientId on the vendor payload. Co-authored-by: Cursor <cursoragent@cursor.com>
Use site-user-id-cookie-fallback-name so atdcUid matches colanalytics val_122.
|
Hi @calebcordry / AMP team, Could you please review PR #40566? It has been open for around few days, and the following checks are still pending. The CLA is already signed, and the remaining checks have passed. Please let me know if any changes are required from our side. Thanks. |
|
Hi @calebcordry @camelburrito / AMP team, Could you please review PR #40566? It has been open for around few days, and the following checks are still pending. The CLA is already signed, and the remaining checks have passed. Please let me know if any changes are required from our side. Thanks. |
|
Hi @calebcordry / AMP team / @ampprojectbot , Could you please review PR #40566? It has been open for around few days, and the following checks are still pending. The CLA is already signed, and the remaining checks have passed. Please let me know if any changes are required from our side. Thanks. |
|
Hi @calebcordry — could you please take a look at this PR when you have a moment? It adds a stable client ID (atdcUid) for Colombia ads (ads/_config.js and ads/vendors/colombia.js). Could you also approve the pending GitHub Actions workflows and Percy check so CI can complete? Thanks! |
Summary
Colombia ads need a stable client id on each ad request, so the same browser can be recognized across page views.
colombiaad type. AMP only setscontext.clientIdwhen that scope is present.atdcUid, with-0000000appended.If the scope is missing,
context.clientIdis null andatdcUidis sent empty.Test plan
<amp-ad type="colombia">and confirm the ad frame receives a client id.atdcUidas{clientId}-0000000.