Implement device-specific landing pages

If you've created pages on your site that are designed for specific devices, use the ifmobile and ifnotmobile dynamic parameters to direct visitors to the correct page depending on the type of device they're using. The search engines determine which URL to use when they serve an ad. For example, the following keyword specifies https://m.example.com?utm=c&device=m as a landing page for mobile devices and https://example.com?utm=a&device=d for tablets and desktop computers:

You can include these parameters when you're creating ads, creating keywords or editing existing keywords.

Search Ads 360 only supports the ifmobile and ifnotmobile parameters

Even for those search engines that support other ways of specifying device-specific landing pages, Search Ads 360 only supports the ifmobile and ifnotmobile parameters. If you use the ifphone and ifnotphone parameters in a Yahoo! Gemini account, Search Ads 360 will convert them into ifmobile and ifnotmobile.

Shared parameters

If some of the parameters are the same for both device types, define them just once, either at the end of the landing page URL, in a URL template, or in a Final URL Suffix. For example, if you want both device types to pass the id of a specific product to the landing page, specify this landing page URL: 
https://{ifmobile:m.example.com?utm=c&device=m}{ifnotmobile:example.com?utm=a&device=d}&sid=1234567

URL fragments after the query string

If you use an {ifmobile} or {ifnotmobile} parameter in a query string (not recommended), including a URL fragment in the ifmobile/ifnotmobile parameter itself is not valid.

For example, this landing page URL is not valid in Search Ads 360 because the ifmobile / ifnotmobile parameters are part of the query string, and the parameters include URL fragments:
https://example.com?p_id=42{ifmobile:&d=m#frag1}{ifnotmobile:&d=d#frag2}

Recommended practice

If you're using a URL template or a Final URL Suffix in accounts with shared templates, add fragments to the end of the URL template or Final URL Suffix. If instead you add a fragment to the end of the landing page URL, any URL parameters in the template may be interpreted as part of the fragment and therefore ignored by the landing page.

Otherwise, use device-specific URLs instead of device-specific query strings with fragments. This landing page is valid in Search Ads 360 because the ifmobile / ifnotmobile parameters are not within the query string:
https://{ifmobile:example.com?p_id=42&d=m#frag1}{ifnotmobile:example.com?p_id=42&d=d#frag2}

Note that this URL is not valid because the URL fragment is not at the end of the URL:
https://{ifmobile:example.com?p_id=42&d=m#frag1}{ifnotmobile:example.com?p_id=42&d=d#frag2}&mtype={MatchType}&kw={Keyword} 

Instead, you would need to repeat the "mtype" and "kw" parameters in each device-specific URL:
https://{ifmobile:example.com?p_id=42&d=m&mtype={MatchType}&kw={Keyword}#frag1}{ifnotmobile:example.com?p_id=42&d=d&mtype={MatchType}&kw={Keyword}#frag2} 

Google Ads Final Mobile URLs

Final Mobile URLs are another way to specify mobile landing pages for keywords in Google Ads (instead using the ifmobile and ifnotmobile ValueTrack parameters). You cannot create, manage, or display Final Mobile URLs from Search Ads 360.

If you sign into Google Ads and create Final Mobile URLs:

• You can successfully sync the keywords into Search Ads 360, but Search Ads 360 ignores the Final Mobile URL. Search Ads 360 only syncs the Final URL exactly as specified in Google Ads.
• Google Ads uses the Final Mobile URL for mobile devices even if the keyword landing page URL contains {ifmobile} parameters. If the Final Mobile URL is invalid (for example if it points to a non-existent page), Google Ads will fall back to the landing page URL.

Clicks on Final Mobile URLs are included in Search Ads 360 reports, and device segments and dimensions correctly attribute mobile traffic to mobile devices.

Baidu Mobile and Non-mobile URLs

Baidu requires keywords and ads to specify mobile and non-mobile URLs. If you sign into Baidu and create keywords and ads, you're required to enter two separate URLs (one mobile devices and the other non-mobile devices). When you sync keywords from Baidu into Search Ads 360, Search Ads 360 reformats the two separate URLs as a single landing page URL with ifmobile and ifnotmobile parameters. You can also mix URL protocols for the same keyword.

Trafficking URLs to Baidu

Search Ads 360 always traffics two clickserver URLs to Baidu for each keyword: one for mobile devices and one for non-mobile devices. (If you specify only one landing page in the Landing page URL column, Search Ads 360 uses the same landing page for both clickserver URLs.)

Trafficking a Microsoft Advertising URL to the engine

If you use device-specific landing pages in Microsoft Advertising campaigns, Search Ads 360 appends the entire URL to the clickserver URL in the ds_dest_url query string. This is regardless of the landing page parameter option that you've selected for the engine account. This means that the clickserver URL for a keyword would look something like the following:

https://clickserve.dartsearch.net/link/click?lid=43700001171542080&ds_s_kwgid=58700000138513001&ds_e_adid={creative}&ds_e_matchtype={ifsearch:search}{ifcontent:content}&ds_e_device={device}&ds_url_v=2&ds_dest_url=https://{ifmobile:m.example.com?utm=c&device=m}{ifnotmobile:example.com?utm=a&device=d}