[null,null,["上次更新時間：2025-08-27 (世界標準時間)。"],[[["\u003cp\u003eUpgraded URLs offer separate fields for tracking information and landing page URLs, providing greater flexibility.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003efinal URL\u003c/code\u003e field represents the user's final landing page and should be the URL visible in the browser bar after clicking an ad.\u003c/p\u003e\n"],["\u003cp\u003eA \u003ccode\u003etracking template\u003c/code\u003e can be used to incorporate additional tracking parameters or redirects, ultimately directing the user to the final URL.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eCustom parameters\u003c/code\u003e enable the creation of user-defined parameters, offering functionality similar to ValueTrack parameters for enhanced tracking and analysis.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eFinal mobile URLs\u003c/code\u003e and \u003ccode\u003efinal app URLs\u003c/code\u003e allow for tailoring the user experience based on device type and app installation status, respectively.\u003c/p\u003e\n"]]],[],null,["# Fields\n\nUpgraded URLs allow you to specify the tracking and landing page parts\nof your URL through separate fields:\n\n- **Final URL:** Represents a list of actual landing pages for your ad, keyword, or sitelink. The final URL must be what the user ultimately sees in the browser bar after clicking an ad.\n- **Final mobile URL:** Represents a list of possible final mobile URLs for your ad, keyword, or sitelink after all cross domain redirects.\n- **Final App URL:** Represents a list of final app URLs that will be used on mobile devices if the user has the specific app installed.\n- **Tracking template:** Optional template to specify additional tracking parameters or redirects. We will use this template to assemble the actual destination URL to associate with the ad.\n- **Custom parameters:** Optional [ValueTrack](//support.google.com/google-ads/answer/2375447) parameters to which you can assign your own IDs.\n\nAs an example, you can find the detailed specifications of these fields at this\n[reference page](/google-ads/api/reference/rpc/v21/Ad) for the `Ad` object.\n\nField descriptions\n------------------\n\nThe sections below describe the fields that comprise an Upgraded\nURL.\n\n### Final URL\n\nThe final URL represents the actual landing page for your ad, keyword, or\nsitelink. The final URL must be the URL the user sees in the browser\nbar after clicking your ad: It must not have any off-domain redirects.\n\nFinal URLs follow the same override rules as destination URLs. For example,\na final URL at the keyword level overrides a final URL at the ad level.\n\nAll existing validation rules for destination URLs also apply to final\nURLs. You can have URL tags in final URLs. All tags should either be\nvalid ValueTrack tags, or custom parameters. You can have up to four\nlevels of nesting when specifying URL tags: \n\n {ifmobile:{ifsearch:{keyword:cp={_customP}}}}\n\nMost of the time, you only need to specify one final URL or final mobile\nURL. In the rare case where a [tracking template](#tracking_template) might\nredirect the user to one of several landing pages that don't go through a\ncommon landing page on the advertiser's domain (for example, when testing landing\npages), you can specify these landing pages using multiple final URLs.\n\n### Final mobile URLs\n\nIf you want to send users to a different landing page on mobile devices you can provide a\nseparate mobile-preferred final URL. However, if you\nprefer using [ValueTrack](//support.google.com/google-ads/answer/2375447)\nparameters, you can use existing ValueTrack parameters\n`{device}` and `{ifmobile}` instead of this field.\n\n### Final app URLs\n\nIf you have ads that link directly into in-app content using\n[deep links](//support.google.com/google-ads/answer/6046977), or have\n[click-to-download ads](//support.google.com/google-ads/answer/2549053),\nyou can specify these URLs in the final app URLs field.\n\n### Tracking template\n\nThe tracking template field lets you specify any additional tracking parameters\nor redirects. When this parameter is specified, it will be used instead of final\nURLs to assemble the actual destination URL for your ad. The tracking service\ntracks the click and redirects the user to a landing page. The URL of the\nlanding page should match the final URL. This template can embed the final URL\nusing ValueTrack parameters such as `{lpurl}`.\n\n### Custom parameters\n\nCustom parameters allow you to create your own parameters, similar to ValueTrack\nparameters. This can be useful when you want to use your own IDs, for instance,\nin identifying ads. Previously, you'd have to hardcode this in the ad's\ndestination URL. Now, you can specify the ID for the ad, use a custom parameter\nfor each ad, and then refer to the custom parameter in the final URL and/or\ntracking template, as you would for any other ValueTrack parameter.\n\nThe name of a custom parameter can only contain alphanumeric characters. When\nreferring to the custom parameter in final URLs and tracking templates, you\nshould surround the custom parameter in braces, and prefix an underscore to\nits name---for example, `{_promoCode}`.\n| **Note:** When setting custom parameter values for an [supported\n| entity](/google-ads/api/docs/ads/upgraded-urls/supported-entities), items on the `url_custom_parameters` list (e.g. that of an [`Ad`](/google-ads/api/reference/rpc/v21/Ad) object ) must have a unique [`key`](/google-ads/api/reference/rpc/v21/CustomParameter). The uniqueness check is case-insensitive, so your list cannot contain an item with `key=\"promoCode\"` and another item with `key=\"promocode\"`. If you have multiple items with the same `key` in the `url_custom_parameters` list, your request will fail with `DistinctError.DUPLICATE_ELEMENT`.\n\nAs with final URLs, custom parameters in a lower-level entity override\nvalues for higher-level entities. You can have up to eight custom\nparameters for an entity. The key and value must not exceed 16 and 200 bytes,\nrespectively."]]
