A function macro performs a function on another macro. Function macros can be used in\u00a0combination with any other creative macro, including custom macros although if they are not\u00a0recognized at render time, they will not be translated and the function will not be called.\u00a0<\/p>\n\n\n\n
Pontiac currently supports the {$URL_ENC} function macro, which can be used for a variety of purposes related to encoding. A key use case is when a URL needs to be passed from ad server to ad server via a creative macro, and due to the presence of unsupported characters in standard URL formatting, must be encoded at various steps of the process. <\/p>\n\n\n\n
The macro takes the following form: <\/p>\n\n\n\n
${URL_ENC(${MACRO_NAME},#)} <\/p>\n\n\n\n
where\u00a0${MACRO_NAME}\u00a0is the macro to be encoded and # is the integer\u00a01,\u00a02, or\u00a03, representing\u00a0the number of times to encode the contents. Note that more than three encodings are not\u00a0supported.\u00a0\u00a0<\/p>\n\n\n\n
Each encoding corresponds to a step in the redirect chain, as well as how a given third-party\u00a0click tracker works with the macro. Double encoding will usually be needed for final destination\u00a0URLs when a second ad server is involved, and triple encoding for a third ad server.\u00a0<\/p>\n\n\n\n
To determine whether you will need to use single, double, or triple encoding, you should check with your third-party click tracker and then test your\u00a0URL_ENC\u00a0macro to ensure it works. If your macro is not working, one consequence of this may be link breakage, which will result in users\u00a0 not reaching the intended destination URL.\u00a0<\/p>\n\n\n\n