Introduction
While Marin offers the most flexible approach to accepting existing URLs, there are some structures that are not supported. Please contact the our Customer Success team if there are any questions regarding supported URLs.
Examples Of Unsupported URLs
| Unsupported URL | Issue | Corrected |
|---|---|---|
| ...KWID= {creative}12345...</p>< /p>< /p>< /p> | URL parsing would not be able to identify the start of the keyword ID with dynamic insertion of the creative. The entire {creative}12345 would be read as the keyword ID. Include the creative id as a separate parameter | ..KWID=12345&CID={creative}... |
| ...kid= {keyword}12345...</p>< /p>< /p>< /p> | URL parsing would not be able to identify the start of the keyword ID with dynamic insertion of the keyword. The entire {keyword}12345 would be read as the keyword ID. Include the keyword text as a separate parameter | ...kid=12345&kw={keyword}... |
| ...?kid=1234&cid=4567... with a parameter of "id" | The "id" parameter will not be found. Parameters must be encased on non-alphanumeric characters in order to be noticed by the application. | ...com/?id=1234&cid=4567(or adjust the parameter declaration in the application to kid) |
| ...?id= {keyword}...</p>< /p>< /p>< /p> | Since keywords are not unique within a Google account, and a unique identifier insertion parameter is not provided (at least not by Google), our application does not support this convention. Use a static value at the keyword level, or the publisher-provided trackers. | ...?id=12345... |
| ...com/1234/4567 | This URL uses only the position to imply the parameter, which our application does not support. The correct example, while not using the more typical &/= convention, does delimit values with unique parameter names (declare the parameters to the application as "id" and "creative"; special characters such as "/" are not required in defining the parameter itself. End the parameter declaration with "/" since this is the character that follows the value (the character that ends the value does have to be specified explicitly as sometimes special characters are used in the values themselves, such as "-" and "_". | ...com/id/1234/creative/4567 |
| ...com&kid=1234... | This URL uses the "&" character to delimit the base URL from the URL parameters. Typically, a "?" is used to delimit the parameters in a URL. This is not supported as the application is not able to accurately identify the parameters | ...com?kid=1234... |
