A search specialist needs to track Floodlight conversions for an engine that isn't officially listed in the Search Ads 360 interface. Which workflow should they use to generate tracking URLs for this source?

For engines that are not supported directly, Search Ads 360 uses an Other engines client account with placeholder keywords so it can generate clickserver URLs for tracking. Google documents that this setup is the workflow used to track conversions on unsupported advertising platforms, including creating the account, adding placeholder keywords, and then copying the generated clickserver URLs for use on the external platform. Google Help+1 The placeholder keyword acts as the reporting object that receives visits and attributed Floodlight data after the click redirects through Search Ads 360. Google Help This is why the unsupported source must be represented through that account type rather than through a supported engine configuration. Google Help+1 Google now recommends engine track accounts for unsupported engines, but the documented placeholder-keyword workflow is still supported and is the one that generates tracking URLs in this context. Google Help+1