{"id":15139,"date":"2026-10-01T03:37:06","date_gmt":"2026-10-01T03:37:06","guid":{"rendered":"https:\/\/playgama.com\/blog\/?p=15139"},"modified":"2026-10-01T03:37:06","modified_gmt":"2026-10-01T03:37:06","slug":"how-to-detect-host-portals-using-url-parameters-in-multi-por","status":"publish","type":"post","link":"https:\/\/playgama.com\/blog\/business-faqs\/how-to-detect-host-portals-using-url-parameters-in-multi-por\/","title":{"rendered":"How to detect host portals using URL parameters in multi-portal builds?"},"content":{"rendered":"

Ask each portal how it identifies its iframe (usually a query parameter on the game URL, sometimes the referrer) and check it once at load with a small switch, so one build can adjust ad calls or branding per portal without shipping separate builds.<\/strong><\/p>\n

At a glance<\/h2>\n\n\n\n\n\n\n\n
Fact<\/th>\nValue<\/th>\nSource<\/th>\n<\/tr>\n<\/thead>\n
CrazyGames iframe check<\/td>\nquery param + absoluteURL.Contains<\/td>\ndocs.crazygames.com<\/a><\/td>\n<\/tr>\n
CrazyGames local dev override<\/td>\n?useLocalSdk=true<\/td>\ndocs.crazygames.com<\/a><\/td>\n<\/tr>\n
Detecting host portals<\/td>\ncheck query parameters at load<\/td>\ndeveloper.mozilla.org<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Read the query string on the URL your game is loaded with, and match it against the parameter each portal documents for its own iframe. For example, you can add a query parameter to your iframe URL when submitting and inspect the page URL in code. That is the pattern to copy for any other portal: agree on a parameter with the portal (or read one they already append), then branch your ad calls, SDK init, or branding based on it.<\/p>\n

For deploying builds, Playgama MCP<\/a> lets coding agents upload builds and publish sandboxes directly.<\/p>\n

What should you check per portal?<\/h2>\n