# 9th Sep: Custom click for Google Ads, Meta parameter builder, External ID for Klaviyo and more
### :sparkles:New and noteworthy
#### Add support for a custom click ID key for Google Ads
We're excited to enhance your experience with our new Custom Query Key for Google Ads! This powerful feature empowers you to customize how you attribute clicks, ultimately boosting your conversions. To make it easier, we've put together a [comprehensive guide](/channels/google-ads/configuration.md#custom-query-key) to help you get started.
#### Add support for Meta's Parameter builder
The addition of this support comes from extensive collaboration with Meta's CAPI team. We dedicated weeks to working together and testing the improvements from their new Parameter Builder JavaScript helper. The first results were really promising. With this support, your attribution will function even better, as we can now connect in-app browsing and resolve broken click IDs. The best part is that you don’t need to do anything —we have automated the entire process.
#### External ID support for Klaviyo
When we initially integrated with Klaviyo, we designated our user ID as the external ID in the platform. Our reasoning was that this would enhance the connection between anonymous and identified users. However, the downside of this approach is that Klaviyo treats the external ID as the primary identifier instead of the email address. As a result, it is possible to have two profiles associated with the same email but linked to different external IDs. Due to this behavior, we decided to remove this functionality. \
\
After speaking with our customers, we learned that some still wanted this option available. We are always eager to support our customers, so we have now added an opt-in feature for this functionality.
### :zap:Improvements
\[Channel] - Wicked reports are not processing the organic parameter correctly
\[App] - Automatically add NC/RC plugin for new tags and remove old checkboxes
### :book: Details
Release day: 9th September 2025\
Release version: 25-33\
Edge version: 13.123.0\
SDK version: 1.29.0
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.edgetag.io/changelog/september-2025/9th-sep-custom-click-for-google-ads-meta-parameter-builder-external-id-for-klaviyo-and-more.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.