[null,null,["最后更新时间 (UTC):2025-07-26。"],[[["\u003cp\u003eEnhance your product feeds by including deep links for product and list views, enabling a seamless user journey from Google surfaces like Search and Maps to your website.\u003c/p\u003e\n"],["\u003cp\u003eLeverage URL template parameters like \u003ccode\u003e{lang}\u003c/code\u003e, \u003ccode\u003e{currency}\u003c/code\u003e, and \u003ccode\u003e{product_id}\u003c/code\u003e to tailor the landing page experience based on user context and product selection.\u003c/p\u003e\n"],["\u003cp\u003eUtilize the \u003ccode\u003efunnel\u003c/code\u003e parameter to distinguish between navigational and categorical queries, allowing for optimized content delivery based on user intent.\u003c/p\u003e\n"],["\u003cp\u003eConsider adding option-specific anchors to your URLs for a more targeted landing experience, ensuring the chosen product option is prominently displayed.\u003c/p\u003e\n"],["\u003cp\u003eWhile the \u003ccode\u003e{src}\u003c/code\u003e parameter can still be used to identify click sources, please note it is deprecated and will be phased out; transition to using the \u003ccode\u003e{surface}\u003c/code\u003e parameter for future compatibility.\u003c/p\u003e\n"]]],["Deep links for product `Options` can be provided for both product and list views, utilizing URL templates. These templates allow for dynamic parameter replacement, including `{surface}`, `{funnel}`, `{lang}`, `{currency}`, `{product_id}`, `{option_id}`, and `{GOOGLE-ADS-CLICK-SOURCE}`. These parameters capture details about the user's context and the product. Parameters can be combined with `&`. The `src` parameter is deprecated. This allows for customized landing pages based on user language, currency, and query type.\n"],null,["# Deep link and URL templates\n\nFor each product `Option` in the product feed, you can provide up to two deep\nlinks (one for product view and another for list view). Each deep link has\nbuilt-in URL template support which enables Google to provide you information\nabout the source of the deep link click.\n| **Note:** Things to do Ads will always use the list view deep link if available. Things to do search will determine the most suitable deep link depending on context.\n\nBy adding additional parameters using URL templates to your deep links, you can\nidentify the source of the deep link click, the currency and language of the\nuser and some additional detail about the product clicked. With this\ninformation, you can then route the user to the most appropriate landing page\n(e.g. with the matching language and currency).\n| **Note:** While Option deep links can be the same across a single product, depending on the website design it may make sense to add an anchor to the URL on a per option basis. This will allow the option selected by the user to be presented front and center on the landing page.\n\nHow URL templates work\n----------------------\n\nTo make use of URL templates, deep links provided to Google must include URL\ntemplate parameters such as `{lang}`. When your deep link is clicked, the URL\nwhich the user is directed to will replace these parameter with the resolved\nvalues.\n\nIf you want to add more than one parameter to a single URL, append them\ntogether in your URL using an ampersand (\\&), like this:\n`?currency={currency}&language={lang}`\n\nFor language codes, refer to\n[BCP47](https://tools.ietf.org/search/bcp47).\n\nThe supported URL parameters are:\n\n| Parameter | What it returns |\n|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| `{src}` **deprecated** | Source of the deeplink click. e.g. The value \\`cu\\` will be returned when URL is triggered from Things to do Ads. Possible values are: bm, cu, e, o. **This field is now deprecated.** This field will continue to be populated for a short period while partners migrate. |\n| `{surface}` | The surface which the product is served on. Possible values are \"search\", \"maps\". |\n| `{funnel}` | Which query funnel which the product is served from. Possible values are \"cat\", \"nav\" |\n| `{lang}` | The language the user is browsing in. For example: \"en-US\". |\n| `{currency}` | The currency the user is browsing in, For example: \"USD\". |\n| `{product_id}` | The id of the product which the user clicked. |\n| `{option_id}` | The id of the product option which the user clicked. |\n| `{GOOGLE-ADS-CLICK-SOURCE}` | The Ads source which the click came from. Possible values: tfsa, tpa |\n\n| **Note:** src parameter is deprecated and support for the parameter will be removed over time.\n\n### Navigational versus categorical queries\n\nNavigational queries are user queries with significant navigational intent such\nas \"Eiffel Tower\", \"Dan's bike tours\". Traffic generated from these queries\nhave their `funnel` template value set to `nav`.\n\nCategorical queries are queries such as \"Bike tours in Paris\" where the user is\nlooking for a breadth of options. Traffic generated from these queries have\ntheir `funnel` template value set to `cat`.\n\nExamples\n--------\n\nIf a user is browsing in *English UK* , shopping in *Pounds* and\nclicked on *an attractions ticket on Google maps* then the URL template: \n\n www.test.com/deeplink?s={surface}&f={funnel}&lang={lang}¤cy={currency}\n\nwill resolve to: \n\n www.test.com/deeplink?s=maps&f=nav&lang=en-GB¤cy=GBP"]]